While Uploading App in Google Play is shows Upload

2020-04-02 10:08发布

问题:

Please any one tell how to remove this error.

Thanks

回答1:

I faced that issue as well. I tried different builds, even old ones, previously uploaded without any issues. Rebuilding, cleaning and still got the same error. Nothing really helped.

I think it's Google Play problem because it just started working after some time (uploading exactly the same apk which was earlier rejected).

So take a sit and wait.
Nice try Google.



回答2:

I also ran into this problem. Our app was originally using an XML for the icon in the manifest:

<?xml version="1.0" encoding="utf-8"?>
<selector xmlns:android="http://schemas.android.com/apk/res/android">

    <item android:drawable="@drawable/icon_default" />

</selector>

This has been working for years. But when I tried to upload my new build this week, I was getting the "icon invalid" error. I tried to make sure I had a icon png in all of the res folders for all resolutions but that didn't fix it. Finally, I tried removing the XML and in the manifest, just point the android:icon directly to the PNG. That seemed to fix the problem.



回答3:

Created a bug report for this: https://code.google.com/p/android/issues/detail?id=229018

Tried very hard to not add any insults as to the quality of the error message and the coder who's responsible.



回答4:

What worked for me today November 2016:

  1. Created the application icon under "mipmap" using "new" > "image asset" dialog.
  2. Then I removed the old icon from drawable floder.
  3. Update the manifest to point to the newly created since the name and folder has changed.


回答5:

I have solved the issue. I have renamed the apk file to zip and explore the drawable folder and found there was some images which i have already deleted from project but they are still showing in apk. After deletion of those files the apk uploaded successfully. I do not why the deleted images still in apk's drawable folder.



回答6:

Do a clean build under Build in Android Studio it fixed the issue for me.