Hi Moss The com.package.app is just an "obfuscated" package name (much like your "com.package.app"). In reality I'm using a unique name or that's what I hope I do ;-).
Thanks for your post anyway. I really appreciate your support! Cheers Emanuel On Nov 24, 2:01 pm, Moss <[email protected]> wrote: > Could it be that the class loader is failing to find the right > package? I just saw that you are using 'com.company.app' as your > package name. Googling a bit I found that there are many apps that use > the same schema. Normally I use my domain to identify my packages in a > unique way like 'com.myweb.myapp'. > > I just tried to reproduce your error and creating 2 apps that use the > same base package name I just get the error when launching them. I > think that the class loader will pickup the first listed package and > then try to load the class (which is not there :P): > - com.package.app.ActivityA > - com.package.app.ActivityB > > If I load com.package.app.ActivityB I'm getting the same error. > > Hope this can help you a bit. > > Cheers, > Moss -- 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
