OAuth 2.0 PKCE authorization fails after user approval before callback

Дата публикации: 28-08-2026 08:08:33

What’s your App ID
Available to X Support on request. Both our production app and a newly created Native App / Public Client reproduce this issue.
What endpoint are you using
GET https//x.com/i/oauth2/authorize
What API version are you on
OAuth 2.0 Authorization Code Flow with PKCE.
What is the issue
The consent page loads normally and shows tweet.read and users.read. After a user selects Authorize app on mobile X shows “Something went wrong —— You weren’t able to give access to the App. Go back and try logging in again.” The callback URI is never reached so our app receives no code and never calls the token endpoint.
Steps to reproduce the issue
Open a valid authorization URL with responsetype=code PKCE S256 and an exactly registered custom-scheme redirect URI.
Sign in with X and select Authorize app on mobile.
X shows the error page before redirecting to the callback URI.
When did it start
August 26 2026 persists across repeated tests.
What have you tried
Both apps are active on a Pay Per Use project.
A new Native App / Public Client reproduces the same post-consent failure.
Exact redirect URI and PKCE parameters verified.
The shared project has US5.00 prepaid credits.
Please check for an account-level project-level or OAuth authorization-service restriction/error. We can provide timestamps client IDs and screenshots privately. No client secrets tokens codes or PKCE verifiers are included.What’s your App ID?
What endpoint are you using?
What API version are you on?
Are you using a library or SDK? Which one?
What is the issue?
Steps to reproduce the issue
Step 1:
Step 2:
What is the error message?
When did it start?
What have you tried to troubleshoot?
2 posts - 2 participants
Read full topic

Схожие новости

#	Наименование новости	Тональность	Информативность	Дата публикации
1	OAuth 2.0/authorize fails with 'Something went wrong' on Pay Per Use tier. Al settings verified: billing, enrollment, callback, credentials	0	7.65	30-08-2026
2	OAuth 2.0 regression / authorization rejects numeric-only state values	0	9.79	27-08-2026
3	Pay-Per-Use app: OAuth 1.0a user context returns 401 on both GET and POST v2 endpoints	0	10.43	27-08-2026
4	API authorization issue OAuth2	0	8.78	28-08-2026
5	Pay-Per-Use: compliance jobs upload_url / download_url return 404 (control plane works) — App ID 33340874	0	11.64	27-08-2026
6	X Can't post link	0	9.12	30-08-2026
7	X API v2 returns HTTP 500 with empty response body across multiple endpoints	0	8.24	27-08-2026
8	Ads API 403 and App Manager cannot resolve JTP iOS and Android identifiers	0	7.88	28-08-2026
9	Do human-reviewed AI reply suggestions need additional approval?	0	9.98	27-08-2026
10	Url contains malware URL for callback url	0	8.24	28-08-2026

Классификация: . Схожих патентов: 0. Схожих новостей: 10. Тональность: 0. Информативность: 7.24. Источник: twittercommunity.com.