Android Provisioning Studio User Manual
9. Troubleshooting
This chapter covers common problems with device connections, APSBridge, Profiles, Deployments, files, and Logcat.
When a problem affects a specific device, first confirm that the correct device is selected and shown as Online in the APS sidebar.
Device connection problems
Device does not appear in APS
Make sure the Android device is connected using a USB data cable and is unlocked. Confirm that USB debugging is enabled in Android Developer Options, then reconnect the device and select Refresh Devices in the APS sidebar.
Some USB cables provide power only and cannot transfer data. If the device still does not appear, try a known data cable or another USB port.
Device is shown as Unauthorized
An Unauthorized device has not authorized the computer for USB debugging.
Unlock the Android device and accept the USB debugging authorization prompt. APS cannot accept this prompt on the device for you.
After authorization, refresh the device list and wait for the device to appear as Online.
Device is shown as Offline
An Offline device has been detected but is not currently available for communication.
Disconnect and reconnect the device, check the USB cable and connection, and refresh the device list. Wait until the device is Online before running actions or including it in a Deployment.
Devices may also appear temporarily offline while Android is restarting.
Device information and APSBridge
Some device information is unavailable
Device information is loaded when a device is selected, and individual sections may finish loading at different times.
Wait briefly, then select Refresh Device Information from Device → Overview.
The information available can vary between Android versions and device manufacturers. APSBridge can provide additional information where supported, so a missing value does not necessarily indicate a connection problem.
APSBridge controls are unavailable
Some device-management actions require APSBridge and specific Android management capabilities.
Check the APSBridge status under Device → Overview → System and review the requirements shown for the action you want to use.
Having APSBridge installed does not make every managed action available. Supported capabilities can depend on the Android version, device manufacturer, and current device-management state.
APSBridge setup does not complete
Review the message displayed by APS and confirm that the intended device is Online and meets the requirements for the selected setup.
Existing accounts, additional users, work profiles, or another device-management configuration may prevent Android from allowing the requested management setup.
Do not factory-reset a device solely in response to a setup error. A factory reset removes device data and should only be performed when it is an intentional part of the provisioning or recovery process.
Profiles and Deployment problems
A Profile cannot be edited
The Profile may be locked.
Select the Profile and use Unlock before changing its configuration, actions, or action order.
An action cannot be added or configured
Review the action settings and complete all required fields. Check package names, file paths, entered values, and any compatibility or validation information displayed by APS.
Some actions may also depend on capabilities that are not available on every Android device.
Start Deployment is unavailable
Confirm that:
- a valid Profile is selected,
- at least one target device is selected and Online, and
- the Profile contains at least one enabled action.
The target devices selected in Deploy are independent of the device currently selected for direct work elsewhere in APS.
A Deployment fails or stops partway through
Expand the affected device in Deploy and review its action results and Live Log.
If an action fails, APS skips the remaining actions for that device. Other target devices continue independently.
Before starting another Deployment, review which actions were already completed. Correct the device issue or update the Profile as required before repeating the Deployment.
Cancel Deployment does not stop immediately
Cancellation takes effect between actions. An action already in progress may finish before APS stops processing the remaining actions.
Cancellation does not undo actions that have already completed or reverse changes already applied to the device.
Files, applications, and Logcat
A file or APK cannot be found during a Deployment
Check the path configured in the Profile and confirm that the referenced file still exists on the computer running APS.
Moving, renaming, or deleting a referenced file can prevent the corresponding action from completing.
Exporting a Profile stores its configuration but does not include copies of referenced APKs, certificates, images, documents, or other external files. When using the Profile on another computer, make sure the required files are also available.
Access to a device folder is denied
Android restricts access to some system and application directories.
Use an accessible storage location, such as Downloads, when appropriate. USB debugging does not provide unrestricted access to private Android directories.
No Logcat messages are visible
Make sure the device is Online and select Start to begin capturing messages.
Set the log-level filter to All and clear any process, search, or Regex filters that may be hiding entries.
If the Logcat buffer contains entries but the list appears empty, broaden or clear the active filters.
An exported Logcat file cannot be found
Export the Logcat results again and verify the selected save location.
Logcat exports are separate from Deployment Logs and are not automatically stored in the Workspace Deployment Logs folder.
Information for support
When requesting support, provide enough information to identify the problem and reproduce it. Include the exact message shown by APS, the action or workflow that produced it, the device model, Android version, and device serial number when relevant.
For Deployment problems, also include the Deployment ID and the Deployment log when available.
Do not include passwords, credentials, private certificates, or other sensitive information unless it is specifically required to investigate the problem.