|Android P apps crash silently instead of showing dialogs|
|By Thom Holwerda on 2018-05-13 15:33:53|
Among all the new additions to Android P including new navigation gestures, Slices API, and new biometrics API, there are some other changes which may also be impactful in a more subtle way. One of these is the removal of App Not Responding (ANR) dialogue boxes for foreground apps. The ANR dialogue appears when something is preventing the main UI thread from responding. When this happens in Android Oreo or below, the ANR dialogue is shown to the user to let them know. Now, in Android P, the application will just crash without any kind of notification for the user.
You know how some people will insist that iOS applications are more stable than Android applications? That's because on iOS, when applications crash, they just... Vanish. No dialog, no notification, nothing. Android will now be adopting the same behaviour, which, while less informative, does remove a silly dialog that you couldn't really do anything useful with anyway.
Good move. Dialogs you can't take any actions with are useless.
|iOS app ARE more stable|
|By shadow_x99 on 2018-05-14 00:46:42|
As a moible developer who writes both iOS and Android apps, and I use something really scientific like Crashlytics to measure my own apps crashing pattern. |
I can say with certainty that iOS app, with simular user base (size-wise) times as much users crash 40% less than it's Android counterpart.
Android just shows WAY more random crashes than iOS. I do not know why, but it's a fact that I have experienced with every app I have written / supported throughout the years.
|- Score: 1|
|By umccullough on 2018-05-14 02:57:05|
On Error Resume Next.... |
A stupid solution to shitty software: just pretend everything is fine and the user doesn't need to know something went wrong.
When apps just 'disappear', it's infuriating - i'd like at least a small informative note that shit hit the fan.
|- Score: 8|
|By nicubunu on 2018-05-14 07:26:41|
|Agreed. I don't want my running app to vanish without a trace, especially when is a slow starting app or one I want to stay running .|
|- Score: 5|
|By bhtooefr on 2018-05-14 09:31:17|
|To be fair, this isn't On Error Resume Next, this is On Error End.|
|- Score: 3|
|And here is the proof|
|By darknexus on 2018-05-14 11:35:35|
Google does copy Apple! I knew it! |
|- Score: 0|
|By darknexus on 2018-05-14 11:39:30|
|Agreed. On iOS, you can at least go to the system log and look at the error there, but I'd still like to see something indicating a crash so I know to look.|
|- Score: 2|
|Should be a notification|
|By jessesmith on 2018-05-14 13:42:42|
While a dialog box without any possible action/recovery option is pretty useless in this case, there should still be some notification to the user. |
I fired up Android recently on a spare device and one service I had installed would crash about every 30 seconds. The flood of dialogs was terrible and disrupted workflow. But obviously the system should notify the user something has gone wrong. Otherwise your apps/services are just disappearing without explanation and that's a huge bug.
Ideally, there should be a message posted in the notification area letting the user know a crash happened, without displaying a pop-up that breaks flow.
|- Score: 4|
|RE: iOS app ARE more stable|
|By protomank on 2018-05-14 15:16:06|
On my game, crashes have mostly three reasons: |
- file system access - it asks user for permission but sometimes user won't give, or simply android won't understand.
- very strange device or odd android version behaves badly.
- random crash - something like updating the screen or sound system gives an exception from lower API to SDL I use, and bump!
Random crashes is around 10% of total crashes, most are due to different pieces of hardware running different pieces of operating system. And that bad thing is that, those, I simply can't fix.
|- Score: 3|
|By umccullough on 2018-05-14 15:35:49|
> To be fair, this isn't On Error Resume Next, this is On Error End. |
Indeed... I used the analogy because it's a similar type of thinking that made "On Error Resume Next" so popular in VB apps... It's not "error handling", it's just "error ignorance".
|- Score: 3|
|RE: Should be a notification|
|By umccullough on 2018-05-14 15:55:43|
> I fired up Android recently on a spare device and one service I had installed would crash about every 30 seconds. The flood of dialogs was terrible and disrupted workflow. |
That's another thing that drives me nuts: Restarting a crashed app automatically without giving the user the chance to make it go away.
Any non-critical "service" that is set to automatically restart on failure needs some kind of kill switch to prevent it from taking control away from the user.
I've had multiple situations where I get into a google play services failure/restart loop, interrupting my ability to actually do anything about it. In at least one of those situations, I had to reflash the ROM (it was a custom rom, and i had recently installed it) - in another situation, I had to use ADB to go in and fix the problem via shell. What a lovely user experience.
|- Score: 3|