my 2 cents:
there must be something about the verify process.
* without further investigation, the whole smack api  is now failing.
 a lot of this seems to be caused by awt or javax classes missing.

* what will verify accept or reject on which base ?

* anyhow, if my installation fails the first time, i'm now stuck:
 adb uninstall fails without error message,
 adb install -r fails with replace_couldnt_delete


On Aug 18, 11:20 pm, "Justin (Google Employee)" <[EMAIL PROTECTED]>
wrote:
> Okay, I think we're all getting confused by overloaded words here.
>
> Alex, I believe you are asking about non-public APIs, that is
> undocumented classes. These classes are no longer accessible, I
> believe in M5 some undocumented classes could be accessed by
> application code. The reason access is disallowed is because, well,
> they're not public APIs.
>
> Shane, I believe you are inferring something about Java private and
> inner classes. There is, of course, no restriction on creating Java
> private or inner classes on Android.
>
> Hopefully this clarifies things.
>
> Cheers,
> Justin
> Android Team @ Google
>
> On Aug 18, 2:07 pm, Alex Pisarev <[EMAIL PROTECTED]> wrote:
>
> > Justin,
>
> > Is there any reasonable explaination why private classes are banned
> > now?
>
> > Regards,
> > Alex
>
> > On 18 авг, 14:02, "Justin (Google Employee)" <[EMAIL PROTECTED]> wrote:
>
> > > What do you mean by 'internal' classes? You mean inner classes or
> > > private classes? If you mean private classes, I believe, yes, this is
> > > now no longer allowed.
>
> > > Cheers,
> > > Justin
> > > Android Team @ Google
>
> > > On Aug 18, 1:50 pm, Alex Pisarev <[EMAIL PROTECTED]> wrote:
>
> > > > I ported my app, did a clean build and when trying to deploy it to the
> > > > emulator I get the following error:
>
> > > > >adb install AndroCom.apk
>
> > > > 1882 KB/s (0 bytes in 2048642.001s)
> > > >         pkg: /data/local/tmp/AndroCom.apk
> > > > Failure [-11]
>
> > > > adb logcat output:
>
> > > > D/PackageParser(   54): Scanning package: /data/app/vmdl38741.tmp
> > > > D/dalvikvm(   54): GC freed 4942 objects / 310576 bytes in 55ms
> > > > D/dalvikvm(   54): GC freed 3353 objects / 354784 bytes in 52ms
> > > > D/dalvikvm(   54): GC freed 6596 objects / 290648 bytes in 57ms
> > > > D/dalvikvm(   54): GC freed 20120 objects / 868592 bytes in 86ms
> > > > D/dalvikvm(   54): GC freed 20197 objects / 732088 bytes in 82ms
> > > > D/dalvikvm(   54): GC freed 20071 objects / 728032 bytes in 96ms
> > > > D/PackageManager(   54): Scanning package com.android.commandro
> > > > I/PackageManager(   54): /data/app/vmdl38741.tmp changed; unpacking
> > > > I/dalvikvm(   27): Opening files: input='/data/app/vmdl38741.tmp'
> > > > cache='/data/d
> > > > alvik-cache/[EMAIL PROTECTED]@[EMAIL PROTECTED]'
> > > > D/dalvikvm(   27): DexInv: --- BEGIN 'vmdl38741.tmp' (bootstrap=0) ---
> > > > D/dalvikvm(   27): DexInv: waiting for verify+opt, pid=209
> > > > D/dalvikvm(  209): Unable to resolve superclass of Lcom/android/
> > > > commandro/activi
> > > > ties/AddLocationActivity$LocationActivityOverlay; (885)
> > > > D/dalvikvm(  209): Link of class 'Lcom/android/commandro/activities/
> > > > AddLocationA
> > > > ctivity$LocationActivityOverlay;' failed
>
> > > > I get tons of other "link of class blah-blah" failed errors - merely
> > > > for every internal class of the application...
>
> > > > What's wrong - we're not allowed to have internal classes anymore or
> > > > what?- Скрыть цитируемый текст -
>
> > > - Показать цитируемый текст -
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
[EMAIL PROTECTED]
Announcing the new Android 0.9 SDK beta!
http://android-developers.blogspot.com/2008/08/announcing-beta-release-of-android-sdk.html
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to