Unanswered

Upload from iOS prefers cached item if filename is similar

(0) Share

Report

Posted on by hjaf

487

I think this is a bug, but would like to know if anyone can reproduce this and perhaps suggest a workaround or tell me if I'm doing something wrong 🙂

Issue:

My app is communicating with sharepoint lists and it is sometimes used to upload attachments to a list item. If a file has been previously uploaded with the name e.g. 'Summary report.pdf' to another item, the old file is persistent when attempting to upload a new attachment to another list item as long as the name is the same.

I have only tested/experienced this using the same list.

This seems to be only affecting powerapps running on iOS, the behavior is not present using a browser on a computer.

Reproduction steps on iOS "pictures of animals" example:

1. List: "Animals" -> Item: "Dog" -> Upload picture of a DOG named 'Picture1.jpg' to item attachments

2. List: "Animals" -> Item: "Cat" -> Upload picture of a CAT named 'Picture1.jpg' to item attachments

Result: Item: "Cat" attachment "Picture1.jpg" is a picture of a dog ;(

If using a picture to test on iOS, the picture must be saved with "Files" in different folders for the filenames to be identical. Use the file browser on iOS when uploading the attachments.

Hints:
Clearing the cache on the iOS PowerApps-app, seems to correct it.

I suspect that this issue is known by the developers, because when attaching images from iOS pictures the attachment naming convention is UUID by default.

Categories:

Building Power Apps

All responses (2)

Answers (0)

Sort by

v-xida-msft Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

HI @hjaf ,

Could you please share a bit more about your scenario?

Do you mean that the IOS device could not upload a image file with same file name as previous one, instead of, it would upload the same image file from the app cache?

Based on the issue that you mentioned, I think this issue may be related to app cache. Please consider take a try to turn off the "Optimize images for upload" functionality within your PowerApps Mobile App in your iOS device, then try it again, check if the issue is solved.

If the issue still exists, please consider share the Session ID of your PowerApps Mobile App, then we could do some investigation on it, and provide a proper workaround for you.

More details about getting Session ID of an app, please check the following article:

https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/get-sessionid

Best regards,
hjaf 487 on at

Like
a
(0)

Report
Copy link

Link copied!

Question: Do you mean that the IOS device could not upload a image file with same file name as previous one, instead of, it would upload the same image file from the app cache?

No, as mentioned, it is successfully uploading a file(not necessarily an image). However, It seems to upload a cached version of the file if the selected file has a filename identical to a previously uploaded file on that device. There is no indication about anything going wrong, and the wrong file is uploaded.

Again, this is not only for images, as described in one example i use a PDF named "summary report.pdf". The dogs and cats example was just to simplify, but replace them with PDFs and the same thing happens. I have already tried disabling optimize images for upload without it making a difference for images, but again, its not only concerning images.

Reproduction steps on iOS "Animal reports" PDF example:
1. List: "Animals" -> Item: "Dog" -> Upload PDF-report about a DOG with a file named 'Animaldescription.pdf' to item attachments
2. List: "Animals" -> Item: "Cat" -> Upload PDF-report about a CAT with a file named 'Animaldescription.pdf' to item attachments

The "Cat" item now contains the Animaldescription.pdf that was ment to be uploaded only to the "Dog" item.

This issue has been reproduced from several iOS devices by different users. I Tested using PowerApps version 3.19041.12, but this has obviously been happening for some time using earlier versions of PowerApps on iOS.

Note: Tests done with PC (browser) do NOT produce the issue, indicating that is not app-specific as the behavior is as expected on the PC. Clearing the cache in PowerApps on iOS seems to temporarily fix the issue.