Delete this threat if there is already one existing but I didn’t find it with the search function or it didn't help me out.
I tried to upload an update of my app.
I have an issue uploading on play console
My abb version that's currently online is called 113.
Now I want to make an update that's called 114
But I want to include version 113
Here is what the console gives me as error
This APK will not be served to any users because it is completely shadowed by one or more APKs with higher version codes. Remove this APK from your release or review the targeting and version codes of the APKs that you are including in this release.
I saw this errors in boards but the solutions there didn't help me since I work with App Bundles and not APKs
Related
My earlier version of the app was uploaded years ago. Now I wish to upload an updated version. The old one was an APK file and now it has to be an AAB package (developed using Android studio). When I was uploading some new app yesterday I underwent a process of getting errors at package name level and more. I have not 'updated' an app yet and the process is new to me. I wanted to know of there would be issues especially with recent changes?
I am looking for some helpful pointers and links that will guide me. I am kind of new to this
Does the app gets reinstalled when a change is done in dynamic module but not in base.
Example:- 2 users have installed the application and out of which one has just the base apk and the other has base as well as the dynamic module which he has installed after downloading the application.
Now if there is a bug in the dynamic module and we update it and update the app bundle on google play. Does the app will get reinstalled for the user which does not have the dynamic module installed.
I have tried lot's of docs and have not been able to find few questions. Can anyone help me out in this.
When you publish an update to your app, even if limited to one dynamic module, you will need to update the versionCode of your app. Thus, all your users will see an update and get the new version, even those who have only the base module installed.
That being said, users who have auto-update enabled (i.e. not updating manually through the Play Store) will receive only a patch between the old version and the new version, which should thus be very small if none of the files in the base module have changed.
I have a published Google Slides Addon via the G Suite Marketplace SDK. After following the publishing guide everything looked great, until I wanted to bump the version number in the Google Cloud Console via my project's G Suite Market Place SDK Configuration tab.
I entered the number and hit "Save Changes", which put the new version life right away. However, it appears that a couple hours it will always be reset to the same old version (7 in my case). I bumped it again three times and have already tried to update the Chrome Webstore Draft, but it keeps being reset.
Checking the docs, I see no further steps required. I have also not found out yet when the reset occurs, it appears to be "over night" from a European timezone.
EDIT: what may also be relevant, the version in the Google Cloud Console does not automatically update when I publish to the Chrome Webstore. Instead, I manually put the newest version.
This issue should be fixed now.
Also the new publishing flow for GSM, which no longer requires to publish or do changes in the Chrome Web Store, is now live.
I have been facing this problem since yesterday. Although I have published an app in the play store before so I am aware of the policies. But I am trying to upload a new app in play store and it's saying me the following error,
Check these warnings before starting the rollout of this release. Addressing the warnings on this page will ensure your existing users are able to upgrade to the latest version of your app.
In addition, I have tried all the way like as
Removing unused code
Unused libraries and resources
Furthermore, I have tried some of the previously asked questions but none of them saved my problem.
I am adding the details of the apk in the following image,
So it would be great if someone can help me with this problem.
I have resolved this issue.
By going Analyze->Inspect Code
This process will provide you all the unnecessary code or resources.
I've spent the last two days trying to submit my app to the App Store. I get the message below:
ITMS-90338: Non-public API usage - The app references non-public symbols in Frameworks/Flutter.framework/Flutter: _kCTFontOpticalSizeAttribute. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/
Here's what Ive done so far:
a) I've scoured my code for any reference to Font Sizes - I had some that were constants - I changed the constant name to:
k_fontSizeMyName
b) I tried to download the latest flutter sdk version
c) I rebuilt my entire keychain.
Im so desperate right now. im tired.
What do I do?
the internet has no mention of this bug.
I've got the same message several times from the App Store Team a few minutes ago.
I think the problem was the Flutter SDK version...!
I used to use the latest version(Flutter SDK version 1.12.3-pre.26) at first but changed the Flutter SDK version to 'v1.9.1+hotfix.3' and the problem is resolved!!!
I solved the problem with the following instruction below:
Switching Flutter SDK version to 'v1.9.1+hotfix.3' with the command:
flutter version v1.9.1+hotfix.3
Archive and upload again ...
Problem Solved!!!!!! 🤩
This may be a recently-introduced Skia regression.
The code was included in Flutter v1.12.3, so v1.12.2 on the dev channel should work.
Flutter's Bad Build wiki page will be updated when there is a fix for this issue.
Update: This has been resolved in Flutter v1.12.5.
Since there have been a lot of problems with flutter recently(when I tried the fix mentioned in another answer I different error) I though I should include this https://github.com/flutter/flutter/releases
Just type flutter version [version code]