I need a solid answer for my case. My company has an Enterprise account and we have already used it to publish some apps to our clients through private store. The account has been renewed for another year.
Activation Date: February 2, 2023 Expiration Date: February 2, 2024
My question, is there any action that should be taken like uploading a new version of the app before this date or even after this date ?
Please note that the certification(used to signed the app) expires in next October 2023.
The case if very critical and we don't want the app to be stopped suddenly.
Related
I have a one year auto-renewable subscription in my app with a three day free trial. According to Apple, while testing in the sandbox, a one year subscription is equivalent to one hour but it says nothing about how long the free trial is. Add to this, when I'm testing and I sign-up for the free trial, the receipt doesn't list a separate transaction for a free trial, it simply lists the first hour long subscription:
transactionIdentifier: 1000000408088544
purchaseDate: Sat Jun 16 19:58:59 2018
originalTransactionIdentifier: 1000000408088544
originalPurchaseDate: Sat Jun 16 19:59:00 2018
subscriptionExpirationDate : Sat Jun 16 20:58:59 2018
I could just check and see if the current date is less or greater than originalPurchaseDate plus three days, but shouldn't another transaction be generated when the free trial ends and the subscription is automatically renewed? That's not happening in the sandbox so I'm unsure of the behavior to expect outside of the sandbox.
In the receipt format documentation, under "Subscription Trial Period", there is a "is_trial_period" key stored in the receipt, however I am validating the receipt locally and believe that I am unable to obtain this value since there is no ASN.1 Field Type and it seems to be stored in JSON when doing server validation.
Does anyone have any clue how to test this or know what the behavior is supposed to be?
I see this message when I sign into iTunesConnect:
"The iAd App Network will be discontinued as of June 30, 2016. Although we are no longer accepting new apps into the network, advertising campaigns may continue to run and you can still earn advertising revenue until June 30. If you’d like to continue promoting your apps through iAd until then, you can create a campaign using iAd Workbench."
I have looked around at what it means and have seen multiple, very different answers. What does it mean, exactly? I guess questions I would like answered are:
1) Will my current apps already in the store still be able to show/monetize iAds?
2) Will new apps submitted before June 30th be able to use iAd for monetization?
3) Will any apps submitted after June 30th be able to utilize iAd for monetization?
One answer I saw was that you can still use iAd and make money, Apple just isn't being the one providing the ads. Another answer said that once this date rolls around, you can't use them at all, and you won't be able to make any money. Basically they won't work.
Can anybody weigh in?
I am developing a new app - not yet submitted, about to submit.
I emailed Apple last week to see if submitting a new app could still integrate iAds, hoping I could still use iAds until June 30, 2016.
This is the response I got:
Hi Paul,
Thanks for your interest. After June 30th, the iAd app network will
no longer be available to help monetize your app. No new apps will
be accepted into the network if you are not live already. We have
campaigns live within our network up until that date. You should
connect with another provider as an alternative to iAd. Workbench
will still be available to promote your app. Thanks for being a part
of our network.
Please go to our developer site to get the latest news regarding iAd
here
Best,
Louis
This is pretty clear. NO new apps will be approved into the iAd network.
So, in response to your questions as listed:
1) Will my current apps already in the store still be able to
show/monetize iAds?
Yes, until June 30, 2016.
2) Will new apps submitted before June 30th be able to use iAd for
monetization?
3) Will any apps submitted after June 30th be able to utilize iAd for
monetization?
No. They will not.
What this means
After June 30th the ad network won't provide any ads to apps using it nor will you be able to start an iAd advertising campaign.
Your Questions
1) 2) Current apps and apps submitted before June 30th can show and monetize iAds. When June 30th comes they will no longer show ads or make money.
3) Apps submitted after June 30th will not be able to utilize iAd monetization.
What to do
Before June 30th integrate another ad network into your app if you wish to continue making ad revenue.
When I restore the user's purchases in ther iOS device, they can access the content if the subscription is currently active. What I want to do is grant access to the content published in the past if they had an active subscription then.
Example:
Anne purchases a 6 month subscription to a magazine on January 1st. When it ends she doesn't renew it. Then in October she has to format the iPad and reinstall the app. When she wants to download the February issue, is there a way to know that the subscription was active then?
You should check in app receipt, where you can find Subscription original Purchase date and subscription Expiration or Cancellation Date. Here is documentation
I have a magazine app and want to implement auto-renewable subscriptions. There are 2 issues released every year. The first issue is released in april and the second issue a half year later in october.
If I implement a one-year subscription, how do I handle the subscription?
Here are my problems:
First: the user subscribed in August and is getting the april issue. Then in october the user is getting the october issue. In april next year the user has still a valid subscription but shouldn't get the april issue because his subscription ends in august. He only get the new april issue, if he renew the subscription.
My second problem is: I don't know if the user is renewing his subscription until august and can't deliver the new issue in april.
I hope you can understand the described problem and have some tips to put me in the right direction.
I'm planning to use Non-Renewing Subscription type of In-App Purchase in my application. I have a couple of questions:
Can I allow the user to choose the start date/time for subscription?
For example, user wants to subscribe for a week, starting from 14 November (Wednesday) to 20 November (Tuesday).
Can I allow the user to subscribe for different time periods (in future)?
For example, today is 14 November and user wants to subscribe for a week in November (Monday, 19 November to Sunday, 25 November) and for December (Saturday, 1 December to Monday, 31 December).
Can I control the subscription logic from a server (via web services)?
For example, when user purchases a subscription for a week, the information is stored on the server. On consecutive logins, on same or different device, the status of the subscription will be received from the server. Note that the application (inherently) requires a Register/Login mechanism to work.
p.s. I'm not using Auto-Renewing Subscription type of In-App Purchase for a number for reasons, including the fact that I can't because of the following guideline:
11.15 Apps may only use auto renewing subscriptions for periodicals (newspapers, magazines), business Apps (enterprise, productivity, professional creative, cloud storage) and media Apps (video, audio, voice), or the App will be rejected.
Based on my experience, here are the responses to my own questions.
Can I allow the user to choose the start date/time for subscription?
Yes.
Can I allow the user to subscribe for different time periods (in future)?
I ended up not doing that, but based on the feedback I received, you can.
Can I control the subscription logic from a server (via web services)?
Yes.