Blank canvas at app startup. Runtime won't start

Welcome to our brand new Clickteam Community Hub! We hope you will enjoy using the new features, which we will be further expanding in the coming months.

A few features including Passport are unavailable initially whilst we monitor stability of the new platform, we hope to bring these online very soon. Small issues will crop up following the import from our old system, including some message formatting, translation accuracy and other things.

Thank you for your patience whilst we've worked on this and we look forward to more exciting community developments soon!

Clickteam.

    Imagine that a game is now installed on an Android device. It was built on Fusion 295.5.

    With the release of Fusion 295.6, I compiled the game and installed it on the same device on which the previous version of the game was installed. No changes have been made to the game.

    As a result, when the game starts, a blank canvas is displayed instead of the game itself:
    Please login to see this attachment.

    Also, when you start the game, you can see the following text in logcat:
    Please login to see this attachment.

    All this indicates that the runtime did not start.

    ⚠️ I want to note that this only happens when updating an existing game that was built on 295.5! If the game build is installed with a new package name, this error will not occur.

    I did several tests with different devices here with 3 (ZTE Z982 Android 7, Google Pixel 3a XL Android 12, Samsung S23 Ultra Android 14 beta), and in all of them, F8 "build & run" and properly the installation.
    The only case this didn't work was because:

    1.- New installations have a lower version
    2.- A new version is a debug version, and the one installed is a release and signed version.

    This is related to Android OS and devices.

    So please provide us with more information when this happens, and if you have Android Studio please use this keyword as a filter in your logcat view --> ActivityManager | Finsky

    Here are some reports. The first one is from ZTE Z982, and the second is the Samsung s23 ultra:

    Regards,


    Fernando Vivolo

    ... new things are coming ...

    Quote from Fernando

    The only case this didn't work was because:

    1.- New installations have a lower version
    2.- A new version is a debug version, and the one installed is a release and signed version.

    Before building, I increase the build number, and I always build with the signing key.


    Quote from Fernando

    So please provide us with more information when this happens, and if you have Android Studio please use this keyword as a filter in your logcat view --> ActivityManager | Finsky

    This is what I got during game launch. Here is the log that is displayed on startup (with arguments ActivityManager | Finsky):

    Edited once, last by GKProduction (September 3, 2023 at 10:22 PM).

    And this is more detailed log just in case (with arguments ActivityManager | Finsky | ru.gkproduction.mysterychamber2015classic):

    I think I didn't explain myself well; please take the log while doing F8 from the fusion editor. This will show me when the app is ready by the fusion build process, and it is installed on your device; at that moment, the app is essential to log in to find out what your device says when it is being installed.

    The tests were carried out by having fusion 295.5 building the application and later the same application with 295.6. Obtain the log to verify what your device says when this process is executed.

    Regards,


    Fernando Vivolo

    ... new things are coming ...

    Quote from Fernando

    I think I didn't explain myself well; please take the log while doing F8 from the fusion editor. This will show me when the app is ready by the fusion build process, and it is installed on your device; at that moment, the app is essential to log in to find out what your device says when it is being installed.

    The tests were carried out by having fusion 295.5 building the application and later the same application with 295.6. Obtain the log to verify what your device says when this process is executed.

    Log from "Build and launch" action:

    Oh, I noticed, I still have old build after "Build and run"... But anyway this problem with blank canvas also have my testers after game update. I provide new builds through internal testing in Google Play Console, so the app has a signature and a new build number anyway.

    If Fusion is unable to update the build on my device for some reason, what else can I do to provide you with more information?

    Fernando, I have new information.

    Now the information that the application must be installed over the old one does not matter! After a complete uninstall and reinstall of the application, the problem still exists.

    I built the same application with different package names. The first package name is original and is used in Google Play, and the second package name is changed. Try to install and run each of these apk:

    Please login to see this link. (Original package name)
    Please login to see this link. (Edited package name)

    The problem may be related to the fact that the application has already been installed on the device before. You have never had this game installed, so you may not have this problem at startup, or it may still occur.

    Quote from GKProduction

    Fernando, I have new information.

    Now the information that the application must be installed over the old one does not matter! After a complete uninstall and reinstall of the application, the problem still exists.

    I built the same application with different package names. The first package name is original and is used in Google Play, and the second package name is changed. Try to install and run each of these apk:

    Please login to see this link. (Original package name)
    Please login to see this link. (Edited package name)

    The problem may be related to the fact that the application has already been installed on the device before. You have never had this game installed, so you may not have this problem at startup, or it may still occur.

    i test both apk, but note they are two different apks under the scope of android since they have different package name here.

    Please login to see this attachment.

    yes both were correctly installed but as mentioned they both exist in my device.

    yes the installation is not complete because you get this error

    Code
    2023-09-04 11:24:52.152 10924-28778 Finsky                  com.android.vending                  E  [141] VerifyPerSourceInstallationConsentInstallTask.d(20): Package name null is not an installed package

    could be happening because some problem with your gradle cache, look for internet how to clean at your side

    ah, and also post here what android studio you have and if you have the latest version of platform 34 (remember still in beta) and for your production case is better to use platform 33 and android 13 and finally is windows 10/11?

    Regards,


    Fernando Vivolo

    ... new things are coming ...

    Edited 2 times, last by Fernando (September 4, 2023 at 4:17 PM).

    Quote from Fernando

    ah, and also post here what android studio you have and if you have the latest version of platform 34 (remember still in beta) and for your production case is better to use platform 33 and android 13 and finally is windows 10/11?

    I have Android Studio Electric Eel 2022.1.1 Patch 2, in mfa I used API 34, target version is 14, and my OS is Windows 11, but Fusion is set to Windows 7 compatibility mode, since one of my mfas does not open in normal mode, but that's another story...

    Using API 33 and target version 13 still gives same result. But also I clean Gradle cache and that didn't have any effect either. :(
    I also tried using File -> Invalidate Caches in Android Studio, turning off Fusion's compatibility mode and even completely reinstalling Fusion, but nothing helped. App still has empty gray screen after launch.

    Edited once, last by GKProduction (September 5, 2023 at 1:09 AM).

    Quote from GKProduction

    I have Android Studio Electric Eel 2022.1.1 Patch 2, in mfa I used API 34, target version is 14, and my OS is Windows 11, but Fusion is set to Windows 7 compatibility mode, since one of my mfas does not open in normal mode, but that's another story...

    Using API 33 and target version 13 still gives same result. But also I clean Gradle cache and that didn't have any effect either. :(
    I also tried using File -> Invalidate Caches in Android Studio, turning off Fusion's compatibility mode and even completely reinstalling Fusion, but nothing helped. App still has empty gray screen after launch.


    i have no clue to be honest, here both APK work since they are two different application because a different package, and the built with 295.6 will never replace the one made with 295.5

    may i suggest remove the compatibility with Windows 7 and try again to see

    Regards,


    Fernando Vivolo

    ... new things are coming ...

    Quote from Fernando

    may i suggest remove the compatibility with Windows 7 and try again to see


    Already tried. No good results.

    By the way, for one of my testers, a game that was installed from an apk with the correct package name started without a gray screen, but the same build from Google Play still does not start.

    Maybe I can give you access to my internal testing so that you can try to run the build that was uploaded to Google Play?

    I installed the application from Google Play on a completely clean emulator (Android Studio Emulator), and still got a blank screen on startup. Could this be due to the fact that I am building in "AAB with expansion" format? Because to Google Play I always upload aab, not an apk.

    I just checked it by building an app into a simple AAB format (without extension expansion). The game now works!! I checked the launch on the device and on the emulator. No more blank screen.

    Fernando, maybe you forgot to do something with AAB Expansion?

    Edited once, last by GKProduction (September 6, 2023 at 12:20 AM).

    Quote from GKProduction

    I installed the application from Google Play on a completely clean emulator (Android Studio Emulator), and still got a blank screen on startup. Could this be due to the fact that I am building in "AAB with expansion" format? Because to Google Play I always upload aab, not an apk.

    ========

    I just checked it by building an app into a simple AAB format (without extension). The game now works!! I checked the launch on the device and on the emulator. No more blank screen.

    Fernando, maybe you forgot to do something with AAB Expansion?

    not sure if i understand so you are using f8 to build an aab with expansion, can you give us full steps.


    ==========================

    tested with several application and device and can't reproduce this here.

    Regards,


    Fernando Vivolo

    ... new things are coming ...

    Edited 2 times, last by Fernando (September 5, 2023 at 6:38 PM).

    Quote from Fernando

    not sure if i understand so you are using f8 to build an aab with expansion, can you give us full steps.


    ==========================

    tested with several application and device and can't reproduce this here.

    No no. I created a build with the specified type "AAB with expansion" using "File -> Build -> Application", then uploaded an aab file to Google Play. Then after installing this build from Google Play, there was a problem with a blank screen when starting the application.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login