itunesconnect availability date selection issue:
itunesconnect availability date always resetting to current date. In
some cases, its not at all showing the availability date.
We are forced to set the price tier in order to bring the
availability date. Even after doing so, its not allowing me to set a
future availability date.
itunesconnect upgraded its GUI, and these issues are started
happening after the recent updates. Anyone know what needs to be done
to set a future date?
Related
Have been using PHP-PKPass successfully for a few years creating membership passes that expire 1 year in the future.
Just with the release of IOS 15.5 the certificate passes seem to be expiring 24 hours after they are installed to the Apple device, on older IOS it is still fine...
No useful suggestions on Apple forum at present (e.g. https://developer.apple.com/forums/thread/708761), has anyone got a workaround or is it just an IOS bug that has been introduced...?
This seems to be a bug, because in the archive of the documentation it says that the expirationDate field is the one that determines whether the pass shows as expired or not in the wallet :
A pass is marked as expired if the current date is after the pass’s expiration date, or if the pass has been explicitly marked as voided.
While relevantDate description says :
Recommended for event tickets and boarding passes; otherwise optional. Date and time when the pass becomes relevant. For example, the start time of a movie.
The value must be a complete date with hours and minutes, and may optionally include seconds.
However, in iOS 15 is seems that the pass is actually expired when we have a relevantDate set in the past.
I have been reading a lot about auto-renewable subscriptions but so far I could not get a satisfactory answer to my questions.
Imagine a user subscribed to my app for 1 month and the very first view of the app has some content that only visible with subscription. Now imagine it's the first day of second's month subscription (after auto-renewed). If I don't query the expiry date from apple server, user can't see subscription items, because the expiry date of first month already passed and we need to get the new expiry date.
My questions are:
1- Is there a way to get the end date of the subscription offline and without disturbing the user (with password prompt etc.)? How user will get subscription content if it is the first day of auto-renewed subscription (second month and so on) and if user don't have internet? Will he see locked content if he has no internet? If so this is sounds weird to me.
2- If it is not possible to get expiry date of auto-renewed subscription offline, what is the best approach to get expiry date of auto-renewed subscription without asking or prompting something to user? Because we want to show the very first page of the app with subscription content smoothly. What comes to my mind is to make user wait during launching and check expiry date from server.
I am sure many developers are still concerned with those issues.
It's been a long time since the last time that I integrated an auto renewable subscription and it harder than I expected, but I can give you some general hints and some more specific for your question.
Starting from your question.
Not exactly, you can get the last updated receipt by asking getting the receipt from the receiptURL, here is where I've found a really gray area. I never had a chance to understand exactly when a receipt is updated automatically, probably this happen right after Apple charged you (of course this update needs a connection). This doesn't seems to happen when you have restored a purchase on another device.
Yes there are, when you have a chance to validate the receipt you can store the expire date somewhere (maybe in a secure way) and only before one or two days after that day try to validate it again. If you want you can apply also a grace period after.
Other tips:
you MUST create a way to restore the purchase or your app will be rejected
on sandbox at the first launch the receipt will not exist, but in production an app will always have a receipt, maybe without subscription info, but there is. Thus if you want to simulate some use case in sandbox environment is better if you restore the purchase right after the launch of the application.
restore purchase always requires username and pwd and refresh receipt seems too
Maybe some of this info are a little bit outdated, I made the integration with iOS7 and never had a chance to update it.
i was uploading my apps on itunes connect. For in app purchase i am using mass import template for uploading IAP but now i am getting error
ERROR ITMS-5103: "Default product interval not supplied (in-app purchase with product_id='com.mclegacy.megacasino3.combo3'). For a new in-app-purchase, a default product interval must be supplied: no start date (or start date of today or earlier) and no end date." at Software/Soft
This error is mainly due to the mismatch of time provided in Price effective date
with US Time. So This error can be solved by waiting till US time and "Price Effective
date" mathches.
So Either Provide US date/time as Price Effective date or wait for given
Price Effective date reaches US date.
I kept getting this error no matter what dates I entered. Finally read the docs and tried:
Price Tier Effective Date: Now
Price Tier End Date: None
And all my products uploaded successfully.
For a brand new iOS app, with the following pre-conditions:
Availability Date is far in the future
App is approved and Ready For Sale
How can one immediately (not even wait for midnight) release the app on-demand without waiting for a future availability date?
I found a few articles relating to this.
Use iTunes Connect to set a date when the app is available on the
store. For example, you can choose a date that immediately releases
the app to the store after it’s approved, or you can set a later date.
Using a later availability date allows you to arrange other marketing
activities around the launch of your app.
https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/UsingiTunesConnect/UsingiTunesConnect.html
You can change your app’s availability at any time, removing it from
sale or replacing it in the store. If you move your app’s availability
to a time in the future, your app is removed from the store until the
new date. It may take up to 24 hours to refresh your app’s
availability in stores in all territories.
Before an app is approved, you may want to set the app’s availability
date to an arbitrary date in the future. When the app is approved by
Apple, you can decide more precisely when you want the app to appear
on the store.
https://developer.apple.com/library/ios/documentation/LanguagesUtilities/Conceptual/iTunesConnect_Guide/Chapters/ChangingAppStatus.html
To me the first statement suggests that if you set the release date in the past it will "immediately" release the app. - I found a similar post also stating the same thing: https://stackoverflow.com/a/7352542/2982796
What I have found it still takes 10 minutes for the application to show up on the direct link, then anywhere up to 24 hours to be searchable from within the app store.
From personal experience, I always set the release date to the date that I submitted it to the app store. This way as soon as its processed its released for sale. If the app is already approved and you had it originally set for a future date. Take the current date and time. It should release within a few minutes.
I uploaded an app on itunesConnect and i set availability date on 20/02/2012. Yesterday I received an email that say that my app is in "Processing for appStore"; today I have entered in itunesconnect and I have seen that my app is ready for sale; but in the version summary app availability date is 20/02/2012. What does it mean? Can I be sure that my app begin the sale on 20/02/2012?
Relax, the availability date controls when others can download it. But once the approval process is finished it'll be ready for sale, which reserves the page URL for it and allows you to send out redemption codes should you want others to download it early for testing etc.