cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CB-12626) Splashscreen crashing on Samsung devices, not rendering on others
Date Fri, 25 Aug 2017 00:19:03 GMT


ASF GitHub Bot commented on CB-12626:

Github user uj commented on the issue:
    @Lazza Ok, i just tried your fix, and it crashes less often, but not 100% crash-free.
 However, this mostly happens when using the back-button to "exit" the program.  There is
a separate Android bug on some devices where exiting with the back button causes the app to
relaunch instead of sleep/resume even though the app is still running, and that *might* be
part of the crashing problem, I don't know.  Note that when I do not use either of the splashscreen
plugins at all, it NEVER crashes no matter what.

> Splashscreen crashing on Samsung devices, not rendering on others
> -----------------------------------------------------------------
>                 Key: CB-12626
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: cordova-android, cordova-plugin-splashscreen
>         Environment: Crashing devices:
> - Samsung Galaxy 7 Edge, Android 7.0
> - Samsung Galaxy Note 4, Android 6.0.1
> "Not showing" devices:
> - Lenovo/Zuk Z1, Android 5.1.1
> - Official Android Emulator with Nexus S simulated hardware, API 25
>            Reporter: Andrea Lazzarotto
>            Assignee: Joe Bowser
>              Labels: android, android-next
> We tested the plugin on a few Samsung devices and found out that the current version
of the splash screen plug-in is completely crashing the app, with an error given by {{AndroidRuntime}}
(including the PID of the app) and a warning given by {{ActivityManager}} in the log:
> {{Force finishing activity packagename/.MainActivity}}
> Moreover, we noticed that the splash screen is not showing correctly on some devices.
The Samsung crash was initially solved by commenting out this line:
> {{preferences.set("SplashDrawableId", drawableId);}}
> Basically, this means that storing the {{drawableId}} in the preferences is not reliable.
This didn't solve the display issue on other devices, which required refactoring the code
that reads the resource ID.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message