upgraded to 1.5 and apps wont run

by Josh » Wed, 29 Apr 2009 12:08:02 GMT


Sponsored Links
 I upgraded to version 1.5 of the sdk and now when i try to run or
debugg apps i get the following error:


[2009-04-28 21:02:58 - Targets] ------------------------------
[2009-04-28 21:02:58 - Targets] Android Launch!
[2009-04-28 21:02:58 - Targets] adb is running normally.
[2009-04-28 21:02:58 - Targets] Could not find Targets.apk!


Im running eclipse 3.4 and i followed the directions listed here
 http://developer.android.com/sdk/1.5_r1/upgrading.html 

any suggestions?
--~--~---------~--~----~------------~-------~--~----~



upgraded to 1.5 and apps wont run

by Xavier Ducrohet » Wed, 29 Apr 2009 13:52:42 GMT


 Do you have a libs folder in your project?

Xav






-- 
Xavier Ducrohet
Android Developer Tools Engineer
Google Inc.

--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


upgraded to 1.5 and apps wont run

by Josh Dobbs » Wed, 29 Apr 2009 22:33:25 GMT


 Yes I do have a libs folder in the project.






--~--~---------~--~----~------------~-------~--~----~



upgraded to 1.5 and apps wont run

by Xavier Ducrohet » Thu, 30 Apr 2009 02:24:16 GMT


 OK, we have identified a problem where files with no extension in this
folder make the build system break.
Even if you don't have files in there, the presence of a .svn folder
in there can cause the issues.

If you use that folder to store jar libraries. I would just move those
jar files to a different folder (the issue is only with the folder
named "libs" and the jar files can be anywhere as long as they are
added to the project build path).

We have fixed the problem and are looking at possibly releasing an
update to ADT soon.

Xav








-- 
Xavier Ducrohet
Android Developer Tools Engineer
Google Inc.

--~--~---------~--~----~------------~-------~--~----~



upgraded to 1.5 and apps wont run

by fdimeglio » Thu, 30 Apr 2009 04:54:34 GMT


 Xavier,

Yes I confirm that if you are using subversion and having a "libs" dir
in which you have:

- your jar libraries
- the .svn dir

then the build just crap out with ADT 0.9: the resulting .apk contains
everything except the signature and if you "zip -T project.apk" you
will see that the apk file is considered as non valid.

This leads too to the EOCD error you see when trying to push the
broken apk file to an emulator or a device.

When can we expect a fix for this issue ?

Fabrice

PS:

btw I have seen other issues with ADT 0.9: the auto generated resource
file is not generated if you AndroidManifest file is containing <uses-
sdk minSdkVersion="2"> instead of  <uses-sdk
android:minSdkVersion="2">
This was working  with SDK1.1 but with SDK1.5 you need to use the
"android:" prefix






--~--~---------~--~----~------------~-------~--~----~



upgraded to 1.5 and apps wont run

by Xavier Ducrohet » Thu, 30 Apr 2009 05:08:36 GMT


 


hopefully sometimes next week. We're adding a few more fixes.


Yeah we've fixed that too. the minSdkVersion attribute must be in the
android namespace (we've fixed the docs for it too)

This has always been the case, it's just that ADT now parses this
value to display a warning in case this conflicts with the build
target. Unfortunately, if the <uses-sdk> node is present but the
attribute isn't, there's a bug which prevent the rest of the build
from happening.

thanks
Xav
-- 
Xavier Ducrohet
Android Developer Tools Engineer
Google Inc.

--~--~---------~--~----~------------~-------~--~----~



Other Threads

1. Problem to open a internal activity(com.android.browser.BrowserDownloadPage) using sharedUserId.

Hello everybody,

In my application, I need to open the Browser Download History
represented by the activity
com.android.browser.BrowserDownloadPage. But when I start this
activity this error message appears:

WARN/ActivityManager(582): Permission Denial: starting Intent
{ flags=0x10000000 comp={com.android.browser/
com.android.browser.BrowserDownloadPage} } from ProcessRecord{43700fd8
723:com.android.container/10018} (pid=723, uid=10018) requires null

So, I used android:sharedUserId="android.uid.system" in my
AndroidManifest, to get the system permission. This solution resolved
the first problem, but creates a side effect. My application is a
system application (like camera, launcher, etc), it cannot be
uninstalled, so when i run the phone build, my apk is not installed
and this error message appears:

INSTALL_FAILED_UPDATE_INCOMPATIBLE

You guys know why this is happening?
Is there another way to open the Browser Download History?

Thanks!

--~--~---------~--~----~------------~-------~--~----~

2. C&D cyanogen devs comeon, really?

So everytime I have seen someone ask about apps2sd for android, the
response has been something along the lines of 'well if you don't like
the space on the phone modify it yourself if its that easy'  Someone
takes this to heart and does it for free for thousands of users who
are already supporting google and you shut them down?  Now we have to
pick between having space for apps on our phone -OR- not having the
marketplace on our phone anymore so it doesn't even matter?  I highly
suggest if you are going to C&D cyanogen to  give users who have PAID
for a 'powered by google' android device to backup their google apps
that they paid for.  We have paid for the software we should be
entitled to use it with any build of android we choose.  Otherwise,
you might want to try taking user requests a little more seriously.
--~--~---------~--~----~------------~-------~--~----~

3. Packaged Google Apps

4. ImageButton on Graphic Background

5. Is Java JDK 1.6 official supported for Android SDK 1.6

6. Paging bos luckysebastian

7. Why is my file not accesible at data/data ?