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 -~----------~----~----~----~------~----~------~--~---
