ExplorOz Traveller won't Open.

Rob

Mine seems to work fine on an ipad in places a long way from any internet coverage.
Tells me where I am, where I’ve been and what’s around and up ahead.
Just saying.

Cheers

I am an Apple man, but have 2 windows computers that I purely use for Ozi, a bullet proof system and has never let me down in nearly 20 years of using it.

The ability to add your own maps is great and very flexible.

Stefan,

Your assertion about version updates is totally false. So to clarify:

Many of the version numbers are not ever released to the public but are test versions. What you don't know is the rules that govern app developers that are governed by the stores which mean we unable to reuse a number that was used in a test version so once we even just publish a test version to the stores to get that into the store we have to publish it as another number.

In addition, 8.0.0 - 8.0.2 were the initial releases across the 4 platforms. One update related to the photo output grid change, one for a link to the reference manual download. So we used up a few versions of 8 just getting to release as some things were found in Beta before general release and this is where the first few version number went.
8.0.3 was only released to Android to correct a label position that occurred after a second nav plan was started and did not impact the operation of the product just a minor display issue.
8.0.4 - 8.0.8 were all background Alpha & Beta testing releases completely related to adding device support for Android AI boxes using CarPlay.
8.0.9 - 8.0.11 an update to the download auto syncing system, hiding of place elevation if it was not defined and some auto sync messaging changes to make it more obvious for new users.
8.0.12 was related to iOS 16.4.1 which made a breaking change to background GPS operation this was urgent but also at the same time we did a position adjust to the output of the odometers it now overlays its own button and does not go to the top of the screen. We also updated the sql database drivers as some android devices on api > 33 were reporting a problem that was only event in logs.
8.0.13 was an update to the notifications driver as there was an update in Android API > 33 that was causing a problem when a notification was received. This was an urgent update as it had effected 10 users (of 6K Android devices).

There has not been a single fix in any of the above that would stop the app running on 99% of all devices but some additional device types are now supported and all will be working better.

In addition, we have NO support issues at all for any "blue screen", "white" screens or any other screens.

This is not the first issue where you have posted as if you are an authority on our product yet you have no idea of the facts and are making misleading public comments.

David

PS: the OP of this post has had his issue resolved after receiving advice by Michelle to uninstall/reinstall when he went to the Help Desk to ask the question.