How to check minsdkversion of generated appbundle? - android

i have build appbundle with minsdkversion 21. i give the file to devops for deployment, but he wants to make sure that the appbundle has minsdkversion set to 21. how do i check that? i heard bundletool but how do i use this to check value of minsdkversion from my appbundle file? or maybe with other tool. thanks
in appbundle there's feature called
Extract device spec from a device as a JSON file.
but i'm not sure how to do so

After uploading a bundle to google play console library, you can check the details of the file using App bundle explorer.
Feature that you are talking about "Extract device spec from a device as a JSON file." Creates json file that contains the specification of the currently connected android device, not the specification of the bundle.
An a easiest solution would be to provide also manifest file generated for your bundle alongside with app bundle.
You can get some more details about path of the manifest here:
Gradle Task to get Android App Bundle Manifest

Related

Differentiate crash reporting between debug and production builds

I'm setting up Firebase Crashlytics for my Android app, and I would like the crash reports for the debug version to be separate from all other versions.
There are several copies of the auto-generated values.xml file (that is generated when the google-services plugin processes toe google-services.json file) located in the different retrospective buildType folders. One of the strings contained in the files is:
<string name="google_crash_reporting_api_key" translatable="false">{API-KEY}</string>
The API key is the same for each buildType, so I'm thinking if I can just create a new API key for the debug version, it'll solve the problem but how to do this? Or is there another way (that doesn't involve changing the applicationId as I can't do this)?
I've searched the android docs, looked up other articles and looked through other SO answers but no luck.
Any help welcomed, thank you.
You cannot differentiate the crash as per the build type (debug version).
You have to create a new project in the firebase with same app details (package name).
Get the API key for the project and then replace that key in your manifest file and DONE.
You just have to replace the key when you change your build Type.

