Closed jurijsk closed 4 years ago
Unable to reproduce this on Mac - it looks like this is falling over reading the .twurlrc file. Can you find one after authentication succeeds? Does twurl accounts
work?
Hi @andypiper!
Yes found .twurlrc
under c:\users\{username}
and it looks like it contains what looks like keys and secrets. twurl accounts
also works.
Also trier to use twurl
in PowerShell instead of bash and everything works perfectly. So I guess it is environment configuration. Just strange that I have installed everything using bash and it does not work there at the end.
Great to hear you're up-and-running - super strange issue. I'll leave this open in case anyone is able to do a bit more digging on Windows with bash at some point.
While the actual reason behind this error remains unknown it's not great to return backtrace in such a way, so I've fixed the code to not return the backtrace at least.
E.g.,
$ twurl -
Invalid URI detected
*This command returns backtrace in the latest version.
@jkovzels Out of curiosity, is that still reproducible if you put the URL inside the single/double quotes?
$ twurl "/1.1/statuses/home_timeline.json"
looking at your backtrace, it's hitting alias_from_name
meaning we were likely unable to parse your arguments (or, it didn't match regex) somehow and tried to find aliases as a fallback, and got this error because you had no aliases configured. Wondering if that's some kind of encoding issue or not, but I can't verify that either. Did you run that command on WSL 2 terminal?
Close until further reports come in.
Running
twurl /1.1/statuses/home_timeline.json
after successful authentication leads to: