It would not be as simple as simply “skipping” the inside network test. Those Xboxes would have to be inside the Xbox network to load the addons initially. There is NO way to load an Xbox with an addon into the reserved space for the app from outside the Xbox network. Otherwise developers could test addons themselves. The security of the Xbox architecture won’t allow that.
The presumption is an Xbox should act the same inside the network as outside the network since they are the same hardware and same software. This turned up a problem in the API or core code. Once that code is fixed, an Xbox inside or outside the network should act the same.
I understand people don’t like buying a product then having to wait. But on the other hand, if the DC6 worked out the gate on XBox, but next month a sim update required PMDG to make a change, you would want that update as soon as possible. If instead of 2 weeks to get the update, it took 3 or 4 weeks, you would be mad and want them to optimize the process to get updates into the marketplace. The are mutually exclusive. You either get more testing, or faster packaging time, but you can’t possibly add more time to each package but make the updates faster.
In case you think I have no skin in the game her, I own both products. I haven’t asked for a refund, even though Seafront Simulations was worried enough to ask all of us to do so. I understand the complexity of what happened, and I’m not blaming anyone, not the developers, not Asobo, not Microsoft. It will get fixed, and I will be able to enjoy my products. Meanwhile, there is still plenty for me to do in MSFS. It’s not like the sim is crashing because of these two products. Look at it like these are products you really believe in, and have pre purchased them.