I think this is related to the restriction that an app with copy protection on cannot be downloaded to an unlocked phone, i.e. ADP. We have seen that too before turning the option off.
On Feb 21, 8:40 am, Stoyan Damov <[email protected]> wrote: > Something else - 1 of the mysteries just unveiled - both of my apps > which wouldn't show on Cyrket are there now (at least by searching for > them, not in the list yet). > > On Sat, Feb 21, 2009 at 6:38 PM, focuser <[email protected]> wrote: > > > good to know that we are not alone. :) > > > I have reported this issue through Android Market support and hoping > > they could fix it soon... > > > On Feb 21, 8:31 am, Stoyan Damov <[email protected]> wrote: > >> :OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO > > >> I had users talking about these Force Close issues yesterday and I was > >> scratching my head for a long time :O :O O > > >> Thanks man! > > >> On Sat, Feb 21, 2009 at 6:20 PM, focuser <[email protected]> wrote: > > >> > Hi fellow developers, > > >> > Recently there is a new option "Copy Protection" in Android Market > >> > Developer Console. We thought that was a nice protection on us and > >> > turned it on. Then here comes the impact: our app was no longer > >> > listed & downloadable on ADP, and *MUCH WORSE*, those who can > >> > download have experienced severe force closes when the app starts! We > >> > have confirmed this by just downloading&running the app before and > >> > after that option is turned on. > > >> > I have no idea what mechanism Google uses to implement that option, > >> > but it seems they are changing the apk -- the application size is > >> > larger when the option is on. > > >> > Seen from the exception trace, it seems it's related to an issue that > >> > I reported > >> > before:http://groups.google.com/group/android-developers/browse_thread/threa... > > - Show quoted text - > >> > It seems the resource is screwed up. Basically findViewById returns a > >> > wrong thing, and in turn you get either NullPointerException or > >> > ClassCastException. We are still not able to use an ant script to > >> > automate the build&sign process, which triggers the bug and gives you > >> > a corrupted apk. However, exporting an unsigned apk using Eclipse and > >> > signing it manually works with no problem. > > >> > What a bug,... we have lost 5000+ users due to this. Google should > >> > have tested more carefully it before making it available. > > >> > Hope this is helpful > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" 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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
