What happens if the user changes the apple id in itunes and then opens the app. The receipt he will get will be still of the old one until you are not refreshing. If you gave a time period of 1 month, your receipt will be updated after that only? How can we deal with that situation?
Post
Replies
Boosts
Views
Activity
Hi,
This is our application consistently rejected
https://apps.apple.com/in/app/mint-business-news/id470175900
AppId: 470175900
We have already implemented the verification of receipt first on production and if get status as 21007 then we are validating the same on sandbox a long time back.
Just to know what exactly is failing, we have put now hardcode error messages in our binary 4.25 (4.2):
When Receipt fails in this delegate of StoreKit
func request(_ request: SKRequest, didFailWithError error: Error) { }
Here error will be:
"There is problem connecting with iTunes. Please try again later."
NOTE:- The screenshot given by the apple reviewer shows the above error which proves that this is an error while fetching receipt from apple in the sandbox
Please review the forum link as well where other people/organizations are also facing the same issue.
https://developer.apple.com/forums/thread/661351
Request you to please check your receipt server of apple before rejecting the app as it is quite common from the above link.
We have tried debugging from head to toe and found nothing related to the error posted above. However, we encountered this error once when the apple StoreKit wasn't able to provide the receipt and control went to
func request( request: SKRequest, didFailWithError error: Error) { } failure delegate.
So, the thing is that they are not even getting the receipt which proves from the error which we hardcoded in the app that the control is coming in func request( request: SKRequest, didFailWithError error: Error) { } delegate.
"There is problem connecting with iTunes. Please try again later."
NOTE:
We have tested the same on a real device with the latest iOS(14.3 currently) and not in the simulator.
Also, we have uploaded app purchases many times earlier with this app without any problems. This is the first time in iOS 14 we are facing these continuous rejections.
We have already appealed the same.
If we are unable to understand anything, let us know the next steps.
Please let us know apple reviewer that their StoreKit is constantly failing and it has nothing to do with what they are sending in rejections.
I again believe it is from Apple end where there storekit function always fails
One crucial step to make things autofill and to use ASPasswordCredential is to add the webcredentials settings in your Apple App Site Association file. Otherwise, you will always receive the "No Credentials available for login" error.
If you do not add there and you do not add the associated-domains in your application, you will never receive autofill specific user ID passwords and accounts for ASPasswordCredential specific to that application or domain.
This will also help in preventing duplicate account creation.
I have made a video explaining how we can use ASPasswordCredential. You can have a look
https://www.youtube.com/watch?v=qD4e5YR8R6s