Prepare mobile builds

Build your app for a simulator or emulator, point it at a test or staging environment, and upload it to Pie. For iOS that’s a simulator .app zipped with ditto. For Android it’s an .apk.

Before you build

Whatever the platform, set these up first.

Environment configuration

• Sandbox or staging environment: Point your app at a test or staging environment, never production.
• Test endpoints: Make sure the endpoints your app calls are reachable from the public internet.
• Test accounts: Create test accounts for Pie, so it never disrupts real users.

Build requirements

• Development tools: Install Xcode for iOS or Android Studio for Android, with its SDK.
• Recent OS versions: Set up simulators and emulators with recent OS versions.
• Custom test files: Get any files your app needs ready. To send them to Pie, see Post-upload requirements.

Upload the build

In Pie, open Builds and select Upload build. Choose your file, enter a Build ID, and select Submit for testing. Use a Build ID you haven’t used before.

Upload an Android build as an .apk. Android App Bundles (.aab) don’t work.

Upload an iOS build as a simulator .app, zipped so the .app sits at the top level of the zip:

ditto -c -k --sequesterRsrc --keepParent YourApp.app YourApp.zip

Selecting Compress on the .app in Finder makes the same zip. Zipping the folder that holds the .app doesn’t work, and neither does an unzipped .app. Pie refuses .ipa files.

Build uploaded means the file reached Pie. It doesn’t mean Pie accepted the build. If Pie refuses a build, such as a device build, the portal shows nothing more, and the build can still be picked under Select Build when you start a run. Builds uploaded through the API return an error for a file type Pie doesn’t accept. A device build inside a valid zip is accepted first and refused when Pie checks it, so the response shows no error.

Need help? Contact support@pie.inc with your platform, the build error messages, and what you’ve tried.