The interesting thing is knowing what changed between OS versions. I
recently upgraded some 1.5 OS apps to make the target OS 1.6 to handle
screen resolution issues. The upgrade caused a crash which didn't occur
under 1.5. It was innocuous as the crash just took the user back to the
splash screen menu. It was because it tried to open an SQL database
that had not been created yet. Most users would not see this as the
first thing they would do is an activity which created the database and
an entry in it. The 1.5 version handled no database just fine and
popped up a message with toast saying there were no entries found. It
didn't of course take much to fix the 1.6 version. But how would any
developer know that a difference had occurred?
Same with a feature which could save said database to the SD card.
Under 1.5 no permissions needed but it wasn't working when I tested it
because you have to have an SD card write permission under 1.6. I
caught that before the upgrade went out.
Since Android is being taken VERY seriously these days it is time for
Google to probably double or triple their Android tech writer budget so
developer documentation is up to snuff.
- Brian
TreKing wrote:
On Thu, Sep 16, 2010 at 3:11 AM, Chris Stratton <[email protected]> wrote:
I was thinking it might be useful if the platform let an activity either
programmatically or in the application manifest register an intent that
would be fired if the activity crashes due to an error, force closes, etc.
Haven't actually done this yet, but you can set an uncaught exception
handler, can't you? Then do whatever you feel is appropriate beyond the
default.
On Thu, Sep 16, 2010 at 3:42 AM, Kiall Mac Innes <[email protected]> wrote:
personally ill hit send bug report and wait for the next update
notification before I try it again..
I hope you also take the time to elaborate on what you were doing when the
app crashed. Because 99% of the reports I get either have no comment or have
something like "Keeps crashing", that is almost useless in identifying and
fixing problems when you have nothing but a stack trace to go off of
(especially when it's a thread stack).
-------------------------------------------------------------------------------------------------
TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago
transit tracking app for Android-powered devices
--
You received this message because you are subscribed to the Google Groups "Android
Discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/android-discuss?hl=en.
