bitemyapp / bitemyapp/twitcurl
Example App does not authenticate with OAuth
- Dominant language
- C
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
```
What steps will reproduce the problem?
1. download and and run twitterClient.exe -u username -p password (where
username and password are valid, tried two twitter accounts)
What is the expected output? What do you see instead?
2. "Do you want to visit twitter.com for PIN" (either choice seems to fail):
Saying no brings up a web response of Could not authenticate with
OAuth. and saying yes provides no URL to enter
I would expect the PIN to of course succeed automatically, or be provided with
a URL to enter in the respective scenarios.
What version of the product are you using? On what operating system?
latest twitterClient.exe
Please provide any additional information below.
I'm having the same set of issues trying to implement twitcurl in code with
keys created by myself.
Could anyone please help me identify if the problem is somehow on my end of
things? Any suggestions? Does twitterClient.exe (Still) work for anyone
reading this?
Thanks in advance!
```
Original issue reported on code.google.com by `st...@xferrecords.com` on 5 Jan 2012 at 6:59
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the reported flow with twitterClient.exe using the documented username and password steps, then inspect the twitcurl OAuth authentication entry points. Compare the PIN and browser outcomes with the expected OAuth flow; the issue does not identify files, tests, or a defined completion criterion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- authentication, security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100