Infeasible
Status Update
Comments
ac...@gmail.com <ac...@gmail.com> #2
Although VPN connections under Android 7.1.2 worked for me, they do not work under Android 8.0.0 anymore. (IPSec Xauth PSK)
ra...@gmail.com <ra...@gmail.com> #3
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Steps to reproduce
What steps are needed to reproduce this issue?
Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)
Expected output
What is the expected output?
Current output
What is the current output?
Android bug report
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.
Alternate method:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.
Steps to reproduce
What steps are needed to reproduce this issue?
Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)
Expected output
What is the expected output?
Current output
What is the current output?
Android bug report
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.
Alternate method:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.
ra...@gmail.com <ra...@gmail.com> #4
Please provide the information requested in comment #2 to investigate further.
ac...@gmail.com <ac...@gmail.com> #5
Please provide the information requested in comment #3 to investigate further.
un...@googlemail.com <un...@googlemail.com> #6
Hi I Am experiencing the same issues as mentioned by the topic starter. I've tried to create a bug report, but i haven't rooted my device. However, i have attached the log of my VPN-router below.
Steps to reproduce
Configure a L2TP / IPsec PSK VPN using the native VPN client on Android 8 and try to connect
Frequency
Issue occurs 100% of the time.
Expected output
Connected to VPN
Current output
Message that connection failed.
Router log (IP-ADRES = the IP address of the Android)
2017-10-20 13:12:21 [IPSEC/IKE][Local][66:-][@IP-ADRES] may be security method/sbunet setting/GRE setting unmatched?
2017-10-20 13:12:21 [IPSEC/IKE][Local][66:-][@IP-ADRES] state transition fail: STATE_QUICK_R0
2017-10-20 13:12:19 sent MR3, ISAKMP SA established with IP-ADRES. In/Out Index: 66/0
2017-10-20 13:12:19 Matching General Setup key for dynamic ip client...
2017-10-20 13:12:19 NAT-Traversal: Using RFC 3947, no NAT detected
2017-10-20 13:12:19 Accept Phase1 prorosals : ENCR OAKLEY_AES_CBC, HASH OAKLEY_SHA
2017-10-20 13:12:19 Matching General Setup key for dynamic ip client...
2017-10-20 13:12:19 Find Phase1 proposal: SHA2_256
2017-10-20 13:12:19 Matching General Setup key for dynamic ip client...
2017-10-20 13:12:19 Find Phase1 proposal: SHA2_256
2017-10-20 13:12:19 Matching General Setup key for dynamic ip client...
2017-10-20 13:12:19 Matching General Setup key for dynamic ip client...
2017-10-20 13:12:19 Responding to Main Mode from IP-ADRES
Thanks for looking into this and good luck!
Steps to reproduce
Configure a L2TP / IPsec PSK VPN using the native VPN client on Android 8 and try to connect
Frequency
Issue occurs 100% of the time.
Expected output
Connected to VPN
Current output
Message that connection failed.
Router log (IP-ADRES = the IP address of the Android)
2017-10-20 13:12:21 [IPSEC/IKE][Local][66:-][@IP-ADRES] may be security method/sbunet setting/GRE setting unmatched?
2017-10-20 13:12:21 [IPSEC/IKE][Local][66:-][@IP-ADRES] state transition fail: STATE_QUICK_R0
2017-10-20 13:12:19 sent MR3, ISAKMP SA established with IP-ADRES. In/Out Index: 66/0
2017-10-20 13:12:19 Matching General Setup key for dynamic ip client...
2017-10-20 13:12:19 NAT-Traversal: Using RFC 3947, no NAT detected
2017-10-20 13:12:19 Accept Phase1 prorosals : ENCR OAKLEY_AES_CBC, HASH OAKLEY_SHA
2017-10-20 13:12:19 Matching General Setup key for dynamic ip client...
2017-10-20 13:12:19 Find Phase1 proposal: SHA2_256
2017-10-20 13:12:19 Matching General Setup key for dynamic ip client...
2017-10-20 13:12:19 Find Phase1 proposal: SHA2_256
2017-10-20 13:12:19 Matching General Setup key for dynamic ip client...
2017-10-20 13:12:19 Matching General Setup key for dynamic ip client...
2017-10-20 13:12:19 Responding to Main Mode from IP-ADRES
Thanks for looking into this and good luck!
al...@nubbus.com <al...@nubbus.com> #7
Steps to reproduce:
1. Setup VPN connection using IPSec Xauth PSK with IPSec key
2. Connect to VPN server
3. Connection attempt will fail
Frequency
100%
Expected output
Connect to VPN server successfully
Current output
Connection attempt fails
1. Setup VPN connection using IPSec Xauth PSK with IPSec key
2. Connect to VPN server
3. Connection attempt will fail
Frequency
100%
Expected output
Connect to VPN server successfully
Current output
Connection attempt fails
al...@gmail.com <al...@gmail.com> #8
It works for me but only "non-permanent".
As soon as I actvate "permanent" it cant connect... like in 6.x and 7.x (now 8.0.0)
As soon as I actvate "permanent" it cant connect... like in 6.x and 7.x (now 8.0.0)
kr...@gmail.com <kr...@gmail.com> #9
oh sry... its "Always On" in english version
zo...@gmail.com <zo...@gmail.com> #10
Reply comment #7 :
Can you please check whether issue is reproducible with latest Android 8.1.0 build(OPM1.1171019.011) for Pixel device?
If issue is still reproducible, please capture a bugreport and share it here.
Can you please check whether issue is reproducible with latest Android 8.1.0 build(OPM1.1171019.011) for Pixel device?
If issue is still reproducible, please capture a bugreport and share it here.
co...@gmail.com <co...@gmail.com> #11
Issue still reproducible with Android 8.1.0 build(OPM1.1171019.011) on Pixel device.
ma...@gmail.com <ma...@gmail.com> #12
Could fix this issue now by removing the whole VPN user account and create a new one. Now the connection works again. As I'm not sure if I tried that with an earlier Android version I can only say that there must be at least an issue with my VPN system (AVM Fritz!Box 7490).
th...@gmail.com <th...@gmail.com> #13
For anyone having similar issues, see my recent comments here https://issuetracker.google.com/issues/37074640#comment366
I'm curious if these are related or if my case is unique. If possible run 'ifconfig' on the device while trying to connect and compare the MTU of the ppp0 interface with that of your main wifi/LTE interface
I'm curious if these are related or if my case is unique. If possible run 'ifconfig' on the device while trying to connect and compare the MTU of the ppp0 interface with that of your main wifi/LTE interface
co...@gmail.com <co...@gmail.com> #14
Thank you for your feedback. We assure you that we are doing our best to address the issue reported, however our product team has shifted work priority that doesn't include this issue. For now, we will be closing the issue as won't fix obsolete. If this issue currently still exists, we request that you log a new issue along with latest bug report here https://goo.gl/TbMiIO .
cr...@gmail.com <cr...@gmail.com> #15
Code changed and optimized, a couple of assets were trimmed down anyway, and manifest modified only in versionCode.
Nothing that should let me think of a new problem introduced btw.
Nothing that should let me think of a new problem introduced btw.
cr...@gmail.com <cr...@gmail.com> #16
[Comment deleted]
ma...@gmail.com <ma...@gmail.com> #17
[Comment deleted]
ma...@gmail.com <ma...@gmail.com> #18
After upload the same apk 300 times, it final work's. strange bug..
Bug is a ugly bug from google market.
Bug is a ugly bug from google market.
co...@gmail.com <co...@gmail.com> #19
It's fixed!
th...@gmail.com <th...@gmail.com> #20
Hi, girls and guys. It's working now.
rr...@gmail.com <rr...@gmail.com> #21
i have:
<!-- <uses-configuration />
<uses-feature />-->
works for my free app then change to tjhe paid one and it doesnt work - some error message ould be rather handy
i can't deploy and dont know why....
<!-- <uses-configuration />
<uses-feature />-->
works for my free app then change to tjhe paid one and it doesnt work - some error message ould be rather handy
i can't deploy and dont know why....
rr...@gmail.com <rr...@gmail.com> #22
not working for me , tried everything made some code changes, test on devices all fine but still i get this error.
sooooo frustrating. Is it a temporary bug? i Have seen it before and doing a rebuild seemed to fix it.
sooooo frustrating. Is it a temporary bug? i Have seen it before and doing a rebuild seemed to fix it.
an...@gmail.com <an...@gmail.com> #23
The same problem for me with an application which was accepted before...
PLEASE GOOGLE CHANGE THE MESSAGE AND INFORM US ABOUT WHAT'S WRONG ABOUT OUR APPS, WE CAN'T BE THOUSANDS OF PEOPLE LOOKING FOR "SOMETHING" WE DON't HAVE ANY INFORMATION ABOUT.
PLEASE GOOGLE CHANGE THE MESSAGE AND INFORM US ABOUT WHAT'S WRONG ABOUT OUR APPS, WE CAN'T BE THOUSANDS OF PEOPLE LOOKING FOR "SOMETHING" WE DON't HAVE ANY INFORMATION ABOUT.
au...@gmail.com <au...@gmail.com> #24
same problem and no explication what's wrong
ma...@gtempaccount.com <ma...@gtempaccount.com> #25
This is happening to me right now. This is a very frustrating issue.
gr...@gmail.com <gr...@gmail.com> #26
Same problem here. Have tried uploading like 50 times with no luck.
ro...@gmail.com <ro...@gmail.com> #27
Same here...
ir...@gmail.com <ir...@gmail.com> #28
[Comment deleted]
ir...@gmail.com <ir...@gmail.com> #29
same here... this really sucks, my app has a bug and i just cant fix it...
ni...@gmail.com <ni...@gmail.com> #30
same issue here. Please, at least identify it as an app problem or a Market bug
an...@dauntless-soft.com <an...@dauntless-soft.com> #31
google sucks - this is the worst problem, ever. period
ra...@gmail.com <ra...@gmail.com> #32
"Priority-Medium"? You mean "fatal" or "high" by any chance? People can't upload apps... I fail to see what could be higher priority than this.
su...@movingfloats.com <su...@movingfloats.com> #33
I have been trying to deal with this issue since last 5 hours ,without any luck. Can someone please let me know if there is a way i can validate the XML file ???
mk...@gmail.com <mk...@gmail.com> #34
Same problem here. It has been going on for 2 days now. The same APK uploaded to the Amazon App Store just fine. Google please help.
ro...@gmail.com <ro...@gmail.com> #35
What the hell. After 11 months of development I just got this message too. Why on earth are we not told what actually caused the failure?
[Deleted User] <[Deleted User]> #36
Same here. After upgrading the app with a few minor changes, I cannot upload the new APK anymore getting the "The server could not process your apk. Try again" error!
my...@gmail.com <my...@gmail.com> #37
same here..weird
w....@gmail.com <w....@gmail.com> #38
Please escalate this to high priority
br...@gmail.com <br...@gmail.com> #39
bump, no empty "uses-configuration" tag either. AndroidManifest.xml has not changed
th...@gmail.com <th...@gmail.com> #40
[Comment deleted]
th...@gmail.com <th...@gmail.com> #41
Today there is a similar problem with all my projects. No changes in manifests... :(
al...@googlemail.com <al...@googlemail.com> #42
Same issue here today, seems to be a BROKEN MARKET - AGAIN... Will try during the next hours. Am I the only one who is really really unhappy with this issue, and the fact that there seems to be NO official feedback on this topic.
Correct me if I overlooked an OFFICIAL statement from google on this topic, but before you get out new versions of Android, new funny features, PLEASE get the basics right. Or AT LEAST provide error codes, something like "ABC123 - Server hickups, not your fault, try again later"
Correct me if I overlooked an OFFICIAL statement from google on this topic, but before you get out new versions of Android, new funny features, PLEASE get the basics right. Or AT LEAST provide error codes, something like "ABC123 - Server hickups, not your fault, try again later"
al...@googlemail.com <al...@googlemail.com> #43
Oh, and please STAR this topic (seem to reflect severity) and author, if you can, change to critical. This is really really a thing which should not happen in a professional environment (Google is not a 3 people startup) - IF its really caused by the server (no comment, so who knows, maybe we are all just stupid :-)
de...@gmail.com <de...@gmail.com> #44
cant upload:(
and total installs (users) did not refresh.
and total installs (users) did not refresh.
pp...@gmail.com <pp...@gmail.com> #45
Also can't upload an update.. no data is transferred between my workstation and the market's servers, I just get that error: The server could not process your apk. Try again.
Come on Google, fix it.
Come on Google, fix it.
mu...@gmail.com <mu...@gmail.com> #46
same problem :( "The server could not process your apk. Try again."
rr...@gmail.com <rr...@gmail.com> #47
I was getting this error and I switched to maven builds for deploying and I haven't had the error since.
po...@gmail.com <po...@gmail.com> #48
What is a Maven Build?
rr...@gmail.com <rr...@gmail.com> #49
it's a build tool tool like ant - not a trivial setup though. search for maven android plugin.
kl...@gmail.com <kl...@gmail.com> #50
Same problem here, doesn't work since like 3 hours of trying.
de...@gmail.com <de...@gmail.com> #51
i can't upload new app screenshots.
an...@wheely.com <an...@wheely.com> #52
Update Eclipse ADT plugin to the latest(r16) version and now I have this error.
kl...@gmail.com <kl...@gmail.com> #53
same problem!
de...@gmail.com <de...@gmail.com> #54
still having this problem:(
zh...@gmail.com <zh...@gmail.com> #55
I Have same problem..
please quick fix it.
please quick fix it.
mi...@gmail.com <mi...@gmail.com> #56
Yep, I can't upload my apk either, keep getting: The server could not process your apk. Try again
And I've not made any changes apart from upgrade version number in xml file.
And I've not made any changes apart from upgrade version number in xml file.
n7...@gmail.com <n7...@gmail.com> #57
same here.
te...@gmail.com <te...@gmail.com> #58
Same here. Only versionCode and versionName changed.
fa...@gmail.com <fa...@gmail.com> #59
One more to the list ,, First time in since I started development but clueless of what to do. I sent a support email to google.. will update here IF i get a response :)
al...@googlemail.com <al...@googlemail.com> #60
Any way to escalate this - it has been nearly 8 hours now, this is SEVER...
Oh, and keep posting "here too", but stopp worrying about your config - its not you, its THEM :-)
Oh, and keep posting "here too", but stopp worrying about your config - its not you, its THEM :-)
de...@gmail.com <de...@gmail.com> #61
FFFIIIIIXXX ITTTTTTTT NOWWW!!!!!
kp...@gmail.com <kp...@gmail.com> #62
Why is this happening? Why are there no better messages? Why aren't google announcing that they're working on it at least? why? whyyy? whyyyyyyy?
de...@gmail.com <de...@gmail.com> #63
finally google post something
22 February 2012: Application uploading and editing issues.
We are aware of issues with uploading and editing applications in the Android Market Developer Console. We apologize for this inconvenience and are working to fix this as soon as we can.
22 February 2012: Application uploading and editing issues.
We are aware of issues with uploading and editing applications in the Android Market Developer Console. We apologize for this inconvenience and are working to fix this as soon as we can.
mj...@gmail.com <mj...@gmail.com> #64
Just throwing my $0.02 in. Not working for me either. I'm using a build from Phonegap's build service and never had a problem before.
Glad to see Google has acknowledged the issue. Anyone know how long these things typically take to get resolved?
Glad to see Google has acknowledged the issue. Anyone know how long these things typically take to get resolved?
al...@googlemail.com <al...@googlemail.com> #65
They could also monitor this list a little bit better. Just my idea, I think they should have some experience with algorithms :-)
So if a topic without any post for 3 month suddenly gets 20+ posts from DIFFERENT users, it should change the severity to CRITICAL by default. We still don't know if they will update this topic, or some other post somewhere in the net.
@devandro - could you keep us posted about news?
So if a topic without any post for 3 month suddenly gets 20+ posts from DIFFERENT users, it should change the severity to CRITICAL by default. We still don't know if they will update this topic, or some other post somewhere in the net.
@devandro - could you keep us posted about news?
kl...@gmail.com <kl...@gmail.com> #66
Now it's working for me.
mu...@gmail.com <mu...@gmail.com> #67
Work fine now.
w....@gmail.com <w....@gmail.com> #68
I think the real problem here is the server responds with "The server could not
process your apk. Try again." Which gives you the impression that something is wrong with your APK, when in fact it entirely a market server issue. It should say something like "Woops, our servers are not working right now, please try again in a few hours".
process your apk. Try again." Which gives you the impression that something is wrong with your APK, when in fact it entirely a market server issue. It should say something like "Woops, our servers are not working right now, please try again in a few hours".
an...@gmail.com <an...@gmail.com> #69
Google says this bug is Fixed on Feb22, but its still happening... :(
lm...@gmail.com <lm...@gmail.com> #70
Tried to upload the exact same apk for about 15 times and finally got it through!
Agree with @W.Dona that Google should respond with a more accurate message so that we won't need to scratch our heads on what went wrong in our code/manifest/compilation process.
And this problem is approaching 3 years old!
Agree with @W.Dona that Google should respond with a more accurate message so that we won't need to scratch our heads on what went wrong in our code/manifest/compilation process.
And this problem is approaching 3 years old!
yy...@gmail.com <yy...@gmail.com> #71
same here, today try to upload my app. about 12.4MB. but upload fail.
any ideal??? how to fix it???
any ideal??? how to fix it???
sn...@gmail.com <sn...@gmail.com> #72
I got the same error. what's going on???
ta...@gmail.com <ta...@gmail.com> #73
I tried to upload my 48MB apk eleven times. It succeeded.
mn...@xtra.co.nz <mn...@xtra.co.nz> #74
[Comment deleted]
mn...@xtra.co.nz <mn...@xtra.co.nz> #75
Hi guys.. just wanted to let you know.. I encountered the same issue (unsuccessful for 7 attempts). Changed the android app version & version name in the manifest file and it went through without a hitch. :-) (probably there is a check to ensure the app with the same app version is not accidentally overwritten)
ra...@gmail.com <ra...@gmail.com> #76
I'm having this error. Did anyone solve this?
je...@gmail.com <je...@gmail.com> #77
It's cropped up for me again as well (since yesterday).
vi...@photosbyvickyleon.com <vi...@photosbyvickyleon.com> #78
having this issue now. Upload wit 5.5 MB for apk. Pls check it, google supporter :((
je...@gmail.com <je...@gmail.com> #79
This is still persisting for me... approx 4 days later.
ra...@gmail.com <ra...@gmail.com> #80
I finally solved my problem regarding this issue. I've written a blog on this. You can find it here
http://rafiqnayan.blogspot.com/2012/09/server-could-not-process-your-apk.html
Hope this will help some of you. It'll be very encouraging for me if you put your valuable comments in my blog.
Thanks
Rafiqunnabi Nayan
Bangladesh
Hope this will help some of you. It'll be very encouraging for me if you put your valuable comments in my blog.
Thanks
Rafiqunnabi Nayan
Bangladesh
de...@gmail.com <de...@gmail.com> #81
[Comment deleted]
de...@gmail.com <de...@gmail.com> #82
Same issue. How can a huge company like Google allow this to persist for such a long time?
Apple would never allow this to happen.
Google sucks!
Apple would never allow this to happen.
Google sucks!
je...@gmail.com <je...@gmail.com> #83
This is happening for me.
It is October 21st.
This thread was started back in February.
30 people are not important to Google to update the error message to something meaningful.
Ok, google, you don't like my APK update then another store will.
Oh and don't forget that i paid money to be on Android marketplace, seems i am seeing just what my dollars mean to you guys - nothing.
It is October 21st.
This thread was started back in February.
30 people are not important to Google to update the error message to something meaningful.
Ok, google, you don't like my APK update then another store will.
Oh and don't forget that i paid money to be on Android marketplace, seems i am seeing just what my dollars mean to you guys - nothing.
je...@gmail.com <je...@gmail.com> #84
Fixed.
It was not uploading anything, only dropping me this meaningless error.
I routed my internet through a VPN to UK and it worked.
So in my case the error means "Uploads from the country of your IP address are not allowed" .. which still makes no sense since the marketplace is available here... but my developer account is in the UK.
Come on google. Think for minute about the user and perhaps give them a message that is useful.
It was not uploading anything, only dropping me this meaningless error.
I routed my internet through a VPN to UK and it worked.
So in my case the error means "Uploads from the country of your IP address are not allowed" .. which still makes no sense since the marketplace is available here... but my developer account is in the UK.
Come on google. Think for minute about the user and perhaps give them a message that is useful.
du...@gmail.com <du...@gmail.com> #85
This is such an annoying long standing issue. I've hit this pretty much every time I've tried to update our apks over the last few years. Such a waste of time.
The most reliably way I have of uploading is to tether to my phone and upload over 3G, which takes much longer but for some reason seems not to give the stupid message.
It's unbelievable that this is still an issue after so long.
The most reliably way I have of uploading is to tether to my phone and upload over 3G, which takes much longer but for some reason seems not to give the stupid message.
It's unbelievable that this is still an issue after so long.
mi...@gmail.com <mi...@gmail.com> #86
Same issue in Jan 2013! Have been trying to upload a minor up date to my apps and have only changed the version code and Version name in the manifest. I am at a university using their internet, I tried two different browsers and the upload byte counter never got passed 0. However, I connected through 3g and the app fully uploaded 5.3MB, then started counting backwards and then resulted in the same error message. I contacted google and they sent me a generic e-mail about "General problems submitting applications" which of course outlined errors in your manifest and other generic debugging topics, but this is my 5th update in two years and I have never encountered this.
jb...@android.com <jb...@android.com> #87
This report applies to Google Play, and the issue tracker where you reported it specializes in issues within the Open Source source code of the Android platform.
We are not able to provide support for Google Play in this issue tracker. Please use the Google Support site for user help athttps://support.google.com/googleplay/ or developer help at https://support.google.com/googleplay/android-developer/ , or report this issue in the most appropriate Google Product Forum at https://productforums.google.com/forum/#!forum/en/
We are not able to provide support for Google Play in this issue tracker. Please use the Google Support site for user help at
Description
- Steps to reproduce the problem
I have been uploading regular upgrades to CTA Tracker Pro to the Android
Market through the Developer Console. Beginning 26-Apr-2009, I was unable
to upload any upgrades. The server responded with "The server could not
process your apk. Try again." The only change in AndroidManifest.xml
previous to this was the addition of <uses-sdk android:minSdkVersion="1" /> .
My original AndroidManifest.xml was structured as follows (note that
package names have been modified for public consumption):
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="
package="com.my.package" android:versionName="1.071"
android:versionCode="20">
<uses-sdk android:minSdkVersion="1" />
<application android:icon="@drawable/icon" android:label="@string/
app_name"
android:name="com.my.package.MyApplication">
<activity android:name=".MyAppActivity" android:label="@string/
app_name">
<intent-filter>
<action
android:name="android.intent.action.MAIN" />
<category
android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
<activity android:name="RouteChooser"></activity>
<activity android:name="DirChooser"></activity>
<activity android:name="StopChooser"></activity>
<activity android:name="UserRouteNameActivity"></activity>
<activity android:name="PreferencesActivity"></activity>
<activity android:name="com.my.package.map.MapViewActivity"></
activity>
<uses-library android:name="com.google.android.maps" />
</application>
<uses-permission android:name="android.permission.VIBRATE"></uses-
permission>
<uses-permission android:name="android.permission.INTERNET"></uses-
permission>
</manifest>
I was able to finally upgrade the application without receiving "The server
could not process your apk. Try again." by adjusting the Manifest to be:
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="
package="com.my.package" android:versionName="1.071"
android:versionCode="20">
<uses-sdk android:minSdkVersion="1" />
<uses-permission android:name="android.permission.VIBRATE"></
uses-
permission>
<uses-permission android:name="android.permission.INTERNET"></
uses-
permission>
<application android:icon="@drawable/icon"
android:label="@string/
app_name"
android:name="com.my.package.MyApplication">
<uses-library android:name="com.google.android.maps" /
<activity android:name=".MyAppActivity"
android:label="@string/
app_name">
<intent-filter>
<action
android:name="android.intent.action.MAIN" />
<category
android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
<activity android:name="RouteChooser"></activity>
<activity android:name="DirChooser"></activity>
<activity android:name="StopChooser"></activity>
<activity android:name="UserRouteNameActivity"></
activity>
<activity android:name="PreferencesActivity"></
activity>
<activity
android:name="com.my.package.map.MapViewActivity"></
activity>
</application>
</manifest>
Note the two changes from the non-working version I posted are:
- All the <uses-permission> lines moved to the top, which I do not
think made any difference.
- The <uses-library> line moved to the top of <application>, which
finally fixed this problem.
The placement of <uses-library> should not invalidate the XML; furthermore,
the placement of <uses-library> in the original, non-working version
correctly matched the documentation here
(
yet was un-parseable by the server.