the minimum sdk version in the manifest was supposedly the gate keeper here...
On Fri, Oct 2, 2009 at 12:05 PM, Spencer Riddering <[email protected]>wrote: > > It's only a week into the ADC2 judging and already phones are being > updated to Android 1.6 Cupcake. With at least one more week to go in > the first round and (I'm guessing) two more weeks of judging in the > second round this means that around 75% of the ADC2 judging will occur > on Android 1.6. The 1.6 SDK was not made available to developers until > after the ADC2 deadline so (except for a few exceptions) all of the > ADC2 applications were not tested on this judging platform. > > Already an undocumented change in 1.6, which can break applications > that worked on 1.5, has been discovered here > > http://groups.google.com/group/android-developers/browse_thread/thread/61aca5f1f5bb0884/8cdd93627f37d636?lnk=gst > and Google has acknowledged the problem here > > http://groups.google.com/group/android-developers/browse_thread/thread/9abb325786b5829c/aebe4677b6620a25?lnk=gst&q=%22There+was+a+bug+in+the+VM+in+1.5+that+would+allow+abstract+classes+to+be+instantiated+through+reflection.%22#aebe4677b6620a25 > > Why is Google allowing an estimated 75% of the ADC2 to be judged on a > platform version that almost no one has had a chance to test on? > > Spencer Riddering > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
