I will release a separate Open Testing version with a quick fix, then work on a clean solution afterwards.
–
BR, Yaro
1 Like
@Lowiekse I have released 2026.01.16-6.11.30 (will be shortly available; Google is checking it) with a single fix for Dev Settings. I didn’t remove them, but I think I’ve discovered a problem. If I’m not mistaken, you were able to see dev settings only for a short period of time upon installing a new app version (or re-installation). This one was fixed.
I still don’t have any idea why you had 1 image per sequence, and I hope they were somehow connected.
Let me know if you face any of those issues in the new release (will be available only in Open Testing for now).
–
BR, Yaro
1 Like
And another follow-up on 1 image per sequence. @Lowiekse, am I correct with the assumption that you’ve hit the limit when you had many sequences with 1 image only? Please let me know, if you remember (or if you don’t).
Uploading 1k images as a sequence will be almost an equivalent of uploading 1 image sequence. Which means you might hit a limit, because you were uploading many sequences (not images though).
If dev settings fix the 1 image problem, it might have side effects of you not having an API rate-limit issue.
–
BR, Yaro
Hi Yaro,
Thats correct.
BR Louis
I have had the dev settings on one of my devices for several days now.
I also see that, due to the dev option, my uploads of approximately 60 kilometres of recordings amount to over 15 GB.
The latest app (2026.01.16-6.11.30) should already be available to you. If you have nothing to upload, try reinstalling the app (delete and install the latest build from open testing) — you should no longer have the issue.
I haven’t been able to reproduce it myself to confirm the fix, but I found an issue and removed it. If nothing is hidden behind, then everything will be shiny from now on 
Why reinstallation? Because the app has a cache for some flags, and I wanted to have a clean fix instead of introducing more logic to handle the cache.
—
BR, Yaro
About 15 GB; it’s not about dev settings—something else has to be there. We don’t capture more images (unless this flag is tagged) or change image quality or capture raw data.
Did you find this 15GB note in the Mapillary app itself or a folder size from a file explorer (or another tool you’ve been using)?
–
BR, Yaro
The Mapillary app itself indicates that there are 15 GB of photos. Uploading also takes an extremely long time and the app displays ‘Waiting for Wi-Fi’. This happens even though the upload is taking place. The device also has a working Wi-Fi connection. I only encountered this problem on the device where the dev options were available.
BR Louis.
1 Like
I will do this. Also because, as I already mentioned, only this device is causing problems. I will keep you informed.
BR Louis.
1 Like
Thanks for your input. Now I can confirm that the issues with the uploader (Desktop) was caused by the issue on Android, where each image was packed in its own sequence.
I haven’t been able to figure out why you had this definitely, but I have one last assumption (more or less strong). Did you upload data captured (1 image per sequence) by Mapillary Android app with Desktop Uploader?
–
BR, Yaro
Yes, I did because the Android app was stuck.
tl;dr everything was fixed
Ok, now everything makes sense. Android (only one specific app version) was packing images into different folders if the images were taken more than 1 second apart. In the app, they’re still one sequence and they’re uploaded as one sequence. But if you plug this to DU, then it reads it as multiple sequences, and hence the capture rate is around 1 image per second—you get many 1-image-per-sequence sequences.
This triggered rate-limiting because that was too many sequences (but not images). Everything was fixed, and you should never face this again.
–
BR, Yaro
1 Like
Importing pictures felt awkward, I did it a few times wrong. I looked how to do it in the manual.
It is especially the meaning of “select” that bothers me. Is it according to the Android UI design guidelines. ? I think users should just select and then click on “Done”.
Hi @filipc, regarding import and “awkward,” I tend to agree, especially when you add existing limitations there. I will try to bring a bit more details which might help at least to understand why it is what it is.
First of all, Android has multiple ways of importing files into the app, and options are around: shared by you Photo Picker, MediaStore, SAF.
You’ve shared a PhotoPicker approach and it is good for images, but only for a few (as you must pick them one-by-one) and it doesn’t provide an image location (they have a task on the Google tracker somewhere about that, and tl;dr it wouldn’t be fixed). And I bet it will crash the app if you are patient enough to select 2k+ images one-by-one. So, this one is a clean no-go for us.
All other methods are more general-purpose (not image-oriented), but they also work for images and preserve an image location. At the same time, one might face other challenges, like the limit of files for IPC transfer if you use a separate app for a picker, and there’s no way to fix it from our side.
And regarding “select,” that’s a separate app, which doesn’t belong to Mapillary and we don’t have much control (if any) over it.
So, for our image picker, it is up to guidelines, to my best knowledge.
–
BR, Yaro