opengisch
QField does not start when positionig background service is already running
What is the bug or the crash? What were your expectations and what actually happened?
On my Samsung Active Tab3 in view mode when I select several features and tap on one immediately in the feature list, the app can become unresponsive quite often. (If I wait some seconds before tapping on a feature in the list, the app does not crash.) This is just the context to describe the following problem.
Then I have to kill the app, but the background positioning service keeps running. After lunching qfield again, the app does not start. It shows the logo in the middle with a white background. If I kill the background service before relaunching the app, qfield starts successfully again.
Steps to reproduce the issue
- Start a qfield project and make sure the background positioning service is running
- Try to crash the app so that it stays unresponsive. (I do not know how to do this on purpose)
- Kill the app
- Check that the background positioning service is still running
- Start qfield again
- QField does not fully start and stays on the logo screen with a white background.
Version
3.7.7
Operating system name
Android
Operating system version
13
Reinstall QField
- [x] I have a fresh install of the latest QField version, but the problem persists.
- [x] Problem can be reliably reproduced, doesn't happen randomly.
- [ ] Problem happens with all files and projects, not only some files or projects.
Additional context
Well, this is a minor thing and should happen only rarely. But may be you can even improve this. For example, by checking if the background service is already running when starting the app.
@bladnor , with the next version of QField (released in December), the positioning [background] service will only be activated when at least one tracking session is active. That should help you a bit?
The problem here probably has more to do with the crashing itself, let us know if you're able to reproduce the crash reliably.
