how long it will take: change ios app from paid to free - ios

I have an iOS app in appstore, before yesterday I was using Tier2 $1.99. Yesterday I changed it to Tier0 Free.
Almost 24 hours passed, I still see it shows $1.99 in appstore.
Anyone knows how long it will take? Or everytime if I change the price, I should resubmit the app again to make it available?
Thanks a lot.

I didn't do anything but just wait. Now It finally becomes free, for my situation, I think it is less than 36 hours.

From my experience the "button" (i.e. the price that gets shown on the App Store) takes way longer to update than what you app actually costs (i.e. if someone would buy/download your app).
Lot's of information is also stored in the locale catch. Did you just visit the page on your iPad? Restarting the App Store app does not help in all situations. If you can provide us with a link, more people from different regions/locales etc. can have a look at it.

Related

AppStoreConnect Subscription Prices not showing up

I have 3 IAP already approved in AppStore Connect.
I want to edit one, to add a limited into period.
When I tap on the IAP, the "Subscription Prices" section is indefinitely buffering.
I tried Safari, Chrome, incognito, Windows, Safari on iPhone, everything.
I also checked my Agreements and both Free/Paid apps are Active and the default currency is USD.
I submitted a ticket to Apple, but from experience, they don't really help.
Help?
I don't know how much this helps, but I think there's a problem server-side for Apple.
I'm experiencing the same problem and have equally not been able to get any support from Apple around this.
My reasoning here is that 2/3 days ago I couldn't log into my portal as it kept declaring that there was no AppleID attached to that email address. Eventually, as I knew there was, I just left it and hoped it would work itself out. I came back the next day and was able to log into AppStore Connect fine with no issues.
I've seen quite a few comments that Apple have kind of f'ed up their migration over to AppStore Connect, and this fits with the weird login problems I faced. I can definitely replicate your issue and have also reported it to Apple, so I assume that this is one of those things which will magically fix itself in a day or two. (Particularly given user:elbib says it's working for them)
It worked fine for me as of this writing. I’ve used my iPad 8th gen.
Issue got solved after raising it to apple via a support ticket.
It took them 2 weeks.
For who that may face this issue.
The title, prices and details that is used to show the product coming from the In-App Purchase have to come from the store. If it comes null is because you didn't agreed or assigned the accept from Apple Developer Program and paid apps contract on the App Store Connect. So, do that and try again.
Hope it helps others.

iOS App in "Waiting for review" stage, if I release a new build do I have to repeat the process?

My first iOS app is currently at the "Waiting for Review" stage on iTunes Connect.
Now, we are working on some bug fixes and I need to upload a new build, however, I would like to release the app as soon as possible.
My question is after an app is accepted, how long approximately does it take for Apple to review a new build / version for an app ?
Also see http://appreviewtimes.com to get an idea of current waiting times, based on developers self-reporting on Twitter.
Same as always, 7 to 10 days. Except when you ask for an expedited review, but then you should have a really good reason (and a really popular app ;-).
Any time you change your binary you go back to the end of the review line. The time varies depending on how busy the review team is.
The bulk of the time seems to be in "waiting for review." The actual review process seems to be pretty quick, assuming they don't need more info from you to make their decision.
The process of getting fixes to a rejected build seems to be faster than the original review process.
I would suggest planning on an app review taking 10 days. It might take less time, but that seems to be fairly typical.
94% of all iOS app updates are reviewed within 5 business days at the moment.
You can always check https://developer.apple.com/support/app-store to get the latest info on that.

iOS / App Store - Found a bug after submitting for review

We submitted for review. We got approved. I found a bug that's pretty destructive to our leaderboards. We have a low time leaderboard and the time is submitted for each character and then a total. For some reason, the check was disabled and the total is submitted each time. So of course, we are going to get super low numbers (1/7th of the total) on the board. I know we can prune some of the top number and issue an update. That's all I can think to do.
I know we can patch but users aren't obligated to update.
What would you recommend? Should we patch and wait to launch?
So I'm guessing what your question is now, but first off, I have a question: is the app already visible and downloadable for users?
If not, cancel the process, fix the bug and re-upload the app for AppStore-approval.
If it is, then just fix the bug asap and upload the new binary.

Know whether user downloaded iOS app for free or paid?

I am switching my iOS app which is already on the app store from paid to free. I want to know which users have paid for the app, so I can treat them differently (like not showing them additional ads). As far as I know, there's no way to get which version of the app users originally downloaded.
One thing I thought of is this. I can release an update at the same time the app goes free. Everyone who launches the game for the first time who has the update gets marked with a "Free Download" flag. The issue here is what if someone paid for the app, then didn't launch it, then updated their app. That means I will treat them like a free user even though they have paid. Thanks!
There's no way to do this with 100% accuracy without releasing a new app.
If you do use a flag of some sort, save the flag in the keychain and/or iCloud so that it will have a better chance of persisting across uninstall/reinstalls and from device to device (if you use iCloud).
Your best bet though is probably to release a new lite version of the app. It can be a pain to maintain two versions, but at least you know for sure who's paid and who hasn't.
I somewhat accomplish this with a server-side script. On initial app launch, I grab data from my server to determine if this is a paid or free install and then save this info in iCloud. It works relatively well, but it does have a drawback; a small percentage of the time the query fails. If it fails, I just set the app as being paid so as not to screw anyone over. This screws me over a bit, but I take the hit for the convenience of not having to update whenever I want to switch paid/free.
You cannot show updates or advertisement for the customers separately who bought the app for free or by paying money. Whenever you changed your paid app to free, the customers can download the application for free now.

How to Minimize App Store Approval Time

What are some things and techniques I can do to minimize the time it takes for my apps/updates to be approved for the App Store? Do smaller updates generally take less time, and do paid applications take longer than free ones? What about the size of the binary?
In my experience, everything takes exactly the same amount of time. You sit in the queue for 6 days, then they review it for an hour or so (much less for updates), and you're either in, or rejected. If you are rejected, it will take a few more days to work through whatever the issue was.
So the only way to take less time, is don't be rejected. :) Seriously, though, go read the developer agreement and the "do this and we'll reject you" document.
They aren't even looking at your app for that 6 day "cooling off" period, so I can't imagine what you could do to make it go faster. (Although I've heard that there is a mechanism for expedited updates in emergencies; but I have no first-hand experience with that).
I cannot post a comment yet, so I am posting this as an answer to your question based on my experience submitting new apps, as well as updates to existing apps in iTunesConnect.
Unfortunately there really isn't anything you can do to speed up the process, aside from fixing the issues in your app if it gets rejected, and re-submitting asap.
Apple allows you to request an expedited app review.
https://developer.apple.com/contact/app-store/?topic=expedite
Please note: If you're facing extenuating circumstances, you can request the review of your app to be expedited by completing the form below. Expedited reviews are granted on a limited basis and we cannot guarantee that every request will be approved.
I have personally used it twice. Once for a cosmetic issue in an app, which was rejected. Another time for a critical bug fix, which was accepted. I wrote a very detailed explanation of what my application did, what the bug was, why the bug was important to our (Mine and Apple's) customer.
One thing I have found is that free apps versus paid apps sometimes take different amounts of time.
For example I have a paid and free version of the same app. I submitted an updated for both one right after the other. First I submitted the free version, then I submitted the paid version immediately after. For some reason the paid version went into review, and was approved a day later, where as the free version is still waiting for review even know I submitted it first. I suspect that free and paid apps have different 'queues' or 'priorities' over at apple.
You can request an expedited review in emergencies. I used it once and the update was available about one or two days later.
However, they say, the expedited review will only be granted in limited cases. So I wouldn't use it if not absolutely necessary.
You can request the expedited review in iTunes Connect. I think the option was on the detail page for an app which is 'Waiting for Review'. There was also a list, in which cases an expedited review can be granted.
App approval times will vary depending more on what else is going on, and can otherwise vary for no obviously predictable reason. I've seen a small update to a simple app take longer to approve than a new large app with lots of features.
Maximum app review times seem to be around the days that lots of other developers are submitting apps, near some major holidays, shopping seasons, or when Apple has just released some OS update, app service or new device. Shorter wait times can sometimes be had by avoiding these longer review time periods. There are services that track the number of new apps introduced per week. Look for the nulls.
Staying well away from any hint of violating any of Apple's App store rules or guidelines, or anything else that can be seen as controversial, also helps not getting hit by a long (additional time required) review time. Other factors seem to make less difference.
Take a look Apple review support
Once you've submitted your app for review, you can view its status in the My Apps section of iTunes Connect or on the iTunes Connect App for iPhone and iPad. Review times may vary by app. On average, 50% of apps are reviewed in 24 hours and over 90% are reviewed in 48 hours. If your submission is incomplete, review times may be further delayed or your app may be rejected. Once your app has been reviewed, its status will be updated and you will be notified.
I tried to use the expedited review for an app for a skistation, so it would be available before the winter season started and it was declined.
You need obviously a very good reason like a big security issue etc to get a expedited review.
Step 1:
Related to your project, note what is the third party libraries are involved and make a note what makes it rejected in apple store.
Step 2:
Make your code stable and keeping in mind about rejection points which you cant keep
(i mean like really stable no warnings, no chance with wrong icons, no chance with mistakes).
Step 3:
Finally, then decide to send for review
That will at-least speed up your process. once you get rejected then its a bad, you have to really wait longer. (from experience saying)

Resources