Remove Version from Review in Google Play Console - google-play-console

I found some bugs in my code and need to submit a new version.
How do I remove or cancel the old version that is in review in Google Play Console?
I am hoping to not waste Google's time to review something that is already outdated.

[Screenshot of the Issue]
I got the same issue you got when uploading two releases at the same time which both of them were in review mode, the simple answer is "You don't have to worry, the latest version uploaded will get published on Google Play"

You cannot remove versions of your app that you have published on the Google Play console. You can only halt releases for ones that have only been partially rolled out.
Instead, just submit the new version on the track and it will override the version that is in review. As it has a higher version code so it will replace the old version after it has been reviewed and users will download the new version.

Related

Deactivate a Google Play app that is currently in review seems impossible?

My app is in review, received a note stating non-compliant SDK version and I need to deactivate the "wrong" release and upload a new version without the SDK. I haven't found any option to remove it. Is it possible to deactivate releases that are in review? Can you confirm if it's enough to upload new release or am I missing something?

Versioning Google play

I have been working to build an app and I deployed it only for testers(internal testers).
yesterday I have done building the app and I want to publish it,
unfortunately, the version code is wrong the version code now is (3033 (2.8.0))
and I want to reset it can you guide me on how can I start from version
1.0.0
Thanks in advance
I contact support they don't allow me to reset the version code until the date of my answer
they reply:
I checked into it and the Play Console doesnโ€™t currently support resetting the version codes.

ITMS-90909: Deprecated API Usage with iOS in Xamarin Forms app

Can anyone suggest what to do about this message that I get when submitting my Xamarin Forms app to the iOS store?
Comment on possible duplicates
This question was asked before and not answered; I don't think an answered duplicate exists.
This is a known issue which was recently closed by the Xamarin team issue can be found here https://github.com/xamarin/Xamarin.Forms/issues/7323
And the fix is and i qoute
All the bits are in place, solution time! TL;DR: all is described in this piece of documentation here.
Make sure you are using the latest Visual Studio (for Mac) on the stable channel, that should put you on the right path. At the moment, you will need to use the Xamarin.Forms 4.5-pre1 preview release. I understand that this might not be an option for all of you, but rest assured, the stable package will be out well before the deadline. Stable 4.5 is planned mid to end of February.
Lastly, put the --optimize=experimental-xforms-product-type flag into your iOS additional mtouch arguments setting and you should get rid of the deprecation warning by Apple. If you don't have any references of your own to UIWebView of course ๐Ÿ™‚
I would like to ask you to try this at your earliest convenience. Maybe not to release an actual new version to the store based on the Forms preview package, but at least upload a build to verify that this solution works correctly. Whenever you do, you can just update to the 4.5 stable package and release a new version with confidence.
If you do run into anything with this solution, please feel free to reach out to me directly (gerald.versluis [a with a long tail] microsoft.com) or open a new issue on the repository. Of course positive feedback is always appreciated as well ๐Ÿ˜‰

Version of internally published Addon keeps getting reset

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.

Is there a way to retrieve information about new app builds from TestFlight?

I am using TestFlight to distribute test versions of my app to a private group of people. As I am making a lot of updates these days I wonder if some of my testers will get sick of the large amount of update emails they receive.
So I thought it would be a better approach to let the app check for updates when started and than showing a small notification that there is a new version out and to only notify the testers about important updates by mail.
So my question is: Is there a way to retrieve information about new builds by RSS or some other channel?
Thanks.
The TestFlight iOS SDK already supports this for beta versions if you have the SDK integrated into your app:
Beta In App Updates
If a user is using a beta version of your app, you are setting the
UDID, a new beta version is available, and that user has permission to
install it; an in app popup will ask them if they would like to
install the update. If they tap "Install", the new version is
installed from inside the app.
NB: For this to work, you must increment your build version before
uploading. Otherwise the new and old builds will have the same version
number and we won't know if the user needs to update or is already
using the new version.
To turn this off set this option before calling takeOff:
[TestFlight setOptions:#{ TFOptionDisableInAppUpdates : #YES }];

Resources