In my app, I'm facing a weird issue I can't explain. I can't even give you a logcat or something as I don't know where it is actually coming from, I can only describe the error:
My app Daily works well on some 5.0 and 5.1 devices, the HTC One Max for example. It does NOT work for Samsung and Sony devices running 5.1 and 5.0, maybe also at a 6.0 Samsung. The app just stays white for a few seconds and nothing happens then.
If you have any further questions about the app itself, you can just ask.
The app is using a MultiDexApplication and MultiDex itself if this might help.
Thanks.
Related
We have received issues from Customers who are seeing Black screen on Samsung Note 5, Samsung Galaxy s7 after they updated their device to Marshmallow. My application target SDK is 19. Basically the user are able to see the Launcher Activity A, but when they click on other activity B they see a Black screen. Activity A--> singletask and Activity B has default launch mode.
We have tested this application on other Vendors Marshmallow( Motorola, Nexus) devices and it seems to be working well. We have also seen some customer using our application on Samsung Galaxy s7 Edge(Marshmallow) too. We had one of the customer facing the same issue on Marshmallow Note 5, but he resolved that issue after Backing up the data from old Samsung J7 device, in which our application was running well. I am not sure, how backing up the data resolve this issue. Is there any device setting which is turned on or any thing which may be causing this issue. We do not have the Samsung Devices with Marshmallow and could not reproduce this issue.
Any advice appreciated, and let me know what could have caused this issue. Thanks in advance.
We received ANR Logs from the users on Playstore and we found out the issue was due to the Spannable String which we had used. The issue seems to be on only Samsung Marshmallow (6.0) Devices. This issue has been fixed in Marshmallow 6.0.1. Really don't understand, why Android is customized to such extent by Samsung. As our application is running well on Motorola Marshmallow 6.0. Here is the entire Logs from Samsung Marshmallow. Hope this might help some one who is facing similar issue.
at android.text.SpannableStringBuilder.calcMax(SpannableStringBuilder.java:1477)
at android.text.SpannableStringBuilder.calcMax(SpannableStringBuilder.java:1468)
at android.text.SpannableStringBuilder.calcMax(SpannableStringBuilder.java:1473)
at android.text.SpannableStringBuilder.calcMax(SpannableStringBuilder.java:1468)
at android.text.SpannableStringBuilder.calcMax(SpannableStringBuilder.java:1468)
at android.text.SpannableStringBuilder.calcMax(SpannableStringBuilder.java:1468)
at android.text.SpannableStringBuilder.calcMax(SpannableStringBuilder.java:1473)
at android.text.SpannableStringBuilder.calcMax(SpannableStringBuilder.java:1473)
at android.text.SpannableStringBuilder.calcMax(SpannableStringBuilder.java:1473)
... repeated 3 times
at android.text.SpannableStringBuilder.calcMax(SpannableStringBuilder.java:1468)
at android.text.SpannableStringBuilder.calcMax(SpannableStringBuilder.java:1468)
at android.text.SpannableStringBuilder.calcMax(SpannableStringBuilder.java:1468)
at android.text.SpannableStringBuilder.restoreInvariants(SpannableStringBuilder.java:1510)
at android.text.SpannableStringBuilder.setSpan(SpannableStringBuilder.java:762)
at android.text.SpannableStringBuilder.setSpan(SpannableStringBuilder.java:662)
Additional Logs on other Samsung Galaxy Edge Marshmallow 6.0 devices related to Spannable Text View
at android.text.SpannableStringBuilder.countSpans(SpannableStringBuilder.java:857)
at android.text.SpannableStringBuilder.countSpans(SpannableStringBuilder.java:864)
at android.text.SpannableStringBuilder.countSpans(SpannableStringBuilder.java:844)
at android.text.SpannableStringBuilder.countSpans(SpannableStringBuilder.java:864)
at android.text.SpannableStringBuilder.countSpans(SpannableStringBuilder.java:864)
at android.text.SpannableStringBuilder.countSpans(SpannableStringBuilder.java:864)
... repeated 7 times
at android.text.SpannableStringBuilder.countSpans(SpannableStringBuilder.java:844)
at android.text.SpannableStringBuilder.countSpans(SpannableStringBuilder.java:864)
at android.text.SpannableStringBuilder.countSpans(SpannableStringBuilder.java:844)
at android.text.SpannableStringBuilder.getSpans(SpannableStringBuilder.java:823)
at android.text.SpannableStringBuilder.sendSpanAdded(SpannableStringBuilder.java:1053)
at android.text.SpannableStringBuilder.setSpan(SpannableStringBuilder.java:763)
at android.text.SpannableStringBuilder.setSpan(SpannableStringBuilder.java:662)
In my app Toasts have worked fine until my RazrM phone was upgraded to 4.4.2. then they stopped. I have tried specifically runInUiThread and moving the call to initiate from different places in the code including in onCreate(). The issue [20373751] (Toast not appearing on Android 4.4 KitKat) proposes rebooting or specifically running on the UI thread. Neither makes a difference.
That issue also questions if there is a bug in Nexus or KitKat. I have the Toasts running fine in 4.0.4 on a Samsung Galaxy Tab. So I am thinking the problem is in 4.4. Has anyone found a workaround? (BTW I am compiling to a target of Version 9, so it is not an issue with the compile level.But I am using the infamous 23.0.2 SDK.) Can anyone prove that Toasts work under 4.4.2 while using SDK 23.0.2?
In [21098062] #marcin_j said:
On Jelly Bean 4.1 or higher,you can disable apps notifications from device settings. Just open notification bar, long tap on any of notifications and click App Info, you should see “Show notifications”. Unchecking this option should disable toasts in your app.
If your app does not show any notifications, then you should be able to reach App Info screen from applications manager.
Maybe this is the cause of you missing toasts
This was absolutely correct. My 4.0.4 device was not affected but my 4.4.2 device had had Show notifications unchecked.
We released a new app which has a widget. This works fine so far on all devices, however on Samsung Galaxy S3 we get reports that it stops working in certain situations.
Unfortunately I do not have such a device to check myself - therefore I would just like to know if anyone had some similar experience.
The widget stops working after the screen redraws itself (which seems to happen on the S3 regularly and randomly). Another user reported that the widget stops working after invoking the Task Manager and "clearing memory". There is no crash - in this case unfortunately.
The app has been tested on many devices with different Android versions - so far we have never seen such a random screen update which caused the widget to stop working.
I am thankfull for any hints.
...in fact it turned out to be a fault in Samsung's Android implemenation - they promised to fix it in the upcoming release. Thanks to Samsung amazing support we finally could confirm this issue !
I've received several reports from users that large parts of UI in my application just went invisible on their Galaxy Nexus with Android 4.1 and they are still clickable. I'm not able to reproduce it on any Android 4.1 emulator.
So the question is, what did Google mess up this time? Is it a known bug?
I ran into this myself. My problem was in using layerType="software" in some layouts. Getting rid of that fixed it.
I'm testing on an HTC Sensation, running android 4.0.3.
I'm publishing using FlashDevelop 4.0.3 and using the Air Mobile AS3 App template.
All the application does is display a Rectangle using:
this.graphics.beginFill(0x00FF00);
this.graphics.drawRect(0, 0, 100, 100);
Just so I can see that its actually publishing something.
The app runs correctly if I publish to the desktop, however when I switch to publishing it to the phone, the problem I'm facing is that the application publishes and runs on the phone, but only for a few seconds.. usually about 4 seconds and then it crashes out.
The really weird thing is that it was working fine about a week ago.. I'm not sure what's changed since then, but yeah it started happening this morning, I tried everything I could think of... including stripping everything out of the app and also doing a factory reset of my phone... nothing seems to have helped...
has anyone else had this problem? or have any ideas on what might be causing it or how to fix it? any help would be greatly appreciated.
Cheers
Update:
it seems changing the render mode to "auto" instead of "direct" stops the crashing, which is great, however if you need to use direct for stage3d content this doesn't really help. anyone else having this issue?
Can you post the source code of your application? I do too have HTC Sensation but my firmware version is 2.3.6. It would be interesting to test it.
I just updated my XPERIA ARC to ICS and now I'm having problems with AIR apps as well. Seems the app is not getting the Click/Touch interactions. Some InteractiveObjects like TextInput gets the click and focus as it should, but Buttons are not working. And I'm using latest Flex/AIR sdks...
But I'm pretty sure we are in Adobe/Apache hands until they update the AIR with a fix.