Having issues creating a subscription, specifically setting the expirationDateTime field in the beta API.
According to the docs maximum expiration time is '4320 minutes (3 days)' on the contacts resource.
When I make the request, I receive an error message of Subscription expiration can only be 4230 minutes in the future. Obviously this conflicts with their documentation. Now, if I adjust the expirationDateTime attribute I am sending to make a subscription request from 4320 minutes to 4230 minutes, it works as expected.
Is this a documentation issue or a mistype in their API source?
Resources:
https://developer.microsoft.com/en-us/graph/docs/api-reference/beta/resources/subscription
https://developer.microsoft.com/en-us/graph/docs/api-reference/v1.0/resources/subscription
This is an issue in the documentation. It is being updated now. The maximum lifetime is 4230 minutes.
Related
I have requested a quota increase on the YouTube Data API.
I am getting the impression I’m being given the run around or no one inside of Google actually works on this.
I requested a quota increase over 3 weeks ago, and every time I email them, I get a very generic:
We understand your concern about the Quota. As informed earlier your request is being reviewed by our Quality Compliance Team. Their review takes longer time and hence is causing the delay. Any update that we receive from them will be shared with you immediately.
But it’s been 3 weeks.
Has anybody else had the same experience? If so, how long did it take to get approved?
We use auto-renewable subscriptions in our application and we set free trials as an introductory offer. But we haven't experienced what if the trial length changes yet.
If we change the free trial length of an existing subscription package, are the existing users notified via e-mail or notifications?
For example we are applying 7-days free trial for our subscription now, what if we change this period with 3-days? Will the subscribers in the trial period (let's say he is on the 5th day of free trial) be notified? In other words, will the existing subscribers in trial period continue with 7 days and new subscribers start with 3 days to trial period?
Is there anyone who has experienced this before?
Thanks for all replies in advance.
AppStore generate a receipt for every IAP separately so, subscription start date and end date are there. If someone registered for 7 days and 3 days has passed. when you changed trial period to 3 days it does not affect the previous trial period. They still use 7 day trial until the "their" trial period end.
How can I set the expiration time for twilio's authy OTP sent via SMS. I don't see how to change the default expiration time anywhere in the docs. I would like the OTP to remain valid for 30 min.
Twilio developer evangelist here.
I'm afraid you cannot change the expiration time for the OTP with Authy.
30 minutes seems like a riskier length of time to allow for one token to be active. There is some drift with tokens, you don't need to enter it within 30 seconds, but half an hour is not among any recommended lengths of token expiration time.
We get the user cancels in the next 30 days from our database and we call to Apple one to one
https://buy.itunes.apple.com/verifyReceipt
We want to call for a list of user cancels in the next 365 days which can be a huge list.
I look for that in the documentation and in google but I couldn't find if there is a limit on the number of requests to Apple.
Does anyone know that?
After contact Apple's support, there are not query limits.
I have this endpoint implemented several months ago and I make a huge number of requests every day without any problem.
It's the only way to verify the status of each receipt because their webhook doesn't seem reliable.
Our iOS App supports yearly subscriptions with different free trial periods. We are aiming to evaluate the receipts available locally on user's device offline.
**We are planning to do this: **
Check if cancellation_date exists - inactive subscription
If cancellation_date doesn’t exist, check if purchase_date exists:
if yes, check if expires_date exists and is in an active period - active subscription
if not, check if expires_date exists and is in an active period - may be trial period
The thing we cant figure out is, if user turns-off subscription in trial period stopping payment, how can the app know such events?
Does expires_date indicate "trial duration + 1 Year" or only "1 year"?
Does original_purchase_date or purchase_date indicate "start of trial" or "the date user has made payment"?
Note: We also plan to periodically refresh local receipt using
SKReceiptRefreshRequest.
Make sure you are looking at the sub-contents of all the in_app entries, ASN1 type 17. There will be one for each renewal.
Cancellation date is only set if the subscription is cancelled by Apple customer service, you should mostly depend on the expiration date.
The trial is treated as separate in_app field in the in_apps array. So as long as you are looking for the latest expires_date field, you will be computing the correct expiration date.
Also, I'm not sure how up to date the in_apps are when using SKReceiptRefreshRequests. Apple says to use server side validation, and the /verifyReceipt endpoint when using subscriptions.
Shameless plug, but if you are trying to implement subscriptions with less effort you might want to try my service, RevenueCat. We handle all the receipt parsing and tracking for you and do it correctly. You can sign up with my referral code.