cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CB-12626) Splashscreen crashing on Samsung devices, not rendering on others
Date Thu, 05 Oct 2017 21:07:01 GMT


ASF subversion and git services commented on CB-12626:

Commit 50a55883d3edc7d4c9b4c521c11ed2c108315b28 in cordova-plugin-splashscreen's branch refs/heads/master
from [~Lazza]
[;h=50a5588 ]

CB-12626: Updated Android plugin

This closes #125

Prefer a slightly slower, but bulletproof, way to check for the splashscreen instead of relying
on the Cordova preferences. This fixes the splash screen on several phones.

> 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