Twitter/X OAuth login fails: 'You weren’t able to give access to the App'

[ColeYoho]

Summary

acp social twitter login returns an OAuth URL, but the X authorization page fails with:

Something went wrong
You weren’t able to give access to the App. Go back and try logging in again.

As a result, the agent cannot be linked to X.

Version / Environment

• openclaw-acp: v0.4.0
• Installed from: https://github.com/Virtual-Protocol/openclaw-acp/releases/tag/v0.4.0
• Runtime: Linux (OpenClaw skill environment)

Reproduction

1. Run acp setup and complete login + agent creation.
2. Run acp social twitter login.
3. Open the returned https://x.com/i/oauth2/authorize?... URL.
4. Login/authorize on X.

Expected

Authorization succeeds and redirects through https://claw-api.virtuals.io/x/auth/callback, after which X-linked commands work.

Actual

X shows:

• You weren’t able to give access to the App. Go back and try logging in again.

Then ACP remains unauthenticated for X. Example follow-up:

• acp social twitter timeline --max-results 5 --json
• Returns: {"error":"Failed to fetch timeline: {\"statusCode\":500,\"message\":\"Agent not authenticated with X\"}"}

Additional Diagnostics

• POST /x/auth/initiate from ACP backend succeeds and returns authUrl.
• Retried after acp social twitter logout + regenerated fresh auth URLs: same result.
• Tried reduced scope (removed tweet.write): same X error.
• This does not appear to be caused by local hardening patches, since social login files were unchanged (src/commands/twitter.ts, src/lib/twitterApi.ts).

Suspected Area

Possible OAuth app/backend config mismatch on the server side (X app settings, redirect URI/permissions/state handling), since failure happens on X authorization page before ACP can proceed.

[pmmochi]

Thanks for the detailed report! This looks like an OAuth app configuration issue on the X Developer Portal side.

We'll need the backend team to verify:

• Redirect URI matches exactly what's configured in the OAuth app
• App permissions include the scopes being requested
• App status isn't suspended or restricted

I'll escalate this internally and get back to you. In the meantime, if you have access to the X Developer Portal, double-checking the callback URL and app status might surface something obvious.