#sinduri_code
1 messages ¡ Page 1 of 1 (latest)
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1296803109061918730
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- sinduri_api, 1 hour ago, 45 messages
I think we answered all these questions in your last thread, no? https://discord.com/channels/841573134531821608/1296753314074988557
What is still unclear
One of our customer report that refresh token in test mode is invalid after generating it in live mode?
That's why I'm confirming it again
Yes that's expected. The tokens are only valid in the mode in which they're generated
So you can't use a test mode token in live mode and vice versa
But the customer reported it in another way. After generating live refresh token , the refresh token generated initially in test mode is become invalid when he try to refresh the access token in test mode
Hi! I'm taking over from my colleague. Please, give me a moment to catch up.