Problemen met Android Studio oplossen

Keystore (digitale handtekening) kwijt

Het is het makkelijkste om steeds hetzelfde keystore-bestand te gebruiken bij het updaten van AndroidAPS, omdat jouw telefoon dan de nieuwe versie van de app herkent als update van jouw bestaande app. Je laat de bestaande app gewoon op je telefoon staan, je installeert de nieuwe eroverheen en al jouw instellingen blijven behouden. Daarom moet je jouw keystore bestand (eindigt op *.jks) opslaan en bewaren op jouw computer.

If you try to install the apk, signed with a different keystore than before, you will get an error message that the installation failed!

In case you cannot find your old keystore or its password anymore, proceed as follows:

  1. Export settings on your phone.

  2. Copy or upload the settings file from your phone to an external location (i.e. your computer, cloud storage service...).

  3. Generate signed apk of new version as described on the Update guide and transfer it to your phone.

  4. Verwijder de vorige AAPS-versie van jouw telefoon.

  5. Installeer de nieuwe AAPS-versie op jouw telefoon.

  6. Import settings to restore your objectives and configuration.

  7. Check your battery optimization options and disable them again.

    If you can’t find them on your phone copy them from the external storage to your phone.

  8. Keep on looping.

Gradle Sync failed

Gradle Sync can fail to various reasons. Wen you get a message saying that gradle sync failed, open the “Build” tab (1) at the bottom of Android Studio and check what error message (2) is displayed.

Gradle Failed

These are the usual gradle sync failures:

Important: After you have followed the instructions for your specific problem, you need to trigger the gradle sync again.

Uncommitted changes (Niet-opgenomen wijzigingen)

If you receive a failure message like

Gradle Uncommited Changes

Step 1 - Check git installation

  • Open the terminal tab (1) at the bottom of Android Studio and copy the following text and paste or type into the terminal.

    git --version
    

    Gradle Git Version

    Note: There is a space and two hyphens between git and version!

  • You must receive a message saying what git version is installed, as you can see in the screenshot above. In this case, go to Step 2.

  • In case you get an message saying

    Git: command not found
    

    your Git installation is not right.

  • Check git installation

  • if on Windows and git was just installed, you should restart your computer to make git globally available after the installation

  • If Git is installed, you have restarted (if on windows), and git still couldn’t found:

  • Search your computer for a file “git.exe”.

    Note for yourself, what directory it is in.

  • Go to the Environment variables in windows, select the variable “PATH” and click edit. Add the directory where you have found your git installation.

  • Save and close.

  • Restart Android Studio.

Step 2: Check for uncommitted changes.

  • In Android Studio, oben the “Commit” Tab (1) on the left-hand side. Commit Tab: Uncommitted changes

  • You can see either a “Default changeset” (2) or “Unversioned files” (3):

    • For “Default changeset”, you probably updated gradle or changed some of the file contents by mistake.

    • Right click on “Default Changeset” and select “Rollback”

      Commit Tab: Rollback changes

    • The files are fetched again from the Git server. If there are no other changes in the commit tab, go to Step 3.

  • If you can see “Unversioned Files”, you might have stored files in your sourecode directory which should be better places somewhere else, e.g. your keystore file.

    • Use your regular file explorer on your computer to move or cut and paste that file to a save place.

    • Go back to Android Studio and click the Refresh button (4) within the Commit tab to make sure the file is not stored in the AndroidAPS directory anymore.

      If there are no other changes in the commit tab, go to Step 3.

Step 3: Resync Gradle (again)

Follow the instructions at Gradle Resync.

Android Gradle plugin requires Java 11 to run

You might experience this error message:

Android Gradle plugin requires Java 11 to run

Click on “Gradle Settings” (1) to go to open the gradle settings.

If you don’t have the link to the “Gradle Settings”, open the Gradle settings manually by selecting the Gradle Tab on the right border (1), select the tools icon (2) and there the item ‘Gradle Settings’ (3).

Gradle Settings

When you have opened the Gradle settings dialog, open the options (1) at “Gradle JDK” and selected the “Embedded JDK version” (2).

Gradle Settings

Press “OK” to save and close the settings dialog.

Important: If you don’t see the setting “Gradle JDK”, you might have not updated Android Studio. Make sure you are using Android Studio 2021.1.1 Bumblebee) or newer.

Now you need to trigger a Gradle Resync

Could not resolve/No cached version

You might get this error message:

![Could not resolve... No cached version](../images/studioTroubleshooting/08_NoCachedVersion.png)
  • On the right side, open the Gradle tab (1).

    Make sure the button shown at (2) is NOT selected.

    Gradle Offline Mode

  • Now you need to trigger a Gradle Resync

Unable to start daemon process (Kan daemon proces niet starten)

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 and unfortunately nothing the AAPS developer can do about.

If 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.

Screenshot Unable to start daemon process

Gradle Resync

If you can still see the message that the gradle sync failed, now select the Link “Try again”. Gradle Sync Failed Mode

If you don’t see the a message anymore, you can still trigger this manually:

  • Open the Gradle tab (1) on the right border of Android Studio.

    Gradle Reload

  • Right-click on AndroidAPS (2)

  • Click on “Reload Gradle Project” (3)

Generate Signed APK generated successfully with 0 build variants

When you generate the signed apk, you might get the notification that generation was successfully but are told that 0 build variants where generated:

APK generated with 0 build variants

This is a false warning. Check the directory your selected as “Destination folder” for generation (step Generate Signed APK) and you will find the generated apk there!

App was created with compiler/kotlin warnings

If your build completed successfully but you get compiler or kotlin warnings (indicated by a yellow or blue exclamation mark) then you can just ignore these warnings.

Gradle finished with warnings

Your 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

Key was created with errors

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.

No CGM data is received by AndroidAPS

  • In case you are using patched Dexcom G6 app: This app is outdated. Use the BYODA app instead.
  • In case you are using xDrip+: Identify receiver as described on xDrip+ settings page.

App not installed

phone app note 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:
  1. Export settings (in AAPS version already installed on your phone)
  2. Verwijder de AndroidAPS app van jouw telefoon.
  3. Enable airplane mode & turn off bluetooth.
  4. Installeer nieuwe versie (“app-full-release.apk”)
  5. Importeer instellingen
  6. Zet bluetooth weer aan en schakel de vliegtuigmodus uit

App installed but old version

If you built 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:

  1. Export settings (in AAPS version already installed on your phone)

  2. Houd jouw keystore file (digitale handtekening) en keystore wachtwoord bij de hand. In case you have forgotten passwords you can try to find them in project files as described here.

    Of je maakt gewoon van een nieuw keystore bestand en wachtwoord aan.

  3. Build app from scratch as described here.

  4. Als je de APK hebt gebouwd, verwijder eerst de bestaande app van jouw telefoon. Verplaats daarna de nieuwe apk naar je telefoon en installeer.

  5. Import settings again to restore your objectives and settings.

  6. You should check your battery optimization options and disable them again.

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.