Android Runtime - Build 292

The Android runtime provided with the build 292 update patch has been updated to work with Gradle, it doesn't need Ant anymore, i.e. it will work with the latest Android Studio without you to have to patch it with Ant files, unlike the previous version.

What do you need to install

+ You should install the latest version of Please login to see this link. and then get the Android SDK pathname from the Android Studio settings screen as shown in Please login to see this link. and paste it in the Android SDK Pathname box in the preferences of Fusion (General tab).

+ Android Studio installs its own version of Java, usually in C:\Program Files\Android\Android Studio\jbr (or jre for old versions). Verify this directory exists on your machine and contains a bin/java.exe file), and use it as "Java SDK directory" in the preferences of Fusion. EDIT: in theory, recent versions of Fusion now automatically detect this directory.

Possible errors the first time you build an application and/or you use a new API

+ Gradle automatically downloads the libraries and build tools it needs, however it doesn't ask you for accepting licenses. If you get an error message that says "License for package XXXXX not accepted.", do this:

1. open an explorer window and go to the Android SDK folder (usually C:\Users\YourName\AppData\Local\Android\Sdk)
2. open the tools/bin sub-directory
3. open a command prompt window in this directory and type "sdkmanager --licenses" (or sdkmanager --update for old versions of the SDK), this will allow you to review and accept the licenses of the downloaded files. You can also simply open the SDK Manager and update the build API/Tools, this may work.

Note: the directory structure of the source files in the Android zip files for Gradle is different. If you use 3rd party extensions that aren't updated, Fusion will try to automatically convert it to Gradle. This works with simple extensions, but could fail for more complex ones. In this case, you'll have to wait for the developer to release an update.

For example if you got Android extensions from Click Store, check if there are new versions of these extensions, compatible with Gradle. You'll have to do this for example if you use GPG extensions and you get a "xxx is not a zip file" error message while building your application.

+ AdMob: another change in the build 292 is that the AdMob object has now 2 separate App IDs for Android and iOS. The first time you build an application with the build 292 make sure the Android App ID in the settings of the AdMob object is set to the correct value, otherwise your app will crash.

+ Build API: use preferably build API 28+ for building your applications.

Quote from Xenon3000

Thank you Yves, is this new engine take more performances of finals apps ?

Using Gradle instead of Ant doesn't change anything (AFAIK).

The Android runtime benefits from the "Optimize events" option of 2.5+ though this might not have a significant impact (this depends on the applications). There are other optimizations we made specifically for the Windows runtime, we'll port them to the other runtimes in the next builds.

With the build 292:

1. Install Android Studio and make sure a recent 64-bit version of JDK 8 is installed.
2. Report the Android SDK pathname mentioned in the SDK config screen of Android Studio to the General / Android preferences of Fusion.
3. If you use 3rd party extensions (for example the GPG extensions provided in Clickstore), make sure you install the "Gradle" version of these extensions.
4. Build your app, with Build API set to 28.
5. If you get a "Licenses not accepted" error message, follow the instructions in the top post of this thread.

I can reproduce the problem here if I insert non-ASCII characters in the pathname Fernando. And if I add the warning they mention it doesn't build. I wonder why testers didn't get this problem, maybe everyone used ASCII user names. I'm trying to see what we can do.

PS: just for info this is because your user name contains non-ASCII characters (probably accents given your location). This problem comes from the fact those tools used by Android Studio only support ASCII characters and (1) Android Studio installs the SDK in the user's Local AppData folder and (2) Fusion saves temp files to the user's Windows temporary folder, also in Local AppData.

For the Android SDK, 2 solutions:

1. you can move it to another folder: copy the Sdk directory from C:\Users\YourName\AppData\Local\Android to another folder that only contains ASCII characters, and then open Android Studio, File / Settings, Appearance / System settings / Android SDK, click Edit to edit the pathname and the browse button in the next screen to change it (and then you can delete the original SDK folder I think).

2. another solution, easier, use mklink to create a symbolic link without ASCII characters to the SDK directory. For this, open a Windows command prompt (you might have to run it as administrator) and enter:

mklink /D C:\MyAndroidSDK C:\Users\YourName\AppData\Local\Android\Sdk

and then set the Android SDK pathname to C:\MyAndroidSDK in the preferences of Fusion.

For Fusion, we probably need to add the ability for you to select another temporary directory, I don't how we can do otherwise (we could create a symbolic link in the product but I think most versions of Windows require you to have administrator privileges for this).

Or you use a user account with a user name without accents or non-ASCII characters...

Did you do what is mentioned above?

Quote

1. open an explorer window and go to the Android SDK folder (usually C:\Users\YourName\AppData\Local\Android\Sdk)
2. open the tools/bin sub-directory
3. open a command prompt window in this directory and type "sdkmanager --licenses" (or sdkmanager --update for old versions of the SDK), this will allow you to review and accept the licenses of the downloaded files.