Troubleshooting Android Studio¶
If you use the same keystore when updating AndroidAPS you do not have to uninstall the previous version on your smartphone. That’s why it is recommended to store the keystore in a save place.
In case you cannot find your old keystore anymore, proceed as follows:
- Export settings on your phone.
- Copy settings from your phone to an external location (i.e. your computer, cloud storage service...).
- Make sure settings file “AndroidAPS Preferences” is stored safely.
- Generate signed apk of new version as described on the update page.
- Uninstall previous AAPS version on your phone.
- Install new AAPS version on your phone.
- Import settings - if you can’t find them on your phone copy them from the external storage.
- Keep on looping.
Kotlin compiler warning¶
If build completed successfully but you get Kotlin compiler warnings then just ignore these warnings.
App was build successfully and can be transferred to phone.
Key was created with errors¶
When creating a new keystore for building the signed APK, on Windows the following error message might appear
This seems to be a bug with Android Studio 3.5.1 and its shipped Java environment in Windows. The key is created correctly but a recommendation is falsely displayed as an error. This can currently be ignored.
Could not download… / Offline Work¶
If you get a failure message like this
make sure that ‘Offline work’ is disabled.
File -> Settings
Error: buildOutput.apkData must not be null¶
Sometimes you might get an error message when building the apk saying
Errors while building APK.
Cause: buildOutput.apkData must not be null
This is a known bug in Android Studio 3.5 and will probably not be fixed before Android Studio 3.6. Three options:
- Manually delete the three build folders (normal “build”, build folder in “app” and build folder in “wear”) and generate signed apk again.
- Set destination folder to project folder instead of app folder as described in this video.
- Change apk destination folder (different location).
Unable to start daemon process¶
If you see an error message like the one below you probably use a Windows 10 32-bit system. This is not supported by Android Studio 3.5.1 and above. I you are using Windows 10 you must use a 64-bit operating system.
There are a lot of manuals on the internet how to determine wether you have a 32-bit or 64-bit OS - i.e. this one.
No CGM data¶
If you receive failure message like
Option 1 - Check git installation¶
- git might be not installed correctly (must be globally available)
- when on Windows and git was just installed, you should restart your computer or at least log out and re-login once, to make git globally available after the installation
- Check git installation
- If no git version is shown in check but git is installed on your computer, make sure Android Studio knows where git is located on your computer.
Option 2 - Reload source code¶
- In Android Studio select VCS -> GIT -> Reset HEAD
Option 3 - Check for updates¶
Copy ‘git checkout –’ to clipboard (without quote signs)
Switch to Terminal in Android Studio (lower left side of Android Studio window)
Paste copied text and press return
App not installed¶
- Make sure you have transferred the “app-full-release.apk” file to your phone.
- If “App not installed” is displayed on your phone follow these steps:
App installed but old version¶
If you build the app successfully, transferred it to your phone and installed it successfully but the version number stays the same then you might have missed to update your local copy.
None of the above worked¶
If non of the above tips helped you might consider building the app from scratch:
- Export settings (in AAPS version already installed on your phone)
- Have your key password and key store password ready. In case you have forgotten passwords you can try to find them in project files as described here. Or you just use a new keystore.
- Build app from scratch as described here.
- When you have build the APK successfully delete the exiting app on your phone, transfer the new apk to your phone and install.
- Import settings
Worst case scenario¶
In case even building the app from scratch does not solve your problem you might want to try to uninstall Android Studio completely. Some Users reported that this solved their problem.
Make sure to uninstall all files associated with Android Studio. If you do not completely remove Android Studio with all hidden files, uninstalling may cause new problems instead of solving your existing one(s). Manuals for complete uninstall can be found online i.e. https://stackoverflow.com/questions/39953495/how-to-completely-uninstall-android-studio-from-windowsv10.
Install Android Studio from scratch as described here and do not update gradle.