I have a sequence of 77 images captured a few days ago which has not been uploaded yet. Today came a new release of the app (android app, version 3.50) and when I now try to upload the images it first says “upload in progress, processing sequence 1 of 1” and the counter rapidly goes from 1/77 to 77/77 (in a few seconds). I guess this is some sort of preparation process, I have noticed that this has been fast earlier too.
After that the real upload should start, but then it just says “upload finished”, but the images are still there (not removed) and when I log in to my account at mapillary.com there are no signs of any recent uploads.
Edit: I have the same problem with a brand new sequence. It says “upload finished” without uploading any images.
I stopped using new releases and installed an old mapillary apk 3.14 which has all functionalities I want together with the previous nice layout (indicating distance based or time based capturing). No gpx and no additional processing, no problems when uploading.
I figured every one ran into this.
The way I combat this glitch is to take more pictures.
There is a percentage of any run that comes out as crumbs. These never seem to be seen again.
I looked through my phone.
They are no longer in my memory, either on the SD
Card or the internal memory.
Oh well.
I checked the memory card (SD) and the files are present on the SD, exactly where the settings in mapillary says they should be stored. Image files + gpx file. So why whywhy does Mapillary not upload them?
I’m “happy” to hear I’m not the only one
Since the images still remain on my SD card i uploaded them manually through the website. But then all the photo angles are lost and had to be corrected manually…
““I’m “happy” to hear I’m not the only one smirk
Since the images still remain on my SD card i uploaded them manually through the website. But then all the photo angles are lost and had to be corrected manually.””
Last night something similar happened to me.
I was able to work through their not loading by leaving the app then coning back in.
I had to do this several times. Each time a few would load, then it would say “upload finished”
I’d go out and come back in again, run through all 3,000+ pictures in the pre prep, then load another small hand full.
When I was about ready to call it quits, the remaining 3,000+ all loaded.
Try leaving the app and coming in clean.
Worked for me last night.
@tomastomas Can you please send me the folder with these 77 images to logs@mapillary.com ,and the log after the processing is done? It seems that the info in the images is not matching the GPX track, so I would like to take a look to check on this.
OK here is another weird thing: I just rolled back to v 3.49 and tried to upload again and it is doing the same thing, processing images (counter is jumping around, not in number order) and then not uploading any, guess I will try and roll back further…
““OK, here is another weird thing: I just rolled back to v 3.49 and tried to upload again and it is doing the same thing, processing images (counter is jumping around, not in number order) and then not uploading any, guess I will try and roll back further…””
@tomastomas thanks for the debug data! It seems that some phones are not savingEXIF DateTimeOriginal, and not CreatedDate, only ModifyDate containing the capture time.
I have had the same problem both on Huawei P10 with dozens of sequences.
I’ll try the 3.51 snapshot when I have a chance.
The latest (beta) releases have also been a bit “sloppy” / buggy in taking photos. That is, the app takes pretty long breaks at times from taking photos – and then it seems to play a bit of catch up (taking photos in sort of bursts). I haven’t checked even time stamps, and so obviously not EXIF tags of photos taken.
I did try to change the distance between taken photos (varying between 3, 5 and 10) but that didn’t seem to make a difference.
The newest versions have also had problem with remembering the mode of auto capture, btw. On my device with v.3.50 (and I think the previous, 3.49 I assume) the app resets the mode from distance based capture to time based capture seemingly every time I switch from auto capture to manual and back. (sorry for not posting this finding separately at least for now…).
““The latest (beta) releases have also been a bit “sloppy” / buggy in taking photos. That is, the app takes pretty long breaks at times from taking photos – and then it seems to play a bit of catch up.””
I am seeing this happen too.
I don’t mind unless the long break comes when I pass an interesting building.
I’d like more control over when the frequency increases and decreases. Maybe it would be Nice if the frequency stayed static.
I have always had this problem so I don’t do manual shots often I just kept it on distance based.
Older versions of Mapillary (I use 3.27 due to too many other major issues now) while in distance mode you could touch the screen and it will take a shot manually and add it to the current sequence. It looks like the newer versions with the newer camera GUI no longer does this.
