Status Update
Comments
ni...@gmail.com <ni...@gmail.com> #2
It does show up in 'Android Private Libraries' (this is new?) though as android-support-v4.jar
ni...@gmail.com <ni...@gmail.com> #3
Workaround(?): Go to Properties->Order and export on the app project and check 'Android Private Libraries'.
ni...@gmail.com <ni...@gmail.com> #4
This needs to be done all library projects as well, so that the app project gets the full set of needed jars.
an...@gmail.com <an...@gmail.com> #5
I confirmed this bug. This bug occurs after I upgraded to ADT 22.
I just experienced it a while ago and I was so afraid that all my projects became broken.
Nikolay's workaround works for me:
For all projects (app and library):
1. Right click the project, and choose Properties
2. Go to Java Build Path-Order and Export.
3. Tick 'Android Private Libraries'
---
(Optional) Clean all projects if necessary
Thanks, Nikolay.
I just experienced it a while ago and I was so afraid that all my projects became broken.
Nikolay's workaround works for me:
For all projects (app and library):
1. Right click the project, and choose Properties
2. Go to Java Build Path-Order and Export.
3. Tick 'Android Private Libraries'
---
(Optional) Clean all projects if necessary
Thanks, Nikolay.
wa...@gmail.com <wa...@gmail.com> #6
I will confirm the bug as well. My library projects were working properly on ADT 21.1. After i had updated to ADT 22 to test my applications using the new Android Studio for IntelliJ, everything broke.
Time to downgrade my ADT.
Time to downgrade my ADT.
da...@gmail.com <da...@gmail.com> #7
Did anyone at Google test the ADT 22 release with some real world examples? Suddenly everyone who uses any library projects (eg AdMob!) will have a broken app. One hopes that in the fullness of time a further release will fix this error. In the meantime it might be prudent to at least include a message in the release notes that gives details of the error and workaround. Actually looking at these bug reports might help too. Many sit here for years on end and never get acknowledged, let alone fixed.
an...@gmail.com <an...@gmail.com> #8
On a related note, I got this bug too even for a project without library
project, but external .jar files as library. I still cannot confirm it
though as it happened only once (yes, I immediately solved it using the
aforementioned method)
project, but external .jar files as library. I still cannot confirm it
though as it happened only once (yes, I immediately solved it using the
aforementioned method)
ve...@gmail.com <ve...@gmail.com> #9
Thanks for the workaround. It did work for me.
de...@gmail.com <de...@gmail.com> #10
I also ran into the same problem. It would be nice to have some release notes about these drastic changes popping up right into your face after installing an ADT update. To me it's already the third time that an ADT update breaks stuff that used to work all the time.
Anyway, thank you for the workaround description. It works for me, too.
Anyway, thank you for the workaround description. It works for me, too.
to...@gmail.com <to...@gmail.com> #11
workaround is working for me. I also have ClassNotFoundException on my MainActivity(the project does use support v4 lib) before the workaround
if...@gmail.com <if...@gmail.com> #12
I also ran into this issue after updating to ADT rev 22, this workaround solved my problem
al...@gmail.com <al...@gmail.com> #13
Half a day lost with Android Studio and ADT 22. Thanks for the workaround, it did work for me too.
su...@fivefly.com <su...@fivefly.com> #14
thanks, worked for me too, updating to ADT 22 did not recognise AdMob in libs folder
ja...@gmail.com <ja...@gmail.com> #15
I had the same problem. Thanks for the help.
il...@gmail.com <il...@gmail.com> #16
[Comment deleted]
il...@gmail.com <il...@gmail.com> #17
Thank's Google for supporting developers and testing software on them!
ma...@gmail.com <ma...@gmail.com> #18
I spent quite some time trying to solve this, until I found this. Thanks for the w.a.
already Android studio is braking it for us using eclipse!
already Android studio is braking it for us using eclipse!
fo...@gmail.com <fo...@gmail.com> #19
I wasted hours on this!
lr...@gmail.com <lr...@gmail.com> #20
Had to clean / build all, but back to working. Thank you for saving my productivity level today!
s....@gmail.com <s....@gmail.com> #21
[Comment deleted]
s....@gmail.com <s....@gmail.com> #22
[Comment deleted]
s....@gmail.com <s....@gmail.com> #23
Same here lost about a day at work because of this. Mine was using the old pre-Play Services GCM jar file.
Edit I can confirm that the workaround did work for me. Thank you nikolay....@gmail.com
Edit I can confirm that the workaround did work for me. Thank you nikolay....@gmail.com
jb...@gtempaccount.com <jb...@gtempaccount.com> #24
Thank so much guys, I tried fixing this problem all day yesterday.
ni...@gmail.com <ni...@gmail.com> #25
Should I paste my Bitcoin address here already :)
ta...@gmail.com <ta...@gmail.com> #26
I have the same issue with Android Studio and can't find a workaround.
Does anyone found one for Android Studio yet ?
Does anyone found one for Android Studio yet ?
ma...@gmail.com <ma...@gmail.com> #27
#25: It's because external dependencies are handled manually in build.gradle file. See Gradle documentation.
If you have your dependencies in libs directory, you can use this:
dependencies {
compile fileTree(dir: 'libs', include: '*.jar')
}
If you have your dependencies in libs directory, you can use this:
dependencies {
compile fileTree(dir: 'libs', include: '*.jar')
}
nu...@gmail.com <nu...@gmail.com> #28
#ADT22 also breaks library .jar projects;export workaround will not fix it!
If A includes B which includes/exports C, A no longer sees C! Have to manually copy C into A. Even Maven is smarter than this.
Just another TESTED, QUALITY, Google release.
If A includes B which includes/exports C, A no longer sees C! Have to manually copy C into A. Even Maven is smarter than this.
Just another TESTED, QUALITY, Google release.
rs...@gmail.com <rs...@gmail.com> #29
#26: Even doing this I'm experiencing the same problem here with Android Studio and GSON jar.
ye...@gmail.com <ye...@gmail.com> #30
#28: The same problem for me.
ye...@gmail.com <ye...@gmail.com> #31
I found a solution for the problem with the GSON jar here: http://stackoverflow.com/questions/16608135/android-studio-add-jar-as-library/16612228#16612228
The steps I followed are:
1. Put the Gson jar (in my case, gson-2.2.4.jar) into the libs folder
2. Right click it and hit 'Add as library'
3. Do a clean build. I navigated in a terminal to the root folder of my app and typed gradlew clean. (I'm on Mac)
These steps work for me.
The steps I followed are:
1. Put the Gson jar (in my case, gson-2.2.4.jar) into the libs folder
2. Right click it and hit 'Add as library'
3. Do a clean build. I navigated in a terminal to the root folder of my app and typed gradlew clean. (I'm on Mac)
These steps work for me.
ca...@gmail.com <ca...@gmail.com> #32
Thanks for the workaround...
And Thanks Google for ruining one entire day...
And Thanks Google for ruining one entire day...
xn...@gmail.com <xn...@gmail.com> #33
>Half a day lost with Android Studio and ADT 22
Didn't loose as much as you but 2.5 hours is frustrating enough. Cheers Google.
Didn't loose as much as you but 2.5 hours is frustrating enough. Cheers Google.
da...@gmail.com <da...@gmail.com> #34
I have similar problem with Android Studio, when compiling my app without librarys works fine, later when compiling with andengine (library for games) have error:
"Caused by: java.lang.ClassNotFoundException:com.example.MainTestActivity" it's rare,
I use
"dependencies {
compile fileTree(dir: 'libs', include: '*.jar')
}"
if can help me please I will be very grateful
"Caused by: java.lang.ClassNotFoundException:com.example.MainTestActivity" it's rare,
I use
"dependencies {
compile fileTree(dir: 'libs', include: '*.jar')
}"
if can help me please I will be very grateful
bp...@gmail.com <bp...@gmail.com> #35
These steps did not work for me. I'm using actionBarSherlock in my app and for some reason, I can't remember, I had removed the support library from the android private libraries. I put it back in and my app worked fine again.
sb...@google.com <sb...@google.com>
xa...@android.com <xa...@android.com> #37
We have a fix ready that will properly make this new container exported.
However we can't really force exporting it all the time (the goal of this new container is for the Maven users to be able to mark it as not exported).
However we can't really force exporting it all the time (the goal of this new container is for the Maven users to be able to mark it as not exported).
va...@gmail.com <va...@gmail.com> #38
I am trying to build Sherlock library with ADT 22 , The workaround does not resolve my issue.
Is there any other solution ??
Is there any other solution ??
[Deleted User] <[Deleted User]> #40
[Comment deleted]
ca...@gmail.com <ca...@gmail.com> #41
2000 crash reports and 50+ 1 start ratings after our today's release with this bug. Thanks a lot google.
mr...@gmail.com <mr...@gmail.com> #42
I have same issue!!!
je...@gmail.com <je...@gmail.com> #43
[Comment deleted]
je...@gmail.com <je...@gmail.com> #44
Thanks to the workaround provided above I could fix my project! This bug bled my brain out for 2 hours!
Thanks guys!
Thanks guys!
el...@gmail.com <el...@gmail.com> #45
Happen to me too, struggeled with it for a day or two before Ive found this post... thanks for the workaround!
ze...@gmail.com <ze...@gmail.com> #46
Like always, every new release of ADT breaks random things. It would be useful knowing that updading ADT in Eclipse on SDK manager does not break your workspace and will make you setup again every project in your workspace.
It's windows style. One step forward, two steps back (or at least, side steps). It'd be great if in the process of adding new features the developers environment didn't break in every update.
It's windows style. One step forward, two steps back (or at least, side steps). It'd be great if in the process of adding new features the developers environment didn't break in every update.
ko...@gmail.com <ko...@gmail.com> #47
Happened to new member of our team. The rest of us will not be updating until the fix is pushed.
la...@gmail.com <la...@gmail.com> #48
I updated my ADT to 22.0.1, this issue still exist, why does this issue closed???
I don't understand..
I don't understand..
an...@gmail.com <an...@gmail.com> #49
Just updated to 22.0.1.
From what I observed, this update won't fix the existing projects bug. You
still have to do the workaround to fix that.
However, it fixes for new project by automatically tick the Android Private
Library in Build Path.
Just a quick observation though..
On Jun 4, 2013 3:03 PM, <android@googlecode.com> wrote:
From what I observed, this update won't fix the existing projects bug. You
still have to do the workaround to fix that.
However, it fixes for new project by automatically tick the Android Private
Library in Build Path.
Just a quick observation though..
On Jun 4, 2013 3:03 PM, <android@googlecode.com> wrote:
ar...@gmail.com <ar...@gmail.com> #50
Changing .classpath to the following for main project and all library projects worked for me:
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
<classpathentry kind="src" path="src"/>
<classpathentry kind="src" path="gen"/>
<classpathentry exported="true" kind="con" path="com.android.ide.eclipse.adt.ANDROID_FRAMEWORK"/>
<classpathentry exported="true" kind="con" path="com.android.ide.eclipse.adt.LIBRARIES"/>
<classpathentry exported="true" kind="con" path="com.android.ide.eclipse.adt.DEPENDENCIES"/>
<classpathentry kind="output" path="bin/classes"/>
</classpath>
Same solution as comment #2 , this just mentions what actual files get changed by that modification.
(this is a cross post ofhttp://stackoverflow.com/questions/2247998/noclassdeffounderror-eclipse-and-android/16919014#16919014 )
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
<classpathentry kind="src" path="src"/>
<classpathentry kind="src" path="gen"/>
<classpathentry exported="true" kind="con" path="com.android.ide.eclipse.adt.ANDROID_FRAMEWORK"/>
<classpathentry exported="true" kind="con" path="com.android.ide.eclipse.adt.LIBRARIES"/>
<classpathentry exported="true" kind="con" path="com.android.ide.eclipse.adt.DEPENDENCIES"/>
<classpathentry kind="output" path="bin/classes"/>
</classpath>
Same solution as
(this is a cross post of
cs...@gmail.com <cs...@gmail.com> #51
I got this problem also ...................
co...@gmail.com <co...@gmail.com> #52
This is terrible! Almost as bad as the INSTALL_PARSE_FAILED_NO_CERTIFICATES error.
Does Google skip QA most of the time?
Does Google skip QA most of the time?
va...@gmail.com <va...@gmail.com> #53
Yes, upgrading your ADT is like playing Russian roulette. A new bug breaks stuff each time, but version 22 is the worst. I should have learned my lesson and stayed with version 21.
lu...@gmail.com <lu...@gmail.com> #54
Thank you, Thank you, Thank youuuuuuuuuuuuuuuuuuuu!!!!!!!!!!
el...@gmail.com <el...@gmail.com> #55
The workaround from nikolay worked for me!
mc...@gmail.com <mc...@gmail.com> #56
I am still having this problem. It is showing no class def found exception for some third party jars.
09-04 16:04:16.242: D/dalvikvm(20580): VFY: dead code 0x0005-001b in Lorg/alfresco/mobile/android/api/services/impl/AbstractSiteServiceImpl;.updateExtraPropertyCache (Ljava/lang/String;ZZZ)V
09-04 16:04:16.242: W/System.err(20580): java.lang.NoClassDefFoundError: org.alfresco.mobile.android.api.services.impl.AbstractSiteServiceImpl$1
09-04 16:04:16.242: D/dalvikvm(20580): VFY: dead code 0x0005-001b in Lorg/alfresco/mobile/android/api/services/impl/AbstractSiteServiceImpl;.updateExtraPropertyCache (Ljava/lang/String;ZZZ)V
09-04 16:04:16.242: W/System.err(20580): java.lang.NoClassDefFoundError: org.alfresco.mobile.android.api.services.impl.AbstractSiteServiceImpl$1
fa...@gmail.com <fa...@gmail.com> #57
still have this in December 2013.
ra...@gmail.com <ra...@gmail.com> #58
Following steps fixed my issues of linker errors with third party libraries.
1. Select 'Properties' by right clicking on your android project
2. On the left panel, select 'Java Build Path' and then click on 'Order and Export'
3. Here select all dependency third party libraries and click on 'Ok'
4. Re-Build your project
1. Select 'Properties' by right clicking on your android project
2. On the left panel, select 'Java Build Path' and then click on 'Order and Export'
3. Here select all dependency third party libraries and click on 'Ok'
4. Re-Build your project
ad...@gmail.com <ad...@gmail.com> #59
kr...@gmail.com <kr...@gmail.com> #60
[Comment deleted]
Description
SDK tools version: 22
Eclipse version: 3.7
ADT plug-in version: 22
Platform targeted by your project: API 17
Version of the platform running in the emulator:
STEPS TO REPRODUCE:
1. Select an app that uses a library project and Run As->Android application
2. The app crashes with logcat similar to this:
W/dalvikvm(24464): Unable to resolve superclass of Landroid/support/v4/app/Watso n; (147)
W/dalvikvm(24464): Link of class 'Landroid/support/v4/app/Watson;' failed
W/dalvikvm(24464): Unable to resolve superclass of Lcom/actionbarsherlock/app/Sh erlockFragmentActivity; (158)
W/dalvikvm(24464): Link of class 'Lcom/actionbarsherlock/app/SherlockFragmentAct ivity;' failed
W/dalvikvm(24464): Unable to resolve superclass of Lorg/nick/wwwjdic/ActionBarAc tivity; (332)
W/dalvikvm(24464): Link of class 'Lorg/nick/wwwjdic/ActionBarActivity;' failed
W/dalvikvm(24464): Unable to resolve superclass of Lorg/nick/wwwjdic/Wwwjdic; (6 88)
W/dalvikvm(24464): Link of class 'Lorg/nick/wwwjdic/Wwwjdic;' failed
D/AndroidRuntime(24464): Shutting down VM
W/dalvikvm(24464): threadid=1: thread exiting with uncaught exception (group=0x4 1aba930)
E/AndroidRuntime(24464): FATAL EXCEPTION: main
E/AndroidRuntime(24464): java.lang.RuntimeException: Unable to instantiate activ ity ComponentInfo{org.nick.wwwjdic/org.nick.wwwjdic.Wwwjdic}: java.lang.ClassNot FoundException: Didn't find class "org.nick.wwwjdic.Wwwjdic" on path: /data/app/ org.nick.wwwjdic-2.apk
EXPECTED RESULTS: App starts on device
OBSERVED RESULTS: App crashes due to link error.
ADDITIONAL INFORMATION:
Decompiling the app shows that support library classes haven't been included. It doesn't show up in bin/dexedClasses either. Adding the jar directly to the app project's libs/ doesn't seem to make a difference.