Google Play Store Release Issue [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed last year.
The community reviewed whether to reopen this question last year and left it closed:
Original close reason(s) were not resolved
Improve this question
I am trying to release a new version of my Android App.
I can upload the APK file but after I click the "Review" Button I am getting below error.
Review summary
Errors
Resolve these errors before starting the rollout of this release.
You can't rollout this release because it doesn't allow any existing users to upgrade to the newly added APKs.
Please note that this app was developed using CORDOVA
The app version details are as below image. The only difference from the previous and this new version is the Target SDK is changed from 24 to 26
Can someone please give some idea to fix this issue. Thanks for your help
I contacted the Google support and they replied within 24 hours.
The issue is the android:versionCode in the AndroidManifest.xml is lower than my previous release. After I fixed the issue I was able to release my app without any issue.
How I fixed the issue
I changed the android-versionCode to a higher value in <manifest tag in the config.xml file so AndroidManifest.xml has the higher value.
Full reply from Google
Hi,
Thanks for contacting Google Play Developer Support.
You're seeing that error message because your new APK has a lower version code than the previous APK. Newer APKs must always have a higher version code than the previous version, or the Play Store won't know that the new APK is an update. Please change your new APK's version code to be at least 206020.
Regards,
Google Play Developer Support
If your Old APK version is a higher number than your New APK version then you get this error.
It is not the version name that matters, that can actually be any string, it is only the version code which must always be higher than a previous version.
https://developer.android.com/studio/publish/versioning
To fix for Flutter
In pubspec.yaml it is the version line, and the number after the + sign is the one that must be higher than the Old Version Code shown in the Google Play Console screen as the "1 app bundle deactivated".
That would be 50 if this was your version line :
version: 1.0.0+50
I faced same issue, interestingly the versioncode(120001) of new release (12.0.0) was less than the versioncode(1104058) previous release (11.4.5)
I resolved this issue following this link Setting Android version code in Ionic 2
Update both versionCode and versionName.
minSdkVesion 16
targetSdkVesion 26
versionCode 2
versionName 1.1
In your config.xml file's <widget> element, add/increment the android-versionCode attribute by one:
<widget id="com.example.foo" version="1.0.1" android-versionCode="10001" xmlns="http://www.w3.org/ns/widgets" xmlns:cdv="http://cordova.apache.org/ns/1.0">
After that, running a cordova clean android and cordova build android --release gave me an .apk that the Google Play Console accepted.
have you upgraded your versionCode from previous versionCode?
minSdkVesion 16
targetSdkVesion 26
versionCode 1 //you need to upgrade it from previous one
versionName 1.0
If you are Monaca Cloud IDE for building and you are facing this error You cannot make this version available because it does not allow existing users to upgrade to new APKs that have been added.
So here what is the problem, When you try to build APK then it generates a random number,
So make sure your new update version code is greater then this 10505
You can set in Monaca Cloud IDE version code
In the root of your project will be a config.xml file. It contains a widget node that has an attribute of version. 1.17.01 in Example: <widget id="com.myapp.mobile" version="1.17.01" xmlns="http://www.w3.org/ns/widgets" xmlns:cdv="http://cordova.apache.org/ns/1.0">
During a cordova prepare operation, this config.xml file is merged into the manifest file for your platform (e.g. platforms\android\app\src\main\AndroidManifest.xml for Android). The merged manifest file will contain both a version code and version string generated from the version listed in the config.xml. Ex: <manifest android:hardwareAccelerated="true" android:versionCode="11701" android:versionName="1.17.01" package="com.myapp.mobile" xmlns:android="http://schemas.android.com/apk/res/android">
This version code 11701 will be what is listed on the play console.
To automatically set this version greater, you can add to your gradle.properties file a variable setting cdvVersionCodeForceAbiDigit=true which will automatically multiply the version by 10. Note this logic is laid out in the build.gradle file at the root of your platform app folder. There is other logic toggled with the cdvBuildMultipleApks variable to set different values based on product flavor (arm, x86, etc). But I think the recommended approach today is to upload a "bundle" and let Google automatically generate the separate apks for various device configurations.

Previous version debug signature and Update android application

I want to update my application. I changed the version code but when I try to install that application it won't succeed.
This error message is shown:
An existing package by the same name with a conflicting signature is
already installed
How to get previous version debug signature and set it in Android studio? Thanks
There are two parameters that remain in your build.gradle file of your app.
versionCode 1
versionName "1.0"
android:versionCode — An integer value that represents the version of the application code, relative to other versions.
android:versionName — A string value that represents the release version of the application code, as it should be shown to users.
Please refer this documentation to know more about this.
Also you can get the VersionName and VersionCode programatically, in this way --
PackageInfo pInfo = getPackageManager().getPackageInfo(this.getPackageName(), 0);
String versionName = pInfo.versionName;
int versionCode = pInfo.versionCode;
EDITED:
Please refer this documentation to create a debug.keystore file.
Hope this helps!
You just need to ensure that your phone doesn't have the same application already installed whilst you are trying to install the same application's new APK.
So before installing the application, follow the following steps: 1. Go to Settings of your phone and look for an option that lists all applications in your phone and try to find whether the application that you are trying to install is already listed. If it is, then uninstall it from there. 2. Usually uninstalling by following step 1 removes the application from your phone however, if you are using a tablet, sometimes Android still keeps the APK file in the downloaded directory. So come out of settings and find out "All files" folder. Look for your app's APK in "downloaded" folder inside "All files" folder and remove it from there too.
Once you have deleted your app by following the above steps then you can go ahead and install your app. Hopefully you won't see "an existing package by the same name with a conflicting signature is already installed" error message.

Ionic/Cordova - update PACKAGE_NAME in platforms/android.json and platforms/ios.json

Is there a way to do this without deleting and re-installing the platforms directory?
The reason I'm asking is that I'm trying to generate two APKs with different bundle IDs -- one for Development and one for Production. The bundle ID is being read correctly from the config.xml file at the root of the project and updated in the <manifest> tag. However, I have the cordova-push-plugin installed which requires an android:name XML attribute of the form PACKAGE_NAME.permission.C2D_MESSAGE and the bundle ID part of this property is not being updated with the bundle ID found in config.xml.
It looks like the Cordova build process for Android looks at the PACKAGE_NAME property in the platforms/android.json file and uses that to insert permissions into the AndroidManifest.xml file. Is there a way to update this?
edit: I'm using Ionic to build my project and use the ionic state reset command to delete/add the platforms back.

Uploading new APK to the play store getting failed

I have already uploaded the beta version, with version code 1,
Now I m trying to upload the new version in Production mode. I am changing the versionCode from 1 to 2 and versionName from 1.0.0 to 1.0.1
Then I am genereating the signed APK.
But when I m trying to upload the apk, its showing "You need to use a different version code for your APK because you already have one with version code 1."
Please help me to get rid of the prob.
(Do it need to delete the previous signed apk file which i have created at the time of generating signed apk and create again)
You most likely changed your versionCode directly in your Manifest file. But if you use Android Studio, final Manifest file is generated and some parts may be overwritten during manifest merging phase (see blog post on what it is). So highlight your app module, press F4 and bump version code on Flavours tab.

Categories

Resources