Glitchy behavior before GPS is found
OS: Ubuntu Touch Device: Google Pixel 3a
I've tested the app for a while now, and I notice that it's a bit glitchy (meaning that it crashes and closes) if you try to use location-dependent functions (navigation / nearby places) before the GPS signal is found. Would it be possible to disable those functions before the GPS-signal is found? And report to the user on the home-screen that the app is currently searching for GPS?
Pure Maps learns location via QtLocation and is currently showing precision on home-screen (main map) on the top right corner. I expect that your OS shows status of how good is the fix in the statusbar.
Re disabling navigation / nearby: in terms of navigation, there is a scenario where you don't want it to be disabled. as starting driving and letting pure maps to figure out the route when you are already on the way. It may also start depending on OS - such disabling should be done via tracking QtLocation / QtPosition API. I haven't looked into it, but probably there is some flag for it.
I have not seen those crashes, yet. Can you provide more precise info on how to reproduce? And can you provide the app log of such a crash?
The crashes occur mainly before gps signal is found, for example when I’m in the navigation window and try to enter a destination. Here is a log: https://dpaste.com/2Q8JRDV7Z
Is that on Ubuntu Touch 20.04?
Yes this is on UT 20.04
Which UT channel are you on?
The only way I can think of to nail this down further, is for you to debug it, as I really can't reproduce this.
I can't reproduce it anymore either, so I will close this issue. Thanks for looking at it and for this great app!