I totally see your point. In a way, what you describe is exactly what happens. However, we are not fully in control of how the LocalStorage is treated, as this is handled by the underlying browser. We have observed there are circumstances in which iOS or Android will clear the LocalStorage either because memory is needed or because the cached information has expired.
Unfortunately, this is the behaviour of the native system and as far as I know, it cannot be changed. I will double check with the team though.
You must be mistaken.
When onRide mode is activated the app must be aware of the module being present and active otherwise no messages would be sent to the module. At that time there is no need to reconnect the same module and thus there is no need to fetch the url. No localStorage involved eventually. Apart from that, localStorage is perfect as long as you treat it correctly.
I suppose you're either not able or unwilling to correct this issue. Which turns Bosch's claims on the internet false. I shall have to consider applying for a refund.
I apologize because I am probably not explaining the functionality of the app clearly enough. However, I can assure it is as described in my previous message.
While checking our documentation on Github I stumbled upon the following statement in our FAQ: "Currently, the user needs to be online to render the module: COBI.js does not support an offline mode."