I have an Ionic (Angular) application published on Google Play, however it has 2700 compatible devices and I am having problems, because several users are unable to install or update it anymore.
I looked in forums and on the Google Play Console support page, and the only things I found about it is talking about the Minimum SDK Target and settings in the AndroidManifest.xml for functions and mandatory sensors. However, my app does not have any mandatory functions or sensors configured in the AndroidManifest.xml and my Minimum SDK Target is 19 (4.4).
Has anyone been through this and knows how to solve it? Because I have other apps using Ionic as well and React Native that compatible devices reach 17 thousand
Related
What steps do I need to take when I have troubles trying to use an app I created and try to run it on the latest Samsung Tab A 10.1? I tried to start the app, the message displayed is :
This application requires the latest version of ARCore
So I tapped the continue button. I was taken to Google Play. The title says "Google Play Services for AR". Then below that it says:
Your device isn't compatible with this version
Does anyone have a solution, please?
Firstly check whether the device you are using has the ARCore support:
It was indeed an easy experience in terms of building and running the app on the IOS device, iPhone 10. There were no complications in activating the ARkit in the devices since they were built in like the documentation mentioned. It was particularly gruesome in building the AR app on an Android device. As per the documentation the Android devices such as Samsung Galaxy A70S is compatible with ARCore.
Firstly the app simply crashed on installing into the device
As a part of the workaround, I looked for installing, "Google Play Services for AR" on my play store which simply didn't show up
I directly tried to install the app "Google Play Services for AR" through google but it failed with the message, the app is not compatible with my device.
I did a trial and error with installing the "Google Play Services for AR" apk directly from https://www.apkmirror.com/apk/google-inc/arcore/, specifically https://www.apkmirror.com/apk/google-inc/arcore/arcore-1-13-19100710-release/google-play-services-for-ar-1-13-191007106-android-apk-download/ to my Android device to enable ARCore which supported 64-bit processor
The app was however still crashing due to the 403 forbidden IP error on persisting the data
The issue got resolved on adding my public IP to azure rules
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
I need to emulate an Android Application on a tablet. I'm currently running Android Studio 3.0.
The problem is that the application uses Google Service API's FusedLocationProviderClient (Documentation), which, as far as I understand, requires Google Services 11 as minimum. The current SDK tools for Android Studio seems to only update Google Play Services to 10.9.*, and it seems that no pre-configured Tablet emulators come pre-installed with Google Play Store, meaning I can't simply update it through the settings page the same way that you can with the new phone emulators that has play store pre-installed.
I've tried to find ways to manually update Google Play Services to the newest one available, however almost all previously accepted answers on here seems to simply suggest downgrading build.gradle dependencies to whatever the emulator supports. That doesn't work in this case however, as I need features specifically in the newer versions :/
Is there any way that one can manually update Google Play Services on an emulator?
No mention of what you're saying in the link you provided. However, it was announced here that if you're going to use Google Play Services 11.2.0, your app's compileSdkVersion must be at least 26.
I would suggest that you go to Android SDK Manager and update your API package there. It often includes the System Image for emulators.
You can see on this screenshot that I'm able to use the Android emulator with Android 27 installed because I downloaded it first in the SDK Manager.
I'm able to use API 27 because I installed the system image in SDK Manager:
from SDK Manager, API 27 package is downloaded and installed, hence it's available on the emulator:
You can also check this SO post for additional reference.
I recently began learning how to create Google Maps activities in Android app development, and have stumbled onto an issue with Google Play Services. Whenever I set my gradle build dependency to compile 'com.google.android.gms:play-services-maps:11.0.4', which is the most recent version of play-services-maps, the emulator screen gets stuck on the following view upon running my maps app:
I have allowed the app to sit there for over an hour, and nothing has changed or updated. As I've read in other StackOverflow questions, I can get the app to properly function by setting my gradle build dependency to an older version, such as compile 'com.google.android.gms:play-services-maps:9.0.0', but this limits my ability to use newer Android features and APIs in my apps, such as FusedLocationProviderClient.
I am running on Nougat 7.1.1, and have installed the following SDKs in an attempt to solve this Google Play Updating issue:
Android SDK Build-Tools
Android SDK Tools
Google Play APK Expansion Library
Google Play services
Support Repository > Google Repository
I haven't found any StackOverflow threads specific to this "Google Play services are updating" message. What can I do to resolve this issue?
Use API 24 or API 26 Android Emulator system images and you should be good to go. API 25 does not have the latest Google Play Store app pre-installed yet. Note on the screen shot that only these images are "Google Play" versions.
In addition to #Jamal Eason's answer, you may use Nexus 5 and Nexus 5X emulators which have Play Store. Check here. You may also try running on real android device connected via USB that supports google maps and having google play service installed.
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?