[
https://issues.apache.org/jira/browse/CB-12626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15986678#comment-15986678
]
ASF GitHub Bot commented on CB-12626:
-------------------------------------
Github user Lazza commented on the issue:
https://github.com/apache/cordova-plugin-splashscreen/pull/125
@filmaj I see. 😄 Just to be clear, my PR is released under the Apache
Version 2.0 license as anything else in this repo (it is also the license
mentioned in the project and the file header). I am not transferring copyright
to someone else that could decide to prevent my code from being under the
Apache License, but I am contributing the code giving all the rights specified
in the license.
Regarding the devices, I suggest to try those written in the first message
above, especially the Samsung ones because they exhibited the crashes
consistently and repeatably.
> Splashscreen crashing on Samsung devices, not rendering on others
> -----------------------------------------------------------------
>
> Key: CB-12626
> URL: https://issues.apache.org/jira/browse/CB-12626
> Project: Apache Cordova
> Issue Type: Bug
> Components: 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
> Labels: android
>
> 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
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
