AppReviewX Log in

Image and file upload testing checklist

Large, wrong-format and interrupted uploads, permissions and progress feedback.

In this guide

Uploads fail in ways a Wi-Fi test on your own phone never shows. Use this list on at least two devices and one slow or unstable connection. Each item says why it matters and how to check it.

Before the upload

1. Permission prompt and denial Why: users often say "no" once, and the app must not dead-end. How to check: fresh install, tap upload, deny. Is there an explanation and a path to settings? Then grant and retry.

2. Limited photo access Why: current Android and iOS versions let users share only selected photos (check each platform's current docs); the picker must still work. How to check: grant access to a few photos only, open the picker, upload one, then try to find an unshared one.

3. Camera vs. gallery Why: two code paths, two sets of bugs (orientation, cancelled capture). How to check: take a new photo, pick an existing one, and cancel both flows halfway.

The file itself

4. Large files Why: out-of-memory crashes and timeouts show up here first. How to check: upload the largest photo or video you have. Watch for crashes, a frozen screen or a silent failure. If the app has a size limit, test one file just under and one over it.

5. Wrong formats Why: users upload what they have, not what you expected. How to check: try a PDF, a screenshot, a HEIC or WebP image, a renamed file (text file called .jpg) and an empty file. Expect a clear message, not a crash or a broken thumbnail.

6. Orientation and metadata Why: rotated or mirrored previews look like bugs to users. How to check: upload portrait and landscape photos taken on the device; compare preview, uploaded result and what other users see.

7. File names Why: special characters can break storage paths. How to check: use a name with spaces, accents, an emoji and a very long name.

During the upload

8. Progress feedback Why: without it users tap again and create duplicates. How to check: use a throttled connection. Is there a progress indicator, can the user cancel, and does the button disable?

9. Interruptions Why: this is the most common real-world failure. How to check: during an upload, switch to airplane mode, lock the screen, take a call, put the app in the background, kill it. Afterwards: does it resume, retry or fail with a clear message? See also interruption tests.

10. Multiple files Why: partial success is hard to display honestly. How to check: select several files where one is invalid or too large. Is the result per file clear?

After the upload

11. Duplicates and retries Why: a retry after a timeout may create two copies. How to check: cut the connection right at the end of an upload, retry, and check the result on the server side or another device.

12. Result visible and removable Why: users must be able to confirm and correct what they sent. How to check: reopen the app, check the uploaded item is there, delete or replace it, and confirm it is gone.

Want other people's devices and connections on your upload flow? Start here and get structured, private feedback.