Skip to main content
Proton v5

Mobile Apps

Resources > Mobile Apps holds the apps tested by mobile automations and the version history of each one. Versions arrive through the screen, Firebase App Distribution or CI, and when you run a mobile automation you choose the app and the version that goes to the device.

Apps and versions​

Each registered version is an installer (APK, AAB or IPA). Versions with the same package (Android) or bundle id (iOS) make up an app.

At the top, App numbers show how many apps there are (Android and iOS), how many versions are stored, the last version received (and how it arrived) and how many apps receive versions on their own, through Firebase or CI.

The list on the left has the Search by name or package search and the All, Android and iOS filters. Clicking an app opens its details:

  • the latest version, its build and when it arrived, with its source (Screen, Firebase or CI);
  • the Identification: the platform, the Package (Android) or Bundle id (iOS) and, on Android, the Launch activity;
  • the versions, from newest to oldest, with the build, notes, source and date. Each one can be downloaded, edited and deleted;
  • the commands to Receive versions automatically (see below).

Send a version through the screen​

New version (or New version of this app, in the app details) takes the installer: .apk, .aab or .ipa, up to 500 MB.

  1. Drag the file or click to choose it. Proton reads the package, the version and the activity from the file itself.
  2. The screen tells you where the version will go: an existing app (same package), which gets the new version as its latest, or a new app, which is created with it. For a new app, enter the App name, as it appears in the list and when running.
  3. If needed, adjust it in Fix what was read. For an AAB, only the platform is read, and the other fields are filled in by hand.
  4. Write the Notes for this version, if you want, and use Add version (or Create app).

For an app already installed on the device, with no file, use Register without a file and fill in the version, the platform, the package and, on Android, the activity.

Import from Firebase​

With the Firebase integration set up (see Integrations), Import from Firebase brings in an App Distribution release in three steps:

  1. Select App: the apps in the Firebase project.
  2. Select Release: the app releases, with version, build and notes. Releases already imported are marked.
  3. Confirm: review the name, the version and the package, and use Import.

Receive versions from CI​

Receive from CI shows the commands for the pipeline to send each build to Proton on its own, with the API token of an account allowed to register mobile apps, preferably a robot account:

  • From CI: at the end of the build, the pipeline sends the installer, with a build identifier (externalId). The same identifier does not duplicate the version.
  • From Firebase: after distributing on App Distribution, CI asks Proton to import the newest release.
curl -X POST https://app.protoncloud.com.br/api/mobile-app/installer \
  -H "Authorization: Bearer $PROTON_TOKEN" \
  -F file=@app-release.apk \
  -F externalId=build-$CI_PIPELINE_ID

Copy command copies the ready-to-use command.

At run time​

When you run a mobile automation, the device and app step picks the app and the version. See Run.

  • Device on the runner: choose a specific version or Always the latest. With the latest, scheduled runs and recurring runs test the last build that arrived. The automation downloads the run's installer on its own.
  • BrowserStack: the version must be on BrowserStack. With the BrowserStack integration, the versions table gets the BrowserStack column: On BrowserStack when the version has already been uploaded, or Send. The Upload to BrowserStack toggle also appears when you send a new version and when you import from Firebase. When running, the app list comes from BrowserStack.

To set up the machine and the device, see Mobile (Android); for the code, see the Proton Cloud SDK.

Edit and delete​

  • Edit this version changes the name, the version, the platform, the package, the activity and the observation, and replaces or removes the file. Each version has only one installer.
  • Delete this version deletes the version and its installer. The trash can in the app details deletes the app and all its versions. With BrowserStack, the confirmation also offers to delete it there.

Permissions and mobile​

Mobile Apps has its own permissions in the profile: view, create (new version and import from Firebase), edit and delete. Users who can run automations in the Automation Center also see the apps, so they can choose one when running.

The screen is designed for a computer.