Skip to content
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

OAuth errors return JSON instead of returning to the flow #24

Open
pgib opened this issue Nov 25, 2024 · 1 comment
Open

OAuth errors return JSON instead of returning to the flow #24

pgib opened this issue Nov 25, 2024 · 1 comment

Comments

@pgib
Copy link

pgib commented Nov 25, 2024

There are a number of scenarios where the Threads OAuth flow returns a JSON error instead of redirecting back to the flow. (Also if the user hasn't yet created a Threads account but does have an Instagram account)

image
@pestevez
Copy link
Contributor

pestevez commented Dec 3, 2024

We are looking into some of these errors, but if you have a list of the instances in which you get the JSON, I can share it internally.

For the one that you list in your report, i.e. "The user has not accepted the invite to test the app", the issue is that the app's Threads use case is not live yet, meaning that only the testers can use the app.

Threads testers can grant your app these permissions at any time. In order for app users without a role on your app to be able to grant your app these permissions, each permission must first be approved through the App Review process, and your app must be published.

The user that generated the access token needs to accept the invitation to test the app.

A couple of helpful links to the documentation:

  1. Authorization
  2. Threads Testers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants