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 }];
Related
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?
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
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.
I have one app that is in market on Alpha mode (because the app is only for a resctricted group of persons).
And now I need to have another twin app (also in Alpha), considered "Dev" so, when I'm going to do updates first the them will be available on that version and only after that they will be apllied to that Production.
My workarround to have this version was to create a new app on the store, then create a new app (with different package name) and publish there (I don't know if this is the best way to handle this).
Problems:
I can't have both apps installed simultaneous, when I try to install the the second app store just gives me a error. Same happens when I try to install from xamarin.
I've been searching and everyone says that I need to have a different package name, but I already had it.
Someone knows a solution for this problem? Or a different way to do
I'm new to this, so please bear with me. I have an app live on the App store, developed in Xamarin. The current version is 1.0.3 and I want to keep it that way. I want to send a new build (i.e build 85) via Application loader with the same version number (1.0.3).
I want to know:
Will it become live as soon as I send it or will I have the option to keep the previous build (i.e 84) live and not this one (i.e 85)? I want the previous build (84) to be live.
Can I upload a build that I got from Ad-Hoc > iPhone => myApp.ipa / currently I'm doing this only or should I generate an ipa from a different configuration like "Release" or "App Store"?
If you try uploading your build with the same version number as your current live build, Application Loader will give you an error message saying you need to create a new app version profile in iTunes Connect.
You should be able to upload an Ad-Hoc build to ITC. However, you may need to tweak your entitlements to enable beta testing via TestFlight:
App "does not contain the correct beta entitlement"