My app broke as a result of an Android API throwing a proactive
IllegalStateException in 1.6. While this is a good inclusion for those
developing on 1.6, it was not documented or required in 1.5, and
therefore may break 1.5 apps that have not been able to test in 1.6
and fix app for the new exception. My app has been tested for extended
periods of heavy use for 1.5 and never ran into the problem Google is
trying to safeguard against (my app runs great in 1.5 which is what we
were told to develop for) so I was unaware that the issue existed
until I was able to test it on 1.6.
>From the stats my app collects, I am able to see that ~30% of the
contest graders were running 1.6 over the period of the contest.... So
I can probably assume that 30% of my end grade was lost. :(
Shelby
On Oct 6, 7:57 pm, niko20 <nikolatesl...@yahoo.com> wrote:
> What API's are you guys using that just going from 1.5 to 1.6 broke
> stuff? I would think 1.6 would have been properly back-compatible...
>
> On Oct 6, 8:58 pm, bellapariah <bellapar...@gmail.com> wrote:
>
>
>
> > What is Google just dropped the 25 lowest scores for every app? There
> > would still be 75 reviews to give a relatively accurate average rating
> > and it would be fair for all without giving benefits to select
> > developers.
>
> > On Oct 6, 6:48 pm, bellapariah <bellapar...@gmail.com> wrote:
>
> > > Thread for developers to discuss problems with 1.6 update and effects
> > > on ADC2. If you see other forums or articles on the issue or if you
> > > are one of the unlucky developers affected by the the untimely 1.6
> > > update, please post is here!
>
> > > Releasing 1.6 in the middle of a contest is unacceptable. According to
> > > the official terms and conditions:
>
> > > "a. SUBMISSION OF ENTRIES: To qualify for a Prize, an "Entry" to the
> > > Challenge consists of an original application that is written using a
> > > version of the Android Software Development Kit ("SDK") (available
> > > athttp://developer.android.com) that validly executes on Android version
> > > 1.5. The SDK contains instructions, documentation, and all necessary
> > > tools to enable a Participant to build an Android application."
>
> > > My App as well as many other ADC2 apps worked fine on 1.5 but started
> > > "force closing" after the 1.6 update. Programmers were told to develop
> > > an application for 1.5, not 1.6, and were not given the tools or
> > > opportunity to test our apps with 1.6. In my case, I have had 95
> > > people test my app for Round 1 judging, but 27 of those were "force
> > > closes" due to the 1.6 update. This is because of an issue with a
> > > Google API that was updated with 1.6. Here are links to other people
> > > discussing the 1.6 issue:
>
> > >http://groups.google.com/group/android-discuss/browse_thread/thread/7...
>
> > >http://groups.google.com/group/android-discuss/browse_thread/thread/a...
>
> > >http://groups.google.com/group/android-discuss/browse_thread/thread/5...
>
> > >http://groups.google.com/group/android-developers/browse_thread/threa...
>
> > >http://www.google.com/support/forum/p/Android+Market/thread?tid=5d754...
>
> > >http://androidandme.com/2009/10/news/did-google-fumble-the-android-1-...
>
> > >http://polyclefsoftware.blogspot.com/
>
> > > One suggestion would be to remove the last 25% of reviews of every app
> > > in the contest (the ones most likely to have been affected by 1.6
> > > upgrades) to reduce the negative effects of the 1.6 release.
>
> > > How many others were affected? Any solutions to fix the problem?
>
> > > Shelby
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
