The sdk version in the manifest doesn't affect 1.6 introduced problems. My app using min of 1.5 still has encountered 1.6 issues (and force quits) that don't occur when running under Android 1.5.
On Oct 2, 2:57 pm, Hong <[email protected]> wrote: > 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/threa... > > and Google has acknowledged the problem here > > >http://groups.google.com/group/android-developers/browse_thread/threa... > > > 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 -~----------~----~----~----~------~----~------~--~---
