I am encountering an issue with S3 image upload functionality using the imageInput component, which seems to have started affecting multiple mobile apps across all devices in our team.
While the image upload works correctly within the editor on desktop, mobile uploads are resulting in a text file being uploaded to S3. The file contains a string like the following:
Additionally, I have noticed that the value of the image input differs on mobile compared to the desktop. Is this behavior expected, or could this be related to the issue we're seeing? (See the screenshots)
Same issue here with Google Cloud Storage Bucket.
On mobile : the files[0].uri value is a string containing the image path in cache.
On desktop : the classic blob structure remains.
Any solution to read this local image and upload it on S3 or similar? Can't figure it out neither.
Converting the file to base64 on the device and then uploading but this seemed to be slow and crashy.
What I have noticed is uploading to retool storage still seems to work (only from the checkbox in the imageInput, a retool storage query has the same issue as uploading to any other cloud storage). So theoretically if there is a way to access the file key used when the file is uploaded to retool storage maybe you could pass it to a workflow and upload it from there? Not ideal but just spitballing.
