Device compatibility issue when i download the app - android

Before publishing my app on Google play store, i testing my app on Micromax A63(Android 4.2) it works accurate but after Publishing when i tried to download my app from Google play store it show "device is not compatible "...whats the reason..I'm confused

The possible errors are:
You had another phone on this account (just check it and make login google play with the correct account)
You haven't set correctly something when uploading the apk. Go to the App tab on Google developer console and check if you made available your app for your:
Phone Device
County
Carrier (the mobile network you are paying for your phone service).

Related

How can I prevent Google Play from installing apps on my Android device when asked to do so from a browser?

I have an Android phone which, in its stock ROM, comes with Google Play and (presumably) Google Play Services.
If I log into the Google account associated with the device on a PC, I can browse the Google Play store in a browser, and ask for apps to be remotely installed on the device. There's a permission prompt on the website, but the app gets downloaded and installed onto the device at the direction of Google, with no interaction or confirmation from the actual device.
How can I prevent this from happening? Do I have to root the device and remove Google Play and/or Google Play Services to prevent just any old apps from being "pushed" from Google's end and accepted by my device?
I need the device itself to remain trustworthy even if the Google account it is connected to is compromised.
This install is done by the Google Play app, so you would only have to remove this. However, this will probably do more to hurt the trustiworthiness of your device than help it. If you do this you will no longer get updates (including critical security updates) to Google Play Services.
A better option would be to add 2 factor authentication to the given Google account, and then you have the whole account protected by the device.

Can't sign into to Google account on WearOS emulator

I am developing an app for WearOS using Google Fit. In order to use Google Fit, you need to be connected to an Android phone. So, I connected a WearOS emulator on Android Studio to my Android phone (Samsung Galaxy S9+). I am having trouble getting Google Fit code to run. In the Log console on Studio, it tells me that Google Play services is out of date. So, I have been trying to update Google Play services and it is much harder than I thought. I am trying to sign into Google through the emulator itself, that way I can just update Google Play through the Play store (the other methods didn't work). But I can't get my Google account signed in. When I go to sign in on the emulator, it asks me to look at my phone and select an account to be copied over to the emulator. I select my account and it tries to copy the files over. After a few seconds, it fails and all it says is "We couldn't copy your accounts. Make sure your phone has a network connection and is connected to your watch." My phone has a network connection and it is connected to the watch. Has anyone else had this problem? I have tried the other methods that people suggest in order to update Google Play services and none of them work. Thank you.

Update Android app in COSU device

I am working of app support COSU app android. The app is working fine for me but I am not understand how user will update our app, because COSU app user can't access any other application even google play store. So now the question is that how user will update our application without google play access.
I have one solutin download app from our server, but in this case user will lose save data like the data we are storing in SharedPreference. Please guide me if you have any other solution for that. Thank in advence
According to Google's docs on COSU (Google Play app management), it is possible to "install, update, and uninstall apps using the Play EMM API". Under "Google-hosted private app management" it describes the ability to host private apps through Play that your users can install/update:
Simplifies the Google-hosted private app publishing and update
workflows available to all admins through managed Google Play, by
enabling admins to update Google-hosted private apps through the EMM console instead of through the Google Play console.
Enterprise admin can upload new versions of apps that are already published privately to the enterprise using the Google Play Developer Publishing API.
If you don't want to use Play for this functionality you can read the "Self-hosted private app management" section.
You can also look at "Managed Google Play" to publish private apps for your users: https://support.google.com/googleplay/work/topic/6145152
After you register for a Google Play Developer account and set up the correct administrator privileges to upload and publish the app to managed Google Play, you can use the Enterprise Mobility Management (EMM) console to distribute the app to users.
Going the EMM route will let you update apps with the same functionality as regular Google Play apps where updates don't cause users to lose data. Unfortunately Google's documentation isn't detailed or centralized for this feature. Going through Google will also require that all of your devices are signed in to Google account in order to install apps or receive updates that you deploy though the EMM console.
Another option is to use a mobile device management (MDM) solution. If you have Samsung devices you can look into Samsung Knox which has a much simpler method for distributing your app: https://www.samsungknox.com/en/article/manage-apps
Another MDM option for single use apps is Mason (https://bymason.com/). Mason lets you upload your app, select any or all of your devices, and then deploy your APK to your users. When updating your app, all you have to do is increment your app version and the update functionality will be the same as a regular Google Play update. Your users also don't have to be signed in to a Google account.
If this sounds useful to you feel free to reach out to me trevor # bymason.com
DISCLAIMER: I work at Mason

test Google Play Game Service Multiplayer with one account

I'm making a Multiplayer game using Google Play Game Service for connection. I'm at the point where I need to test connection between devices and it seem like I need a different account for each device.
I tried create new Google Account, but Google force me to verify account with a phone number that had not been used to verify another account. I only have one phone number.
The question is: How developer test their apps in this situation ? Do they have multiple phone number just for verify account ? (need to afford multiple phone bills just to keep them active ?)
Some developer are using Android Emulator. Just download the emulator system image that includes the Google Play Services, under Android 4.2.2, from the SDK Manager. However, it is highly recommended to run your game on your physical test device.
Must verify that you have set up the test account that you are using to log in to the app. You don't need to have multiple account, just export an APK and sign it with the same 'certificate' that you used to set up the project in Google Play Developer Console. Then, install the signed APK on the physical test device by using the adb tool.
For more information, use this as your reference: https://developers.google.com/games/services/android/quickstart#top_of_page

Is it possible to get a GCM registration Id assigned to an Android device that isn't activated?

I am trying to make an app that would require two devices to communicate and am using two Android devices, one activated with Verizon, while the other is not activated. I am running code that gets a GCM registration id which successfully retrieves one on the activated device but does not do so on the other device. I assumed that an internet connection would be enough to qualify a device to receive a GCM registration id but it appears not to be the case. Can anyone please clarify this for me (and/or perhaps point me to something I might have failed to find online)?
Thanks!
GCM is a Google Play service; it requires that both the Google Play APK and the Google Play services APK are installed on the device:
http://developer.android.com/google/play-services/setup.html#ensure
It's also helpful to add a quick check in your code to verify that the user has Google Play Services installed. Check out Google's explanation of it (with sample code):
http://developer.android.com/google/gcm/client.html#sample-play
It requires devices running Android 2.2 or higher that also have the Google Play Store application installed, or or an emulator running Android 2.2 with Google APIs. However, you are not limited to deploying your Android applications through Google Play Store.
It uses an existing connection for Google services. For pre-3.0 devices, this requires users to set up their Google account on their mobile devices. A Google account is not a requirement on devices running Android 4.0.4 or higher.
Source: http://developer.android.com/google/gcm/gcm.html

Categories

Resources