Install apps on multiple Android devices with Swarmbot: APK, APKS, progress and failures

Select target devices on the Swarmbot device wall, then upload or choose an APK or APKS from the dock. Swarmbot tracks transfer and installation progress per device and automatically reduces concurrency for large packages.

Swarmbot can send one APK or APKS installation job to multiple selected Android devices and keep showing the transfer and installation state of each device. It is designed for people maintaining work phones, test devices or store devices: validate on a small sample, then expand the same job without opening every stream window.

Start on the Swarmbot device wall. Filter and select the target devices, then open Install App from the dock. You can choose an existing package from the apks library or drag an .apk or .apks file into the dialog to upload it.

Expand a batch in three steps

Do not begin by selecting every device. A safer rollout is:

  1. Choose one or two representative devices. Include different Android versions or models when they matter, then confirm that the app installs, launches and preserves the data you need.
  2. Run a small batch. Check that network, USB and ACC devices can all finish, and learn how long the package takes to transfer.
  3. Expand to the full target set. Use groups, filters or box selection before submitting the job. Do not include filtered-out, offline or unrelated devices.

The point is not to install on fewer devices forever. It is to stop one bad package from reaching the entire fleet at once. For the broader rollout method, see planning a multi-device workflow in Swarmbot.

APK and APKS are not interchangeable

A regular APK is usually one directly installable file. An APKS file is an APK Set Archive that can contain the base APK, feature modules and configuration APKs for CPU architecture, language and screen density. Android's official bundletool documentation explains that deployment selects the combination required by the target device rather than installing only base.apk. Read the Android bundletool documentation

Keep the complete APKS archive when installing it through Swarmbot. Extracting only base.apk can leave out required splits: the file transfer may finish while the app still fails to install or launch. If you first need to identify the package type, read APK vs APKS: why base.apk may not be enough.

Updates also depend on signing identity. Android compares the certificate of the new build with the installed app and only accepts it as a normal update when the signing relationship is valid. Android app signing documentation Repeating the same failed installation does not fix a signing mismatch. Confirm the package source and signing key before deciding what to do with existing app data.

You do not have to keep the installation dialog open

Swarmbot runs a batch installation as a background job. Submission means the job was accepted; it does not mean every device has finished. Recent Tasks in the dock continues to show overall progress and separates queued, transferring, installing, completed and failed devices. Closing a stream window does not erase the installation job.

Watch three things:

  • how many devices have completed and how many are still queued;
  • whether the active device is transferring the package or installing it;
  • whether failures are concentrated on one model, connection type or error.

If only a few devices fail, fix and retry those devices instead of reinstalling on the successful ones. This avoids unnecessary updates and repeated package transfers.

Why a 200 MB package does not use maximum concurrency

Swarmbot reduces effective concurrency according to package size and device channel so several large transfers do not overload accSys or the network path. In the current released version, requested concurrency is capped at 6, packages of at least 100 MB run at up to 3 effective workers, and packages of at least 200 MB run at up to 2. ADBG and direct accSys network transfers also share a smaller global transfer limit.

A queued device therefore does not automatically mean the job is stuck. With a large package, finishing two stable transfers before starting the next devices is often faster than making many devices reconnect after partial uploads. Status polling also slows down for large fleets, so the UI does not need to refresh the whole list continuously.

Diagnose the stage, not just the words “installation failed”

Use the stage to narrow the cause:

  • Transfer has not started: confirm that the device is online and that its accSys connection is healthy. Swarmbot's device-wall diagnostics can create a support report when needed.
  • Transfer was interrupted: check whether the failures are limited to network devices, large packages or one access point. Do not immediately resubmit the job to every device.
  • Transfer finished but installation failed: check for missing APKS splits, signing mismatch, Android compatibility and free storage.
  • Installation finished but the app is not ready: installation only proves that Android accepted the package. Login, permissions and business setup should be verified as separate automation or script steps.

If the device connection itself is unstable, return to the Swarmbot USB, Wi-Fi, ACC and shared-device connection guide before retrying the installation.

External AI and business systems should use the asynchronous job

Swarmbot Local API exposes asynchronous batch installation. Submit device_install_package to receive a job_id, then query device_install_package_status until the job reaches a terminal state. For very large fleets, a selector can describe the current online group without expanding hundreds of internal device IDs in an AI conversation.

The essential rule is: an HTTP response is not the installation result. An external AI, n8n flow or business system should save the job_id, poll at the interval returned by the API, and inspect failed devices at the end. It should not hold one HTTP request open for many minutes or create a new job merely because a client-side timeout occurred. The exact schema is available in the Swarmbot client documentation and the developer entry.

A practical routine

  1. Put a package with a confirmed source, version and signing identity in the apks library.
  2. Select the target group or filtered set on the device wall.
  3. Install on representative devices and confirm that the app opens.
  4. Expand the batch and monitor Recent Tasks.
  5. Retry failed devices only and keep their error details.
  6. Run login, permission and initialization steps as a separate script or automation, recording results per device.

Swarmbot's value here is not forcing a hundred devices to transfer at maximum speed. It is turning one installation into a controlled multi-device job with visible results. Validate first, expand deliberately and handle outcomes per device.

参考来源