I have set the defaultMinSdkVersion=19 //Integer - Minimum requirement is Android 4.4 in build.graddle.
And I have submitted the app to playstore. In playstore console it shows API levels 19+
But still people can download the app in to devices running os version 4.3. This causes issue, because my app does not work properly on 4.3 and lower versions.
Does anyone has face this problem?
App is build using ionic
Related
In August 1, Google Play requires new apps to target at least Android 8.0 (API level 26). But in appgyver, I notice the latest available version is 4.5.3. Is there any way to upgrade it? Thanks!
I having the same issue, which is the maximum API level which appgyver supports is 21 only. GooglePlay required at least API Level 26 on August 2018 onward.
AppGyver just officially answered this question here.
TL;TR AppGyver is using Crosswalk, an Intel product, to build Android apps, and Intel has shut down Crosswalk over a year ago, now it is not possible for AppGyver to update their Build Service without rewriting the entier Android part, which would cost them too much, Supersonic and Steroids being depreciated, Android is officially abandonned by AppGyver, the Build Service will stay as is for apps that are internally distributed but won't allow to build apps destinated for Play Store.
Edit: I found a solution that allow me to get the app accepted on the Play Store, but app will crash on Android 8.
I then tested to install my app from the Play Store on a Android 6 with success but as we could expect it crashes on Android 8, the edited Target SDK number dupes the Play Store so it lets the APK in, but in the end it hasn't been built with Android 8 capabilities, so it won't work on that version.
All I had to do was to import my APK in APK Icon Editor, go in the Properties tab, change the Target SDK value to 26 (be sure to keep a lower value in the Minimum SDK field as it's the one telling what Android version can actually instal your app, if it's high then older phones won't have access to your app), and click on Pack APK to generate a new signed APK that is accepted by the Play Store!
Its as easy as this:
I then tested to install my app from the Play Store on a Android 6 with success but as we could expect it crashes on Android 8, the edited Target SDK number dupes the Play Store so it lets the APK in, but in the end it hasn't been built with Android 8 capabilities, so it won't work on that version.
Edit: it seems like it also crashes on Android 7 :(
Appgyver is constantly working on their platform and bringing latest updates. hopefully soon this issue will be resolved as well.. try contacting their support
My game is now in beta tests. I want it to be available for devices with Android 4.4 and up. I've set the minimum android API to 19, but on my app Google Play site the requirement stays 4.0+.
Does minimum API requirement work for alpha/beta apps?
It's a Crosswalk app, APK made with IntelXDK. I've also checked XML config files, and they all seem to be ok (android-minSdkVersion is set to 19) so it looks like Google bug. Is it a known issue?
I have recently included android wear support in my app but when I went to publish it today I was made aware my earlier version would be archived. My earlier version was targeting api 16 to include as many devices as possible.
I was hoping if a user doesn't have the latest devices capable of running my updated android wear version then they would get the earlier version I have published.
What is the correct procedure to enable this to happen please?
Regards
It is possible to keep your app supporting API 16 while adding Android Wear support. The Google Play Services library runs on many older devices, and it will do the right thing to ensure that your code will not crash. Since an old Gingerbread phone cannot support Android Wear, you will just get an error code when you try to make use of Wear functionality, and you can just handle it gracefully with whatever way is appropriate for your application.
I published an app to Google Play, but some of my users are unable to find it using their device.
The min apk for the app is 11 (Android 3.0).
When someone uses for example a Samsung Galaxy SII with Android 4.0, the app can't be found because the initial release of the SII was with Android 2.3. With a SIII it's no problem.
In the developer console, the console automatically checks to see which devices are compatible when uploading the apk. As developer, I can disable devices for download, but not enable devices.
Does Google Play check the current version on the device or does it uses the versio, of initial release?
How can I reach as many as possible devices? When I lower my min APK in the manifest, I get compilation errors.
Thanks in advance
That's a really good question. Lowering your minSdkVersion or publishing multiple APKs is the best solution to reach many devices, your problem with this approach is that probably you are using some API features that aren't present in older APIs so that's why you're having compilation problems.
http://developer.android.com/google/play/filters.html#manifest-filters says:
Example:
The manifest includes uses-sdk android:minSdkVersion="3", and the
app uses APIs that were introduced in API Level 3. A user is searching
for apps on a device that has API Level 2. Result: Google Play will
not show the app to the user.
So I assume google will filter based on the current API version.
Can you post your app link?
I downloaded sample in-app-billing application and I tried to run that application on devices
its working fine for devices with android OS version 2.2.
but I am getting problem with devices having OS version 2.1.
Actually I am able to connect to market server and I am receiving response saying that request sent to server ,but I am not getting response about purchase state (ie whether the purchase is success or not).
we are getting this problem with android OS 2.1 devices,for OS 2.2 its working fine.(i tested in devices with OS 2.1 and 2.2 only)
From developer pages: http://developer.android.com/guide/google/play/billing/billing_subscriptions.html
System requirements for subscriptions
In-app purchases of subscriptions are supported only on devices that meet these minimum requirements:
Must run Android 2.2 or higher
Google Play Store app, version 3.5 or higher, must be installed
Google Play 3.5 and later versions include support for the In-app Billing v2 API or higher, which is needed to support handling of subscription products.