Bug? Galaxy S4 - 4.3 - Unfortunately, <AppName> has stopped. on Activity exit

qle

Member
Licensed User
Longtime User
Forgive me if this should have been placed into General forum first.

B4A: V3.00

Device:
Device: Samsung Galaxy S4 - GT-I9505
OS: Android Version 4.3
Kernal: 3.4.0-2082040
se.infra@SEP-126#1
Thu Nov 21 15:13:46 KST 2013
Build#: JSS15J.I9505XXUEMK9
Enforcing: SEPF_GT-I9505_4.3_0014


Also tested on: (all without issue, runs fine as epected)
Galaxy Note 2 - GT-N7105 (AV: 4.1.2)
Galaxy S - GT-I9000 (AV: 2.3.6)
PDA_Scanner (AV: 2.3.7)

Summary:
The Samsung Galaxy S4 was running fine with all B4A , until a Operating System update (pushed by Samsung) Now all apps developed in B4A crash on S4 (4.3) with "Unfortunately, <AppName> has stopped."
To View the error happening
Reproduction Steps:

Compile and install, simple press button on screen to start second activity, then press the 'back' button on the device, 4 out of 5 times i will get the error:Unfortunately, <AppName> has stopped.

The sample Attached is a zipped exported app with bare minimal code to cause the issue,
In fact almost no code at all, just a button to start activity.

Sorry i do not have another S4 (4.3) to fully confirm that it is only S4 (4.3) issue..
The S4 im using is quite clean and standard (almost out of the box new)

I have tried in Debug (legacy) and Debug (Rapid), no information about the crash is shown in the Logs (no filter) panel.

Lee.
 

Attachments

  • G_S4_Test.zip
    212.6 KB · Views: 297

qle

Member
Licensed User
Longtime User
Thank you, this did fix the issue..

Is this something i should have found in the forum somewhere? (i did a lot of searching!)
Is there an advanced search in the forums (with AND, OR, exclude, quote type searches?) that i have missed?

edit: i did miss the thread on 'fatal signal error Android 4.3 KeyCodes.KEYCODE_MENU'
 
Last edited:
Top