Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 2D9B7200CA4 for ; Wed, 7 Jun 2017 22:36:23 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 2C2D0160BE2; Wed, 7 Jun 2017 20:36:23 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 7BA04160BD0 for ; Wed, 7 Jun 2017 22:36:22 +0200 (CEST) Received: (qmail 42920 invoked by uid 500); 7 Jun 2017 20:36:21 -0000 Mailing-List: contact issues-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@cordova.apache.org Received: (qmail 42703 invoked by uid 99); 7 Jun 2017 20:36:21 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Jun 2017 20:36:21 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 2BD3F1A04B2 for ; Wed, 7 Jun 2017 20:36:21 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id hZC-GwKY55Sl for ; Wed, 7 Jun 2017 20:36:20 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id D81315F6C3 for ; Wed, 7 Jun 2017 20:36:19 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 719E3E00A3 for ; Wed, 7 Jun 2017 20:36:19 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 2A80A21E10 for ; Wed, 7 Jun 2017 20:36:18 +0000 (UTC) Date: Wed, 7 Jun 2017 20:36:18 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: issues@cordova.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CB-12626) Splashscreen crashing on Samsung devices, not rendering on others MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 07 Jun 2017 20:36:23 -0000 [ https://issues.apache.org/jira/browse/CB-12626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16041568#comment-16041568 ] ASF GitHub Bot commented on CB-12626: ------------------------------------- Github user karlachavez commented on the issue: https://github.com/apache/cordova-plugin-splashscreen/pull/125 We can reproduce this issue on a Samsung S6 with the following tech specs: http://www.samsung.com/ca/business/business-products/smartphones/smartphones/SM-G920WZWABMC Due to it, we have to remove the splashscreen of our app. It's important to mention that the issue is presents since the device was updated from Android 6 to Android 7. Do someone know when the fix proposed is going to be applied? > 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: 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 > 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: issues-unsubscribe@cordova.apache.org For additional commands, e-mail: issues-help@cordova.apache.org