@lance.carocci wrote:
@scott.denman, it's standard practice for us to request logs in order to identify where the problem lies, as this experience is not intentional. Whether you have forced Fusion into Offline Mode or physically disconnected your internet, it's not by-design that they hold up initialization until they time out, they are supposed to retry silently in the background.
Requesting log files is fine, though in this case they swell up to several hundred megabytes over the span of a few minutes. I can confirm that it does hold up initialization, and the same line keeps being emitted in the logs (I'll happily provide a snippet when I'm able to). Maybe the app is crash-looping at another point after it writes the log statement, but wasn't emitting any other details about where that might be. I could see the launchdarkly logs being a red-herring in this case. Hopefully y'all can get to the root of this bug soon 🙂
Please note, however, that Fusion is far from offline software just because it has an Offline toggle.
Either it can or it can't. If enough has migrated to the cloud that the software is unusable without it, then get rid of offline mode, and make sure people know that it is 100% required to use the software. It'll save a lot of frustration with folks who think they are getting a traditional desktop application. Call it "Fusion Cloud" or something, I'm not a marketing expert.
Offline mode exists because we know travel or areas without internet is the reality of life, but the app is not designed to run in Offline mode by default or indefinitely, and it is not designed to run with cloud endpoints blocked.
So again, let's make sure that if you're building an offline mode into the software, that it is well tested and supported. If Autodesk isn't going to do that, then kill the feature off and be honest about how this software is entirely dependent on an internet connection and Autodesk services. From my experience, the software can not start up without an internet connection, so it's useless offline to me.
As far as blocking cloud endpoints, I expect software to be communicating directly with *.autodesk.com, not random third-party URLs directly. In the former case, it would be obvious what was happening, and I would be 100% okay with not blocking those endpoints. Even with options to "opt-out" of things like tracking and analytics, it's perfectly valid to completely block unknown endpoints instead of trusting a vendor's "promise".