Reduce startup delay about garminhomeassistant HOT 5 CLOSED

Might trial this to see if it saves a noticeable amount of time given the toggle states still need updating anyway.

from garminhomeassistant.

@philipabbey Thank you very much!

from garminhomeassistant.

Hello @minusnine!

Thank you for your interest in the application.

I believe this is because the app performs a synchronous HTTP GET to retrieve the configuration.

All responses to a call to makeWebRequest are asynchronous, meaning once they are fired off, the application continues, but it can't do much without the response!

Would you consider some means to allow the user to cache this information to reduce latency?

Under different circumstances - yes. However we are limited in what we can offer in a watch environment. Presently, I'm trying desparately to reduce the memory footprint in order to continue supporting some older devices. As a result there will be no room for new features.

Sorry.

from garminhomeassistant.

Simulation of a Vivoactive 3 device without debug:

Error: Out Of Memory Error
Details: Failed invoking <symbol>
Stack: 
  - initialize() at 

Encountered app crash.

Pity as I had it working quite nicely.

from garminhomeassistant.

So the memory issues might just be down to struggling to force the SDK to compile without debug.

from garminhomeassistant.