Most Common Upload Errors
By Afrah Saleem · · 4 min read
Most upload errors on AppForShare come from four causes: the file is not an .ipa or .apk, it is larger than your plan allows, it is not a complete and valid app package, or (for iOS) it was built for the Simulator or signed for the App Store. The fix is usually to export the build again with the right settings.
Below are the errors you may see, what they mean, and how to fix each one. A related problem is a build that uploads fine but will not install; that is covered at the end.
"Only .ipa (iOS) and .apk (Android) files can be uploaded."
AppForShare accepts two file types: .ipa for iOS and .apk for Android. Common causes of this error:
- Android App Bundle (.aab): bundles are for Google Play and cannot be installed on a phone directly. In Android Studio use Build APK(s), or generate a universal APK from your bundle with Google's bundletool.
- A zipped .app or .xcarchive: export an .ipa from Xcode instead (see below).
- A renamed file: the extension must match the real content. A .zip renamed to .ipa will fail the next check.
File too large
Each plan has a maximum file size. If your build is over the limit, the upload stops with a message that names your limit and the plan that takes larger files.
| Plan | Max file size | Storage |
|---|---|---|
| Guest (no account) | 50 MB | n/a |
| Free | 150 MB | 2 GB |
| Pro | 2 GB | 25 GB |
| Team | 4 GB | 150 GB |
If the file fits but the error says the upload would go past your storage, delete old builds you no longer need, or move to a plan with more storage. More on this in File size and upload limits.
"The file is not a valid archive."
Both .ipa and .apk files are ZIP archives inside. This error means AppForShare could not open the archive. Usually the file is incomplete or damaged: the download from your CI server was cut off, the file was copied while still being written, or it was modified after export. Export or download the build again and upload the fresh copy.
"This is not an iOS app: Payload/*.app/Info.plist is missing."
A valid .ipa contains a Payload folder with your .app bundle and its Info.plist inside. If you zipped the files by hand or zipped the wrong folder, this structure is missing. Export the .ipa from Xcode instead of building the archive yourself:
- In Xcode, choose a real device or Any iOS Device as the destination (not a Simulator).
- Choose Product, then Archive.
- When the Organizer opens, select the archive and click Distribute App.
- Pick a method that supports installs outside the App Store: Release Testing (Ad Hoc), Enterprise, or Debugging (Development). Names vary slightly between Xcode versions.
- Export and upload the resulting .ipa.
If you get "Info.plist could not be read", the plist inside the app is damaged. Clean the build folder and archive again.
"This is not a valid Android APK"
AppForShare reads the Android manifest to find the package name, version and icon. If the manifest cannot be read, or there is no package name, the file is not a usable APK. Rebuild it from Android Studio or your Gradle task and make sure you upload the final .apk output, not an intermediate file.
The upload works, but the build will not install
AppForShare does not sign or re-sign builds, so the signing in your file is what the device sees. On iOS, check these first:
Missing embedded provisioning profile
Every installable iOS build contains a file called embedded.mobileprovision inside the .app bundle. It lists the team, the app ID and, for Ad Hoc and Development builds, the device UDIDs allowed to run it. iOS checks it at install time. It is missing when:
- The build was made for the Simulator (the
-iphonesimulatoroutput). Simulator builds have no profile and cannot run on a phone. Use the-iphoneosoutput. - Code signing was turned off or misconfigured. Check Signing and Capabilities in your target settings.
Wrong distribution type
Builds signed for App Store distribution, including TestFlight builds, cannot be installed from a link. Export with Ad Hoc, Enterprise or Development signing instead.
Device not in the profile
For Ad Hoc and Development builds, the tester's UDID must be in the profile. Testers can get it with the free UDID finder. After you add it in the Apple Developer portal, sign and upload the build again.
For more install problems, see Can't install an app on an iOS device and Solving common app build upload issues.
Frequently asked questions
Can I upload an Android App Bundle (.aab) to AppForShare?
No. AppForShare accepts .apk and .ipa files only, because a phone cannot install an .aab directly. Build an APK, or create a universal APK from the bundle with bundletool.
Why does my .ipa say Payload/*.app/Info.plist is missing?
The file does not have the structure of an iOS app package, usually because it was zipped by hand. Export the .ipa from Xcode through Product, Archive and Distribute App.
What is the maximum upload size?
Guest uploads can be up to 50 MB, Free up to 150 MB, Pro up to 2 GB and Team up to 4 GB.
My iOS build uploaded but testers cannot install it. What should I check?
Check that it was signed Ad Hoc, Enterprise or Development (not App Store), that it is not a Simulator build, and that each tester's UDID is in the provisioning profile for Ad Hoc and Development builds.
