Fixed bug where the location permission was being asked erroneously on map explore screen
Fixed bug where automatic uploads would not resume when a WiFi connection was restored
Google require us to bump the target Android version to 16 before Aug 31. Please let us know if you find any issues regarding uploading and UI/UX as those areas are the most affected.
Thanks in advance for testing new builds before they go live for everyone!
Perhaps I’m misreading the Google page. What I’m reading is that your app must support at least Android 16. If the app doesn’t support that, it won’t be available to users with Android 16. The app may still support earlier versions of Android.
With this version, uploading still doesn’t seem to be working properly. I’ve had to restart the upload several times and regularly received the message ‘waiting for Wi-Fi’, even though I was connected to my home Wi-Fi.
The only improvement is that I can restart the upload. In the previous version, I had to download the interrupted sequences to my PC and upload them using the desktop uploader.
Right, Google’s app review process and AOSP license for large scale licensees are broken, not the user’s phones or the users themselves. Besides, it is not like nobody could have known or imaged for how long phones can be used and that
they have tons of cryptographic code that may have vulnerabilities
the OS can have bugs and vulnerabilities too
they continue to be used long after production has ended.
However, not only Google is to blame but also regulators too for being passive about requiring vendors to provide at least security updates long after software enabled devices have become EOL. While phones might sound quite trivial, just think about cars, trains, construction equipment, or power plants etc. Apparently, it is gonna have to take disasters for regulators to finally take notice and action. Sadly, this situation is pathologically unbearable.
Anyway, thank you @Anders for further Mapillary app updates.
As things stand, the update seems to be working. I deliberately disrupted the Wi-Fi to trigger it. It takes a long time for the upload to restart, but eventually it does and uploads all the recordings.
Great! Yeah it can take up to 30s for the operating system to detect/forward that the WiFi connection has been restored, but hopefulle you don’t have to worry about having to restart uploads manually.
I had a sequence that had stopped whilst I was on a 5G mobile connection. The upload did not resume automatically after switching to a Wi-Fi connection.
I had to stop the upload by clicking the cross next to the upload bar. I then had to restart the upload manually.
I tried out capturing photos with the app for the first time, but I am unable to take any photos because the app in unable to find a GPS lock (despite the location on the map being correct and all other apps not having trouble finding a GPS lock)
I would think that one should be allowed to start a sequence anyway, perhaps via a manual process with confirmation, if we will provide a separate GPS trace as well. That would allow someone to use it even in an area where their phone didn’t have good GPS reception, but another device did.
Yes, I did check. It has access to the precise location information, and the location is correct on the map, but the app doesn’t “believe” that it has a precise location lock.