We received news from Google, that play store will no longer sho win Huawei.
Huawei has come up with another store called AppGallery . The question is, can same apk upload to Huawei AppGallery and the other still active in Play Store ?
It's possible to upload the same APK file to both Google Play Store and HUAWEI AppGallery. But if your app uses GMS features like Google Sign-In or Firebase Cloud Messaging, it won't work well on the devices that don't have GMS, like Mate 30, P40, and any other new devices. Huawei app reviewers won't set it visible on HUAWEI AppGallery.
It's recommended that you use GMS if a device supports GMS; otherwise, use HMS (Huawei Mobile Services).
Please refer to the following links:
To check whether GMS is available.
HMS Overview
An annoying challenge arises on devices where both Play Store and Huawei AppGallery are installed. I distribute the same app with the same signature, but different mechanisms for purchasing access to premium functionality. If a user has installed the app from Play Store, and has acquired an in-app purchase, unfortunately the AppGallery updates the app also for this user, thus making him loose the purchase.
You can use absolutely the same *.apk (not *.aab).
The only problem (at least for us) is the absence google services =( So if you use pushes or remote config or smt like this it might be a problem.
When it comes to firebase you can check services which require google services here
Related
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
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).
We're building an app that relies on Google Cloud Messaging to recieve data. The app will be installed on several tablets, that each should collect different data from our server. When trying the register our test tablet with our GCM server-side, we get the error "Google Play Services out of date. Requires 3265100 but found 3027105".
We have not attached the device to a Google account, since our understanding was that if you are running 4.0.4 or higher you do not need this. We're running 4.2.2 on an Acer Iconia A1. We really don't want to attach an account to each tablet (could possible be hundreds of them).
How do we update Google Play Services, or do we even need it?
Thanks in advance
If you are using GCM from the google play service library yes you need a google account because google play services gets updated through the play store.
you can however not use google play services and just download the GCM library from the SDK Manager but its not going to get updated anymore so if there are any bugs or anything they wont be fixed. all the new updated will go into the Google Play Services
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
I have built an application that we will be selling to customers through the Google Play store.
We also have individuals in house that will support outside customers, and also use it in house. They need to have the application running on their own device. If I distribute it to them via an .apk file, can they receive updates via Google Play? Or do they have to purchase it through Google Play to receive updates?
Secondary question: Is there a better solution to distributing to internal users?
As curious myself and not having official info on this, I just did a test:
On Google Play I have an App at version 1.3.2
I've installed via ADB the version 1.3.0 on my device.
Opened Google Play > My Apps.
The update to version 1.3.2 was available.
Did the update
All seems to work normally.
So my word on this is: Yes they will receive the update (the app has to have the same signature of course).
Maybe you might just have a look on term of services if this isn't breaking any rules.
On the second question, the "better" solution may wary based on the company infrastructure which we don't know.
If the version on Google Play is identical to the version you distributed, signed with the same signature, and it is available as a free app, then Google Play can be used to update the version distributed outside of Google Play.
I received the following in an email from a member of the Google Play Team:
"The side-loaded apps used by your internal users will not receive updates from Google Play. You will need to provide them with the new APK in order for them to access the new features/functionality. This is working as intended to ensure that only users who have purchased a paid app will receive notifications and updates."
So: Paid for apps cannot be updated via Google Play if they are "side-loaded" (installed outside of Google Play).