Yep I put in that change, and all it did was make it guaranteed the app would crash instead of sometimes crashing.
On Fri, Oct 9, 2009 at 10:09 AM, bellapariah <bellapar...@gmail.com> wrote: > > Hi Brian, > > I am looking at the usage data from my server which includes how many > people signed up for an account as well as how many games they played > (my app is not available in the market yet so anyone that signs up for > an account should be an ADC2 tester). My final numbers were 102 > testers, 29 of which were force-quits due to 1.6 upgrade. (so around > 30% of testers were using 1.6) > > Also, here is the change made to 1.6 that is causing my app to not > work properly if anyones interested: > > 2009-05-20 Jean-Baptiste Queru donut snapshot > > > http://android.git.kernel.org/?p=platform/frameworks/base.git;a=history;f=core/java/android/os/RemoteCallbackList.java;hb=a8675f67e33bc7337d148358783b0fd138b501ff > > RemoteCallbackList.java: > > > http://android.git.kernel.org/?p=platform/frameworks/base.git;a=blobdiff;f=core/java/android/os/RemoteCallbackList.java;h=584224fccc8b0959a2580a14411536855b1423cc;hp=23c0a7bf473c48c2c93f6f4d9f97881a3c1315cd;hb=a8675f67e33bc7337d148358783b0fd138b501ff;hpb=843ef36f7b96cc19ea7d2996b7c8661b41ec3452 > > @@ -222,7 +224,12 @@ public class RemoteCallbackList<E extends > IInterface> { > > public int beginBroadcast() { > synchronized (mCallbacks) { > - final int N = mCallbacks.size(); > + if (mBroadcastCount > 0) { > + throw new IllegalStateException( > + "beginBroadcast() called while already in a > broadcast"); > + } > + > + final int N = mBroadcastCount = mCallbacks.size(); > if (N <= 0) { > return 0; > } > > 1.6 will throw this exception to let developers know if one of their > calls to beginBroadcast() was not terminated w/ a call to > finishBroadcast(). In 1.5, not calling finishBroadcast() is unchecked, > and although this is a programming mistake (cut and paste typo in my > case), my app, and probably several others, can still operate in 1.5 > without any noticeable consequence. This sort of thing is easily seen > and corrected within 5 - 10 minutes of testing on 1.6, but, of course, > we weren't given the 1.6 update to test with for the contest. > > Shelby > > On Oct 8, 1:58 pm, Brian Wright <brian.n.wri...@gmail.com> wrote: > > How did you determine you had " 95 people test my app for Round 1 > > judging, but 27 of those were "force closes" due to the 1.6 update. " > > > > I have not been told anything? Where is this data? > > > > On Oct 6, 8: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 > > > -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
