Hi Hong, Here are the details of the 1.6 change that is causing my app to not work properly:
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, 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, 12:55 pm, Hong <[email protected]> wrote: > Shelby and Thomas, can you elaborate more on the force closes issues? > Specifically, what API/methods broke from 1.5 to 1.6? > > Thanks > > On Thu, Oct 8, 2009 at 3:12 PM, Shelby Troxell <[email protected]>wrote: > > > > > Sure. The point of the title was to catch attention and try to consolidate > > all the conversations regarding 1.6 issues into one location since their are > > many threads with similar names. Also, I've been very disappointed that no > > one from Google will make a statement about the issue, or post in the forums > > in general. Sorry to hear about Gigbox. Ours was Amoeba Blackjack and is in > > the same situation. > > Shelby > > > On Thu, Oct 8, 2009 at 3:42 AM, Thomas Jørgensen <[email protected]>wrote: > > >> Hi all > > >> After updating to 1.6 we got a force close error in our ADC2 > >> application Gigbox. We were able to quickly fix the error and post an > >> update to the Android Market. Should we make it to the second round of > >> ADC2, then our application is limited in functionality, and it will > >> not be posible to judge it fairly on 1.6 devices. > > >> We are aware that the official terms and conditions leave no options > >> to deal with this case. But we do hope that Google will try to address > >> this issue one way or another, even though there is no optimal > >> solution that will benefit us all. > >> From our point of view, the first round of ADC2 has been fair and > >> equal. The first round was stopped before too many handsets were > >> updated with 1.6. In order to make the second round fair, we think > >> that the optimal solution would be to allow updates to the > >> applications, in order to correct 1.6 related issues. New features > >> shouldn't be allowed. > > >> Best regards, > >> Gigbox Team > > >> Btw: Shelby, what about changing the title for this thread to be more > >> specific towards the ADC2 and 1.6 issues insted of Google employees? > > >> On 7 Okt., 03:49, bellapariah <[email protected]> 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! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
