Wired, Xbox X, 1 Gbps fiber optic internet verified by Xbox network Test, no other issues.
When you open almost any modern application (on PC, on Mac, on Xbox) the standard practice is to verify the signature via a “notary server” online. If that notary server is offline or unreachable, the OS should have a graceful fallback logic (example, recognize that it has been ‘notarized’ on previous launches with no changes and allow you to launch) however the Xbox is not doing this, and is instead throwing up a generic error that there is an issue with the license which seems to blame the user, instead of distinguishing that it is an unreachable server. It’s really lazy programming, resulting in a terrible experience.
I believe MSFS or the Xbox is using stale DNS cache results, because if I unplug the ethernet cable (effectively the same as switching to Wifi and back) it forces new DNS requests which then resolves and finds the servers.
What s worse, is the error then states that I don’t have “Offline Mode Files” installed so I can not start a flight… but I DO have Offline files installed, 60 GB worth, so the error is 100% incorrect. It is because it can’t reach the “notary servers” to validate the license and has no graceful fallback. So again, the error messaging is WRONG. Who is the person who decides the error flow chart, please? They need to include graceful fallback for DNS resolution errors, and MSFS needs to not use stale DNS cache results.
Since we are beta testing, I’m TRYING to give MS / Asobo feedback about this bug, but it is falling on deaf ears, apparently.
