Just as the title says, so far this has happened twice. I turn on airplane mode, do not disturb (to save battery, I have been doing this for months and not ran into a problem.) but recently, it says its recording, the miles show up, as well as the time since I started, the camera button shows up red, but when I stop the recording and look at my captures, it’s not there. I recently got coverage on around 4 uncovered streets, but the coverage glitched. Thankfully today, I was recording with my GoPro also, so it wasn’t as big of an issue. If anyone knows why this is happening and how I can fix it, it would be a great help.
1 Like
Thanks for the report; that’s an interesting one. So, to trace your steps, you have enabled Do Not Disturb and Airplane modes, and then you’re opening the Mapillary iOS app and starting capturing. Am I correct here?
cc @Anders
__
BR, Yaro
Yes that is correct.
1 Like
Thanks for reporting, I’ll look into it!
2 Likes
Thank you, if it happens again, or stops ill be sure to write in the replies of this topic.
1 Like
It happened again earlier today, thankfully, I checked the map. I was able to see my phone was not recording (even though Mapillary said it was) and was able to restart the app, then it worked fine! It seems (so far) that this is only affecting the first captures of the day, but I will update if anything changes.
1 Like
Quick question, when this is happening, is the app in the foreground and the phone is not locked?
Yes, the app is open and the phone is unlocked.
1 Like
Hello! I would also like to report the same behaviour of Mapillary “losing” sessions in the sense that it shows recording but doesn’t save the. I do not use airplane mode or dnd while capturing and I’m connected to mobile data. I am however on the TestFlight 6.1.0 version of Mapillary as I find the “needs captures” layer very useful. I have lost both first captures for sessions and intermediary ones. Due to the randomness of when it decides to not save them, I have started chunking my captures when I’m walking around the city.
1 Like
I have kinda got the hang of my glitch. For me when it only captures a few images then stops, or doesn’t start at all, I have to restart the app. (The map will show they are recording if I start and stop the capture but it will not save) I have made it habit to check if I am recording now, and I have my GoPro Max2 on single lense mode most of the time as a protector if it glitches (but the quality is less)
Is this the same thing you’re experiencing?
My process is I press the start button to check if it has turned red, walk for a kilometer on a planned route based on the needs capture map layer, check if the button is still red, press it again to finish the capture and then press the X to go to the home screen and check if the recording has actually saved.
I had initially confused this bug with me not starting the capture. The app has the “tilt phone up” warning and when it’s active it doesn’t start the recording when you have pressed it. However it still plays the haptic feedback as if you’ve successfully started it which is what messed me up.
I don’t believe I experience the exact same issue as you’re describing because my recordings show all the red dots of the taken photos on the preview map(before saving and exiting the capture screen).
On some captures I also manually take individual images (for example shop opening times) via the button for that or usually via my headphone’s or phone’s up/down volume buttons(shortcut that works in the camera app too). On instinct I thought that this could be the issue, but I’ve also lost captures that are fully automatic.
All captures are with a fully unlocked phone and the Mapillary app isn’t exited from, nor is the control center accessed.
1 Like
cc: @Anders - do you have ideas?
Thanks for the bug reports! Sorry to hear you are experiencing these bugs, I’ll look into it again and see if I can replicate the issues now that I have more information.
1 Like
I forgot to comment on this. The “needs capture” layer is available in the production version, it also has a bunch of bug fixes compared to the TestFlight version.
2 Likes
Just a quick update before I sign off for the day. I spent a few hours debugging today, I tinkered with
- Weak (although simulated) GPS and tilt recovery
- Rapid stop/exit
- Background camera interruption
- System-kill relaunch
- Cold-start capture timing
Unfortunately, I wasn’t able to reproduce the errors described in this thread. I will test on another and older device tomorrow (iPhone 11 Pro).
What devices do you use, and which iOS version?
I’m on an iPhone 17 running iOS 26.2.1 (23C71). I’ll try to check if I have the same issue on the non TestFlight app. Would a full screen recording be helpful(assuming the issue occurs)?
1 Like
Thanks! Sure, if you are able to record a video when it happens, it would ofc be useful!
I forgot to ask, assuming everything was working all the time before, do you guys have any rough idea of when the issues started happening?
It would help me narrow down what could have caused the issues.
I use iPhone 14, and am running 26.6.1
For me, issues started around the end of August of this year