- Docs
- Resources
- Agent Pool & Device Farm
- App Library
App Library
The App Library holds your company’s mobile builds. Runs on Device Farm devices install the build you pick from here, and admins can install it on devices by hand.
In short
On this page you can
- Upload an APK, AAB, IPA or iOS simulator
.zipwith Add application. - See each app’s package id, version, size and who uploaded it.
- Replace a build with a new version without creating a second app.
- Fix a missing package id or bundle ID, or give an app a readable name.
- Install a build on one or many farm devices.
How to use it
- Open Device Farm › App Library (Admins can change it, users can read it).
- Click Add application, drop the file and click Upload.
- Check that the row shows a package id; if not, fix it in App details.
- For a new build, expand the app and use Replace app.
- Pick the app in your Device Farm run settings, or install it from Devices.
Who can change it
Admins add, replace, rename, fix and delete apps. Users see the same list read-only; an empty library tells them “No apps yet. A company admin can add apps to the App Library.” The library belongs to your company: other companies never see your builds. It needs the Device Farm right (What you see).
Upload a build#
Add application
Click Add application. If the library is full you see “App Library is full — update an existing app or delete one to add a new app.” instead.
Choose the file
Drop the file on “Drop an APK, AAB, IPA or simulator .zip here”, or click to choose it. The dialog shows the file name, size and the platform:
.ipaand.zipare iOS,.apkand.aabare Android. Remove clears the choice.Upload
Click Upload. The dialog shows “Uploading and parsing…” while the file is stored and its details are read.
“file name: added to library”. The row shows the package id (Android) or bundle ID (iOS) and the version read from the file.
| File | Platform | Use it for |
|---|---|---|
.apk, .aab | Android | Android phones and emulators |
.ipa | iOS | Real iPhones and iPads (an .ipa cannot be installed on a simulator) |
.zip of the .app folder | iOS | iOS simulators |
Any other file type gives “Only APK, AAB, IPA or simulator .zip files can be uploaded.” If the details cannot be read, the upload still finishes with the warning “App details (package/activity) could not be read — they can be entered manually at run time.”, and the row is marked “package id could not be read”. Fix it as described in Fix app details.
The Release notes (optional) field in the upload dialog is not stored with the app today.
The list#
- The strip at the top counts Applications, Versions and Android / iOS, shows the total size stored, and warns “n app(s) missing package id” when some rows have none (how they are counted).
- Search app / package… matches the display name, file name, package id and platform. The platform filter (All, Android, iOS) is remembered in this browser.
- Columns: Application (name and package id), Platform, Latest version (version, LATEST, size and uploader), Versions, Updated, and the App details icon.
- Expand a row for Version history. Admins find Replace app and Delete there.
- Export: Filtered results (.csv) or All apps (.csv). Refresh reloads the list.
Upload a new version#
Each row is one app with exactly one stored build. A new build replaces the old one, so pipelines that use the app get the new build without any change.
Expand the app
Click the arrow at the start of the row.
Replace app
Click Replace app and choose the new file. The same upload dialog shows the progress.
“file name: new version uploaded”. Package id, activity and version are read again from the new file; the upload date and uploader change, the first upload date is kept.
Replace instead of adding again
Adding the same app again creates a second app and counts against the limit of 30 apps. Replace keeps one app per product and platform.
App details, rename and export#
The App details icon opens the app’s record: Application, File name, Package, Platform, Version, Size, Uploaded, Uploaded by, URL. Export gives Metadata (.csv), Metadata (.json) or Copy as text.
Admins can rename the app (tooltip “Rename - the file name stays unchanged”). The new name is only a display name; leave it empty to show the file name again.
Fix app details#
The package id (Android) or bundle ID (iOS) tells the run which app to open. When it is missing, runs may open the wrong app. Admins fix it in App details:
Check the platform
Set Platform to Android or iOS. A wrong platform is the usual reason the id could not be read.
Enter the ids
Fill Package and App Activity (Android) or Bundle ID (iOS), and the Version if you want. “The file itself is not changed.”
Save
Click Save.
“App details updated”. The warning on the row disappears.
Platform Android
Package com.example.shop
App Activity com.example.shop.MainActivity
Version 4.2.0Delete an app#
Expand the app and click Delete. Confirm “Delete this app?”: “It will be removed from the App Library. Runs that selected it will no longer install it.” Check your Device Farm pipelines in Schedule first and pick another app there.
Install on devices#
Runs install the selected app on the device before they start; you do not need to install it by hand. Install manually when you want to explore a build live or prepare devices.
| Where | Installs on | Who |
|---|---|---|
| DevicesUse deviceInstall App | That device (“Install app on device”) | Admins and on-premise users |
| DevicesBulk install app | The devices you pick (“Install app on devices”) | Admins |
Pick the application
Search with Search application / package…. Apps without a package id are marked “no package id”.
Pick the devices
Choose by Nodes or Devices, with Select all, Clear, search and Filter by tags. Devices of the other platform are marked “wrong platform” and cannot be picked.
Install
Click Install. Each device moves through Sending… → Queued → Installing… → Installed or Failed.
“Installed on all devices”, or “Finished with errors” with Retry failed.
A device that does not answer within 6 minutes is marked “timed out — no result from the device”. On-premise users can only install builds that are in the App Library.
Use the app in runs#
When a run targets the Device Farm, you pick the app per platform from this library in the run settings (in Automate for a dry run, in Schedule for a pipeline). Package and activity are filled from the app’s record. The build is installed before the run and skipped when the same version is already on the device.
If something goes wrong#
Didn’t find your answer?Write to support with your project name and what you see on screen.
info@smartestqa.ai