Reputation: 35
I am building an app using Eclipse. I got it to work on my device and I am trying to distribute it to a couple friends for them to test it on their phones, but I send them the same .apk I installed in my N1 and they aren't able to install it.
I tried sending them the version from inside the bin/ folder, extract it as an unsigned application or as a signed one, with the same results.
My SDK target is 1.6, so this isn't a problem, because both of them have 2.1+.
The main problem for me is that I have to test the application on real devices, since the emulators don't surf the net if I am connected to Internet through a proxy.
I use a Google keytool because I am using some Maps functionality, so I think that it could be in some way the source of the error, but I don't know what I have to do to fix this. Is it possible that the key is only valid for my device?
I thought that maybe the .apk wasn't working and I could only install it through my USB cable, but I was able to install my app from the same e-mail I sent to my friends.
Thanks in advance!!
Edit: I finally got hold of a friend's device and the error I got was the following, although I was able to install the app via Eclipse (USB cable).
WARN/PackageInstaller(3317): Parse error when parsing manifest. Discontinuing installation
But if the manifest was wrong, I wouldn't be able to install and run the app, right?
Upvotes: 0
Views: 1113
Reputation: 2332
whats the logcat output when the instalation fails ? you can connect to the device using a usb port or use a logcat app from the market
Upvotes: 0
Reputation: 73494
The Google Maps api has both debug and release keys. So if you are using a debug key and generate a release apk, then the Maps api key will be incorrect and your map won't load any tiles.
You should make sure you are using the Maps Api key generated from your release keystore, and export the app in release mode.
Upvotes: 1