File Provider Extension App Review checklist

Define domains, roots, and item identity

List each account, team space, root folder, shared drive, offline area, and file type the provider exposes. Stable item identifiers are critical because the system and user expect files to persist across launches.

If account switching changes the file tree, verify old domains disappear and new domains appear without leaking prior account names or thumbnails.

Test every file state

• Available online only, downloaded, pinned offline, uploading, and failed upload.
• Renamed, moved, deleted locally, deleted remotely, and restored remotely.
• Conflict after edit on two devices.
• Quota full, permission denied, account expired, and no network.
• Unsupported file preview, large file, package directory, and shared file.

Protect filenames, thumbnails, and account context

File names and thumbnails can reveal private customer, legal, health, school, or workplace data. Avoid logging or analytics capture of raw filenames unless strictly necessary and disclosed.

AppReviewReady interpretation: test the extension from Files, document pickers, share sheets, and the main app. Privacy behavior must be consistent even when the main app UI is not visible.

Give review a sample file tree

1. Create a review account with a small, named file tree.
2. Open Files, browse the provider, download a file, edit it, and save.
3. Trigger an offline state and a conflict state.
4. Delete or rename a file remotely, then refresh the extension.
5. Verify sign-out removes file access from system surfaces.

Document File Provider behavior

The reviewer should not need a production storage account. Keep sample files fictional and small enough to test without long downloads.

After launch, monitor enumeration errors, file-version conflicts, and provider crashes separately from ordinary app errors. A broken provider can make the system Files interface look unreliable even when the main app still opens.

If the provider exposes team or organization folders, test role changes and removed membership. The extension should stop showing files when server permissions change, even if local metadata is cached.

For regulated or enterprise storage, verify managed devices and personal devices do not see the same file domains unless policy allows it. File visibility is a permission decision, not just sync state.

Also test very small file lists and very large file lists. Empty folders, thousands of items, and slow server pagination should all give the reviewer a stable result instead of a spinner that appears to be a crash.

File Provider review path:
Provider domains: [personal/team]
Sample files: [names]
How to access: [Files app path]
Offline behavior: [download/pin]
Conflict behavior: [message]
Sign-out behavior: [removes access]
Private data logging: [none or fields]