I am planning to release my first iOS app in AppStore today. I have two questions
1) The app is already approved so if I release it then how soon will it be available in store for user to download & install?
2) if there are some issues with the app then I need to rollback. Is it easy to rollback and how soon app disappear from the store?
Once apps are released to the store it can take up to 48hrs for them to be visible. (In some rare instances even longer, especially if it is the first app of the account)
There's no easy way to rollback an app. For that you should do extensive on device testing via TestFlight or similar. You can remove an app from sale, i.e. it is no longer possible to download it. You can then submit an app update and request an expedited review to get the fix faster to your customers and the app back online.
Related
I was wondering if you can disable or delete (already installed) app from tester's devices in TestFlight, since expiring the build or removing testers will leave the app installed until it automatically expires after 90 days testing period.
The problem is that I submitted the app for review in order to enable external testing, and during this period I would want to disable the app in internal tester's devices. I want to do this because I'm using Firebase for back-end with the free plan, which has a limit for transactions. So, I don't want the testers to use the resources while the app is being reviewed and tested by Apple.
Of course, I could notify these users to not use the app in the meantime, but I'm curious to know if this is possible, because it would be helpful in some other cases too.
NOTE: I know this question has been answered, but it's from 2012, and I want to know if anything changed.
I recently started using RevenueCat for all of my InApp purchases; today my app was approved in the App Store so, I went ahead and downloaded it to try the new version directly from the App Store and I noticed that the In-App purchases are not loading. What is funny is that if I connect my phone to my computer and compile the app directly from Xcode it does show the In-App purchases.
So my question is, is there any setting in RevenueCat that we need to turn on when the app goes into production?
If such of setting does not exist, what would be a good way to troubleshoot the issue to determine where the problem is, if it's RevenueCat, the App Store or my code?
FYI - When I install the app directly from Xcode I can make purchases with a send-box account and everything functions as it should.
There aren't any RevenueCat settings to update when your app goes live. This sounds like a propagation issues with the App Store if these are new products - sometimes they can take ~24hrs to be available in production to all users after being approved.
Unfortunately, doing nothing and waiting is probably the answer here. In the future if you can not show new products to users until >24hrs after they're approved it should prevent this from happening again.
My app has been approved but is awaiting developer release as I want to release it manually. Before releasing, it however, I want to test using test flight
When I try to send the approved build to my testers, Apple asks for a login id and then gives me a dialog to Submit For Review. Is this just Apple being clumsy with their language or do they actually want to review it again before testing even though it's been approved?
Anyone have any experience with this?
Here is pic of dialog box
My experience is that the Store and TestFlight are two different worlds with two different approval processes — but that the former affects the latter in a peculiar way.
The way the issue you raise has arisen in particular for me is that you release, say, version 1.1 build 26 on the Store, it is ready for sale, and then you proceed with development and upload version 1.1 build 27 to TestFlight. Even though 1.1(26) is being sold already, and even if 1.1(26) was already released on TestFlight, 1.1(27) requires a new approval! In other words, it appears that an App Store release resets the approval clock, as it were, on TestFlight.
That is almost exactly your situation. The approval on the App Store apparently means that your next TestFlight upload needs a new approval. So yes, you will have to wait while it is approved. This usually takes just a couple of days.
Instead of using TestFlight, there is even more simpler method to test the Apple approved build (Pending Developer Release state) before releasing to Store. It is Promo code testing.
You can generate nearly 100 promo codes, if i am not wrong. These promo codes can be shared to the developers so that they can actually test the store build without releasing it to app store.
You can find many articles about Promo codes. I have shared one here.
I had uploaded my App successfully to TestFlight, 5 days ago(with new version and new build number). Which is already uploaded on App Store (But with its Older version).
Now i have added external user to test it and select the build to test and then click on save button, then it is showing "Waiting for beta App Review".
I don't know why user is not added directly rather app goes into "Waiting for beta App Review", and how much time it will take to approve?
Please help me if anyone has faces such issue.
Once you add another user (ie not your apple id), then it must be reviewed by Apple first to ensure the app is safe (contains no malicious intent) for the users testing it.
Normally takes a couple of days for apple to turn around and approve.
There is a distinction between iTunes Connect users and people in TestFlight.
When you upload build, and it shows up, then it becomes visible to your users. But there is an approval process (presumably automated) before TestFlight users see the announcement (assuming it is approved).
I am trying to release an invite-only iOS App. I don't particularly want this app on the App Store, and using TestFlight causes a lot of problems (having to constantly update binaries, limited users... Apple IDs).
At the same time I'd rather not have to resort to a third party distribution to get this kind of an alert.
Is it possible to release a secret invite-only App on the App Store?
Consider enrolling for an Apple Developer Enterprise Program
This will cost more but then you can distribute using your server . You can use MDM also no need to upload or use test flight.
I am not sure the last time you used Test Flight, but it has changed a lot in the last year. There can still be headaches with it, but since it was bought by Apple you now distribute your App through iTunes Connect which is the same way you would do it for releasing in the App store. You have a number of beta testers (up to 1000) that all you need is their email address. You can also have internal testers (up to 25 I think) which will get every build you upload automatically (however they do have some access to the information about your app through their iTunes accounts).
So in summary it takes the same amount of work and the same process to have beta testers that it does to release it through the App Store except that you don't have to wait the 5+ days for the App review. Do note that the beta version will expire after 30 days at which point you just need to upload a new one.
You cannot release a secret App on the App Store, as it violated Apple's App Store Review Guidelines
2.22 Apps that arbitrarily restrict which users may use the App, such as by location or carrier, may be rejected