Known Issues¶

Known Issues in Release 24.12.0¶

A view-based app may fail to build on Android Studio 2024.2.1 and throw a java.lang.IllegalAccessError from the K2 JVM Compiler. By default, the Gradle JDK in Android Studio 2024.2.1 is set to JBR 21.0.3. You can find this in Settings -> Build Tools -> Gradle. Change it to JBR 17.0.11-17.0.12, and make sure the JDK on your machine is set to the same version. Afterward, clean your project and try again.

Known Issues in Release 24.8.0¶

Chrome may have problems of sending out the visible status in some rare cases (Google issue), then the timeout flow might be impacted in those cases. We recommend using WebView for launching your web-based Fiori application instead of Chrome Custom Tabs (CCT).

Known Issues in Release 24.4.0¶

WebView, by default installed with API 28 or older versions of Android devices, will cause OAuth failure during the login process. The error message in the cockpit is: "OAuth token request includes an invalid code_verifier." To resolve this issue, please update WebView to the latest version.

Known Issues in Release 3.4¶

The visited steps of the Flows library won't reflect the current dark/light theme or language settings if those configurations were changed in the middle of a flow.

Known Issues in Release 3.3¶

Connection Accounts: Connection Accounts won’t work after you upgrade to version 3.3. Run the script in the installer to upgrade the H2 database.

Known Issues in Release 3.0¶

SAP Translation Hub Integration: The SAP Translation Hub feature does not work if you are using an SAP Business Technology Platform Trial Account.
Automatic upload for logging and usage: Due to Google API issue, the automatic upload will not happen if the device is in roaming.

AndroidX Support¶

The Android SDK libraries are currently compiled with the support library API packages instead of AndroidX. It's still possible to use AndroidX with the SDK by following the migration guide here.

Some possible issues that might be encountered:

Jetifier fails to convert Databinding classes, resulting in a NoClassDefFoundError. For more information on this issue, read the bug associated with the issue. The workaround is to include a later Jetifier release that handles the Databinding classes correctly:
```
buildscript {
    dependencies {
        classpath 'com.android.tools.build:gradle:3.3.1'
        classpath 'com.android.tools.build.jetifier:jetifier-core:1.0.0-beta03'
    }
}
```
Glide produces a mix of support and AndroidX annotations. An upcoming release of Glide should provide better support. The workaround for now is to include the support annotations also:
```
implementation 'com.android.support:support-annotations:28.0.0'
annotationProcessor 'com.android.support:support-annotations:28.0.0'
```

Last update: December 13, 2024