xxxhdpi icon not working? need it to be featured

Solar2D Android
#1

Hey guys im really stuck, i have a game which is planned to be featured on google over xmas time.

I have resolved all issues they sent me, but one. xxxhdpi is not being found?

Can someone from corona please reply as im running out of time!?

here is their reply.

* Must resolve before feature:

  • The app must have a xxxhdpi (192 x 192 px) launcher icon so that the newest class of devices with high-density displays are best supported.  Please note that launcher icons should be placed in /res/mipmap-[density]/ folders and set android:icon="@mipmap/app_icon" in manifest file as outlined in the following: http://developer.android.com/guide/practices/screens_support.html#support

I have the icon Icon-xxxhdpi.png sized 192x192 in my base directory and i used the build 2016.2999 but above is what they have told me.

#2

Hi chris_raz,

It sounds like Google wants the icons in the /res/mipmap-[density] directory. Corona-made Android apps currently put all launcher icons in the /res/drawable-[density].

You can verify that your Corona-made app includes the Icon you’ve provided by unzipping the.apk generated by Corona’s build system and looking for an icon.png in the /res/drawable-xxxhdpi-v4 directory.

#3

Hi Ajay, Thank you so much for the quick reply,

I just unzipped the apk file and the icon.png is in the /res/drawable-xxxhdpi-v4 directory.

Is there anything you can do on your end? as they keep coming back to me with this issue. and as stated above in their reply its a must resolve before feature which will be over xmas which will be huge for me and my time is running out for it to be approved. please let me know

from reading the link they sent, it seems they do want it in the mipmap-density folder, here is a snipet from the link.

Note: Place all your launcher icons in the res/mipmap-[density]/ folders, rather than the res/drawable-[density]/ folders. The Android system retains the resources in these density-specific folders, such as mipmap-xxxhdpi, regardless of the screen resolution of the device where your app is installed. This behavior allows launcher apps to pick the best resolution icon for your app to display on the home screen. For more information about using the mipmap folders, see Managing Projects Overview.

Again please let me know what can be done.

many thanks,

Chris.

#4

Hi Ajay Any news on this?

#5

Hi chris_raz,

We’re investigating a resolution to this issue now. Currently it looks like we may need to accelerate some other Android maintenance items to make this happen. In particular, Google introduced the /res/mipmap directory with Android 3.0, where Corona currently supports as far back as Android 2.3.x.

Google is apparently planning on dropping Android 2.3.x support with the next version of Google Play Services, so we’ve been looking to go in a similar direction.

I’ll keep you posted on any news related to this.

#6

Thanks Ajay, do you have any approximate timeline? As you can understand with my time constraint, i will need to get back to them very soon.

#7

A rough guess would be the end of this week or early next week. Bundling an Android APK to put launcher icons in the res/mipmap directory isn’t the difficult part (as I’ve already got that bit working). The ramifications of dropping Android 2.3.x is the more thought-provoking, time-consuming part.

#8

Ok thank you so much Ajay, I really appreciate your help on this one. If you can keep me updated when it’s implemented that would be great as I need to update them so I don’t miss this opportunity. Thank you again

#9

Hi chris_raz,

The latest daily build should address your issue with getting featured on Google Play. It also drops support for Android 2.3.3 - Android 4.0.2 as I had mentioned as a possibility before.

See the blog post for more details.

#10

Thank you so much Ajay! I truly appreciate that.

Just to confirm from the blog post, i also need to update the app to the latest gpgs plugin and admob plugin as part of this right?

#11

You’ll likely want/need to do those for other reasons, but that’s not strictly required for this change. If you’re using the legacy gameNetwork-Google plugin, you’ll most likely need to update if you’re also using the free AdMob support in plugin.google.play.services however.

#12

Cool no probs, will update both in any case. Thanks so much again Ajay! Really appreciate it

#13

Hi chris_raz,

It sounds like Google wants the icons in the /res/mipmap-[density] directory. Corona-made Android apps currently put all launcher icons in the /res/drawable-[density].

You can verify that your Corona-made app includes the Icon you’ve provided by unzipping the.apk generated by Corona’s build system and looking for an icon.png in the /res/drawable-xxxhdpi-v4 directory.

#14

Hi Ajay, Thank you so much for the quick reply,

I just unzipped the apk file and the icon.png is in the /res/drawable-xxxhdpi-v4 directory.

Is there anything you can do on your end? as they keep coming back to me with this issue. and as stated above in their reply its a must resolve before feature which will be over xmas which will be huge for me and my time is running out for it to be approved. please let me know

from reading the link they sent, it seems they do want it in the mipmap-density folder, here is a snipet from the link.

Note: Place all your launcher icons in the res/mipmap-[density]/ folders, rather than the res/drawable-[density]/ folders. The Android system retains the resources in these density-specific folders, such as mipmap-xxxhdpi, regardless of the screen resolution of the device where your app is installed. This behavior allows launcher apps to pick the best resolution icon for your app to display on the home screen. For more information about using the mipmap folders, see Managing Projects Overview.

Again please let me know what can be done.

many thanks,

Chris.

#15

Hi Ajay Any news on this?

#16

Hi chris_raz,

We’re investigating a resolution to this issue now. Currently it looks like we may need to accelerate some other Android maintenance items to make this happen. In particular, Google introduced the /res/mipmap directory with Android 3.0, where Corona currently supports as far back as Android 2.3.x.

Google is apparently planning on dropping Android 2.3.x support with the next version of Google Play Services, so we’ve been looking to go in a similar direction.

I’ll keep you posted on any news related to this.

#17

Thanks Ajay, do you have any approximate timeline? As you can understand with my time constraint, i will need to get back to them very soon.

#18

A rough guess would be the end of this week or early next week. Bundling an Android APK to put launcher icons in the res/mipmap directory isn’t the difficult part (as I’ve already got that bit working). The ramifications of dropping Android 2.3.x is the more thought-provoking, time-consuming part.

#19

Ok thank you so much Ajay, I really appreciate your help on this one. If you can keep me updated when it’s implemented that would be great as I need to update them so I don’t miss this opportunity. Thank you again

#20

Hi chris_raz,

The latest daily build should address your issue with getting featured on Google Play. It also drops support for Android 2.3.3 - Android 4.0.2 as I had mentioned as a possibility before.

See the blog post for more details.