Access Problem

[HanYiCheah1]

Referring back to the topic I cant access the app, I look through all the comments and checked the encoding around the scope and the forum for that is closed so I can’t comment on it. I am facing the similar problem where I can’t access it and it popped out with There is something went wrong and I aren’t able to give access to the app.

[HanYiCheah1]

My URL: https/twitter.com/i/oauth2/authorize?client_id=OUpxeThzVXVBY2NwLUd1bWtSUkg6MTpjaQ&scope=tweet.write%20tweet.moderate.write%20users.read%20follows.read%20follows.write%20offline.access%20space.read%20mute.read%20mute.write%20like.read%20like.write%20list.read%20list.write%20block.read%20block.write&redirect_uri=http://localhost:4000&response_type=code

[gauloics]

Hi welcome to the community

@HanYiCheah1

redirect_uri=http://localhost:4000

It might be a bit complex, but the first thing I noticed was redirect_uri, This is about callback urls, where the rule is not allowed using localhost:xxxx read docs https://developer.twitter.com/en/docs/apps/callback-urls
Try fix this first

Second, there is a missing parameter, this parameter is missed in your code:

• state
• code_challenge
• code_challenge_method

Ref. https://developer.twitter.com/en/docs/authentication/oauth-2-0/authorization-code

[HanYiCheah1]

Hi @gauloics and thx for the welcoming me to the community.
After changing the things that you recommended, I am still facing the same issue. Do you have any other recommendation for this particular issue?

My new url: https:/twitter.com/i/oauth2/authorize?client_id=OUpxeThzVXVBY2NwLUd1bWtUkg6MTpjaQ&scope=state%20tweet.write%20tweet.moderate.write%20users.read%20follows.read%20follows.write%20offline.access%20space.read%20mute.read%20mute.write%20like.read%20like.write%20list.read%20list.write%20block.read%20block.write&redirect_uri=http://127.0.0.1:4000&response_type=code&state=state

[dewey]

Did you add it to the whitelisted list of callback URIs in your project settings?

[gauloics]

@HanYiCheah1

redirect_uri=http://127.0.0.1:4000

@gauloics

This is about callback urls, where the rule is not allowed using localhost:xxxx

I recommend using an address like example.com, ngrok is useful if it’s still in development

@jessicagarson

I haven’t gotten localhost to work, but I have used ngrok in the past or example.com. Also, you will need several scopes, not just tweet.write for this to work. You can find the full list of scopes per endpoint here.

[HanYiCheah1]

yes i did but it still not working

[HanYiCheah1]

Hi @gauloics, even after i push my twitter login to the original server, I still receive the same problem

the new URL: https:/twitter.com/i/oauth2/authorize?client_id=OUpxeThzVXVBY2NwLUd1bWtUkg6MTpjaQ&scope=state%20tweet.write%20tweet.moderate.write%20users.read%20follows.read%20follows.write%20offline.access%20space.read%20mute.read%20mute.write%20like.read%20like.write%20list.read%20list.write%20block.read%20block.write%20code_challenge%20code_challenge_method&redirect_uri=https://engine.nexent.co&response_type=code

[gauloics]

https://twitter.com/i/oauth2/authorize?response_type=code&client_id=M1M5R3BMVy13QmpScXkzTUt5OE46MTpjaQ&redirect_uri=https://www.example.com&scope=tweet.read%20users.read%20follows.read%20follows.write&state=state&code_challenge=challenge&code_challenge_method=plain

@HanYiCheah1

code_challenge%20code_challenge_method

Try this

https://twitter.com/i/oauth2/authorize?response_type=code&client_id=OUpxeThzVXVBY2NwLUd1bWtUkg6MTpjaQ&redirect_uri=https://engine.nexent.co&scope=tweet.read%20tweet.write%20tweet.moderate.write%20users.read%20follows.read%20follows.write%20offline.access%20space.read%20mute.read%20mute.write%20like.read%20like.write%20list.read%20list.write%20block.read%20block.write&state=state&code_challenge=challenge&code_challenge_method=plain