About bobvlas

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. Regards, Bob ... View more

In my view things go like this: 1.In the main screen of the app, when not connected to the hub the user swipes one of the lower module icons (e.g. "Music" or "Contacts"). 2.User taps "Edit" 3. A page "Add and manage your modules below. The minimum number is two." appears. 4. User adds his "My Module" by tapping the green +-icon. 5. Then a page appears "Enter URL of your module:" 6. Now user can input the url of his module. This could be like "http://localhost:9000". The user module then is situated on the device and delivered by a local webserver. All references in the module are to local files, even "cobi.js" is. So for this module no internet access is required. 7. The above url is stored in localStorage. 8. This all happens during installation and being on line. 9. During riding ("COBI.context.onRide") I noticed the app trying to reopen the page mentioned above under 5. That page is loceted on the web and thus needs internet access. But opening it is unnecessary because the user url has already been stored in localStorage. Maybe you can look at it? Regards, Bob ... View more

Can you please give us a clou as to how long it will be goint to take? ... View more

Okay, then please explain why it is that my module, that does not need internet access at all, combined with the Cobi app that does not need internet access during ride, when they are coupled do need internet access?   Regards, Bob       ... View more