App exits before auto-starting on install, but runs fine when started manually

[Jon-DK]

I am working on an update for a rather large app. When running on the emulator, everything is fine, but when I sideload the updated version to a Versa, or install it from the Fitbit App Gallery, the app installs but quits before actually running. The log shows no entries from the App, only from the Companion:

[11:11:06 AM] Companion: Companion launched by [launchedOnTracker]
[11:11:15 AM] Companion: App closed on device, unloading companion in 3 seconds…
[11:11:18 AM] Companion: Unloading companion…

However the app seems to install fine, and when I start it by tapping its icon on the watch, it runs as expected.

[11:19:19 AM] Companion: Companion launched by [launchedOnTracker]
[11:19:19 AM]       App: App Started

[11:19:20 AM]       App: JS memory: After initialize - 51720/65528

… more logging from App

The same thing happens when installed from the App Gallery, so the update was rejected for auto-exiting and not starting.

I've tried to remove chunks of Javascript and svg-markup, removing and reinstalling the app, but it seems very fuzzy at which point it will actually auto-start consistently.

Any ideas what could be the problem here, and what I can do to solve it? I've seen in another thread that unused markup should be hidden with display="none" and not visibility="hidden" but I already do that. 

Thanks in advance for any suggestions

Best regards

Jon

[JonFitbit]

It sounds like it's taking too long during the bytecode compilation phase. Are you able to PM me a link to download the project source, and I can as the engineering team to take a look.

Thanks

[Jon-DK]

Hi

Did the engineering team have a chance to look at this yet?

Thanks and best regards

Jon

[Jon-DK]

Hi again

I know you guys are probably busy, but I hope you can take the time to look into this issue. Thanks in advance!

Best regards

Jon