Google Play has changed APK menu to Version Manager, or something like that (my Store is in spanish).
Now i've read how to upload multiple APKs to production, but what if I want to upload multiple APK (x86 and armv7) for BETA testing? I'm using ionic with Crosswalk Project and it generates 2 apks.
In previous version you had to enable advanced mode, but I don't see advanced mode in this Version Manager.
Can anyone point me in the right direction please?
Thank you for your time!
Related
I have one android app (e.g MyApp) in the Google Play Store, and at the moment the package is from the RC build in our pipeline, but we also want to publish package from CI build for testers. Is it better to create a new app called MyAppTest in play store which receives the package from CI build? Or is it better to just upload the package from CI build to "MyApp" under internal testing track? In the package from RC build, the version is like 1.0.0-RC1, and the package from CI build the version is like 1.1.0.1.
What is the best practice for this problem?
You should keep all into a single project! And use the different levels of testing of google play (alpha, closed beta, open beta).
Usually there are some levels of testing:
Internal testing (Release Candidates)
Open Beta for selected users
You should try to scale the same version from internal, to open beta to production. Most versions will be transitory, and won't reach production at all.
But you should keep the semantic versions all the way, some devs like to add -RC or -beta after the version to name, to tag as "in testing" version.
I have this app released on play store that I want to make available on my website. I tried downloading the signed apk via the Google play console and use that, but some users in China have issues installing it.
They get a message like this while installing: "Your device does not support Google Play Services and cannot install "
I have a few Google sdk bits referenced in my project (signin, safetyNet, ads) which I would assume I need to delete before building for this apk version, since target devices don't have gms..
What about signing? Can I simply build without the said code and distribute it? (Generate release apk in android studio) Or do I need to upload to play console and download the one signed from google?
Please let me know if you have any clues on this, been banging my head around for a few days already.
Cheers :)
This might help you taking your decision:
If you have Play App Signing enabled, the APK generated through your studio and the APK generated through Play Console will have different signatures.
Otherwise, both approaches will have the same signatures.
So, it depends whether you care about your APK on website having the same signature as Play Store. If you don't care about having same signature, you can go ahead with creating APK from Android Studio itself and publish to your website.
If your app utilizes Google Play Services, as is informed by the error message, then it WILL not run on the device unless Google Play Services and everything that it depends on is installed on the device. The only work around is to convert your app features that uses Google Play Services to its alternative that's supported in China.
I've dealt with similar issue on Huawei smartphones, my approach was to 'develop another app' using Huawei SDK, check out https://developer.huawei.com/consumer/en/ for its complete reference
I want to publish my Xamarin.Forms App to Google Play Store. But when I upload the APK it gives me warning and disables roll-out option. It says we need to use Android App Bundle (.aab) format so that APK can be optimized for size and resources.
Currently, Visual Studio 2019 Archive option does not support the Android App Bundle. I have taken latest update of Visual Studio 2019 but still above format is not supported.
I googled and found some link to do this from the command prompt by modifying some settings in the Project file. But the build returns errors after couple of minutes with exit code 1.
This is frustrating as I can't publish it to Google Play Store. I have already published the iOS version of App.
Any help here will be very much appreciated.
Me and my team are currently releasing to Google Play with no problems our app as APK.
The App Boundle is a nice way to release smaller applications by delivering just what the device that downloads your application needs. The Xamarin Show published recently a video on this topic, that could be of interest for you:
https://www.youtube.com/watch?v=_IOZ0SUKZq4
Through the following images i show how we upload/publish our APK:
First, in the image below you see that APKs are still supported:
APK uploads correctly:
Then we are able to save and review the APK:
APK is uploaded with warning:
The warning states:
For now we just ignore the warning and go on to roll out:
In case that after following those steps your Start Rollout option is not yet enabled, it might be the case that you still have some other Listing Sections for your Application. After you introduce all the information required by Google, the Start Rollout option must be available.
With Visual Studio 2019 I created a archive folder that contains 3 signed-apk files for the app I plan on publishing to the google store.
In the signed-apks folder the file names are:
com.blah1.app.apk
com.blah1.app-arm64-v8a.apk
com.blah1.app-armeabi-v7a.apk
Which one(s) should I use? The Google Play Console seems to let me add all 3. Any other information you also provide would be great as well.
Thanks.
You should upload all three. you are generating an apk per ABI
From the documentation:
Multiple APK support is a feature on Google Play that allows you to
publish different APKs for your application that are each targeted to
different device configurations. Each APK is a complete and
independent version of your application, but they share the same
application listing on Google Play and must share the same package
name and be signed with the same release key. This feature is useful
for cases in which your application cannot reach all desired devices
with a single APK.
I am a newbie to Android programming and i started putting together an application using Google Maps using Eclipse with KitKat SDK. I developed a simple app to display Google Maps in the Emulator by installing com.android.vending(4.6.16) and com.google.android.gms(4.3.25) apks. I downloaded these APKs from different sites(not sure how authentic they are).
I am making use of the command aapt dump badging to determine the version.
The map opens but i was repeatedly getting a message that "Unfortunately Play Services has stopped"
Objective is to ensure that I am using the right set of APKs with the emulator
The trouble that i am facing is there seems to be no clear directives on where i can find the authentic version of these APKs. I tried Google Play and when i give a search for com.google.android.gms, it yields a result of applications. I was expecting a URL to download the recent version of the APK. Correct me if i am wrong
1. How to download just the recent version of APKs from Google Play ? Am i looking at the correct site
2. Second is there any authorized site from where i can download these APKs?
I was looking for a listing of the APKs with the version number against it. So that i can download the version that i need. I am not sure of the dependencies of the APKs on the Android platform.
3. Finally is there any dependency between com.google.android.gms.apk and the com.android.vending.apk on the basis of the version or the SDK platform used?
Thanks
Govindarajan
I have a suggestion, Try to use Genymotions for testing maps/places app. it is faster than emulator and you can build and check maps application.
www.genymotion.com/
LINK