-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to call App Store Server API sandbox environment #92
Comments
@sigriswil If you don't have a production release of the app, you are not allowed to use the production App Store Server API. Once you release an app for the first time in production, then you will be able to receive a TRANSSACTION_ID_NOT_FOUND exception |
Thank you for your answer. We manage multiple app information and don't know if the apps have a production release. Even if there is a production release, the token hasn't expired, and very occasionally returns a 401 response for unknown reasons. Is there a way to know if it's an actual 401 error, or a 401 error because there's no production release? |
Is this the scene? (httpStatusCode=401, apiError=null, apiErrorMessage='null') #96 |
Yes. I happen in the 'Get Transaction Info' API. |
The issue appears to have changed into a duplicate of #96, closing this issue in favor of that issue |
I call transaction information for several apps. And I don't have environment information.
That's why I'm calling the sandbox environment as an official guide. However, unlike the official guide, certain apps sometimes use production URLs to call endpoints to receive 401 status codes and successfully call endpoints using the sandbox environment.
Why does this difference occur unlike the official guide?
Is there any way to determine if I should call into a sandbox environment when I receive a 401 status code from a production endpoint?
Sometimes it's a production transaction and JWT hasn't expired, but I'm getting a 401 status code response and calling it into a sandbox environment.
Please let me know the solution.
The text was updated successfully, but these errors were encountered: