Просмотр новости
Найдите то, что Вас интересует
Спутники
РН
SpaceX
Роскосмос
NASA
СпутникиРНSpaceXРоскосмосNASA
What’s your App ID?
33372800
What endpoint are you using?
/i/oauth2/authorize (OAuth 2.0 Authorization Code Flow with PKCE)
What API version are you on?
X API v2, Pay Per Use tier
Are you using a library or SDK? Which one?
No SDK — connecting via a third-party AI assistant’s built-in custom OAuth connector, which constructs the authorize request directly.
What is the issue?
Every request to /i/oauth2/authorize returns “Something went wrong — You weren’t able to give access to the App,” both when initiated through the third-party connector flow and when hitting the authorize URL directly in the browser. This happens consistently and has persisted across multiple days and multiple credential regenerations.
Steps to reproduce the issue
Step 1:
Step 2:
What is the error message?
“Something went wrong. You weren’t able to give access to the App. Go back and try logging in again.”
When did it start?
started: 29 August, 2026, 15:30-20:00 UTC+1
repeated: 30 August, 2026, 15:30-16:30 UTC+1
What have you tried to troubleshoot?
Verified the Callback URI matches exactly what’s registered in the app settings
Verified App type is Web App, Automated App or Bot (Confidential client), permissions set to Read and write
Regenerated Client ID/Client Secret and re-tried with fresh credentials
Confirmed Default Project shows “Connected” status under Project Access
Confirmed Pay Per Use billing is active: positive credit balance, payment succeeded, no failed transactions or pending billing steps
Confirmed via a direct browser request that the API endpoint itself is reachable and responding normally with a valid JSON error listing supported auth types, ruling out a basic outage
None of the above resolved the issue — the authorize screen fails before any consent screen is shown
1 post - 1 participant
Read full topic
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | OAuth 2.0 PKCE authorization fails after user approval before callback | 0 | 7.24 | 28-08-2026 |
| 2 | Pay-Per-Use app: OAuth 1.0a user context returns 401 on both GET and POST v2 endpoints | 0 | 10.43 | 27-08-2026 |
| 3 | OAuth 2.0 regression / authorization rejects numeric-only state values | 0 | 9.79 | 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 API v2 returns HTTP 500 with empty response body across multiple endpoints | 0 | 8.24 | 27-08-2026 |
| 7 | Ads API 403 and App Manager cannot resolve JTP iOS and Android identifiers | 0 | 7.88 | 28-08-2026 |
| 8 | X Can't post link | 0 | 9.12 | 30-08-2026 |
| 9 | $200 recurring monthly charges despite project being on pay per use | 0 | 9.39 | 29-08-2026 |
| 10 | App Suspended (28881659) but Account in Good Standing, can still post | 0 | 8.99 | 27-08-2026 |