All of our users are on white-labeled Android apps.
Same issue here, will these pictures be lost, or will we be able to recuperate them??
We’ve rolled back our changes.
What this means for now:
- You should be able to upload new images and files without seeing this issue now
- Records that were affected, e.g. because the image or file was uploaded, will still show the warning triangle.
We’re investigating how to recuperate the images and files that are affected.
great job, thank you for your support
@Arthur_Rallu, initial testing on our side shows that things are working again. Thank you!
Any Idea if the images taken before the fix are lost or can be saved??
We’re still investigating if that’s possible.
If we find out it’s not possible, you would have to re-upload images and files to the impacted records. It might be faster to do that in some cases.
We’re not able to automatically and completely retrieve all the images for you. However, we’ve managed to put in place a manual process that lets you finish the upload of the pictures and files. It’s not optimal but this is what we’re able to do today.
First I’ll give the instructions on how you can recover the pictures and files, then I’ll explain what is happening.
Manual steps to recover your images:
- Open the app that has some problematic records, ie records for which the image was not uploaded to your data source and for which your DB/spreadsheet will show the funny name of your image/file.
- For each problematic record, edit it and update just one field but not the picture/file field, and save the record.
- For the first record, I’d check in my data source that the image is there after the sync, and that the image also shows up in the app
- Move on to the next problematic record and repeat step 2.
So what’s happening?
As you’ve noticed, the image and filename got a funny name in your DB/spreadsheet and your images & files were not uploaded to your data source. The images & files are supposed to be uploaded to a temporary storage and then to your data sources. However, the second step did not happen. By editing a problematic record, your app will again signal to update the image/file and the process will resume where it left off. As the intermediate storage is temporary, I recommend you take care of updating these records quickly.
Our apologies for the issue this has created.
Thanks for the time and help for the images are showing now.
Hi! I’ve noticed this started happening for all our apps today and the manual solution outlined above is not working…
I am starting to experience this same issue across all the applications. It appears to display the image fine for some records and not others. Even for newly created records, the image displays ok to start with in a Card view, then displays the warning triangle the next time. Click on the detail view shows the image correctly.
I have checked the database (MySql) for the odd looking entry mentioned by @Arthur_Rallu and in the database and there is nothing unusual about the entry referencing the location for the image.
Since this problem persists, is there a better way of handling images as a Blob in the database, rather than as a file?
@Arthur_Rallu Could we accomplish this with a quick update (re: Quick Update System - How to update records in your app with a push of a button)
- Looking for confirmation that the “form view” is not required for this to happen.
Arthur’s workaround will equally work with a quickedit vs a form update.
Matt, that said, are you running into the image upload issue?
Started: 9/4/2021 15:49:22
Stopped: 9/4/2021 18:28:12
- Did making an update to the row help?
- What value was saved in the image column of your sheet?
- Would you mind letting me know what is the userID of the user who uploaded the image?
I have the same problem, this happens because of moving the owner of the appsheet, the image file is not saved. when the owner of the appsheet is returned to the first owner the image still does not appear when input. is there any solution?