On 07/07/2013 02:23 PM, Tim Mensch wrote:
On 7/7/2013 10:13 AM, b0b wrote:
I get occasional report of resources not being found on app startup,
thus crashing the app.
The exact cause is difficult to know: broken install, broken ROM,
PEBKAC, repackaged version, ...
I even saw a crash due to someone running an instrumented version...
Another possibility: The user has connected their phone to a computer,
and the SD card has been taken offline. This assumes the user moved
the app to the SD card, of course.
Since there is nothing that can be done with such dubious crashes, I
just ignore them, along with Android platform crashes that are
unfixable (WebView anyone ?).
Yes, WebView. The best is WebView crashes in an ad plugin, so you're
doubly removed from any ability to fix the problem.
Tim
Then I get a glowing 5 star review for the same version this morning.
You would think this would allay any idea to the user with the problem
that the problem is the app. It looks like the guy with the problem
(and possibly another guy with a 7" Samsung Galaxy II) have posted their
stack trace every time they've tried an uninstall/reinstall. The stack
trace is always the same with a
android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1094)
happened on the startup screen with OnCreate. At that point everything
is very vanilla. The update changes occurred deep in the app with some
improvements to an existing function.
Of course I've noticed over time with a lot of other well rated apps "it
crashes on startup after the latest update" as if something went afoul
with the device itself not the app.
- Brian
--
You received this message because you are subscribed to the Google Groups "Android
Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/android-discuss.
For more options, visit https://groups.google.com/groups/opt_out.
