authentication fails #1

New Issue

2021-01-02T15:57:12Z

ericsfraga commented

2021-01-02 15:57:12 +00:00

(Migrated from github.com)

I've added nntwitter to my secondary select methods but as soon as I start gnus, it fails with
nntwitter-api-set-oauth-tokens: ‘nntwitter-api-set-oauth-tokens’: authentication failure
I did originally have eww as my default browser. I did change this to default browser so that Firefox pops up. I do get the twitter authentication page which gives me a PIN but there is nowhere to type that pin in within Emacs.

I've added nntwitter to my secondary select methods but as soon as I start gnus, it fails with `nntwitter-api-set-oauth-tokens: ‘nntwitter-api-set-oauth-tokens’: authentication failure` I did originally have eww as my default browser. I did change this to default browser so that Firefox pops up. I do get the twitter authentication page which gives me a PIN but there is nowhere to type that pin in within Emacs.

dickmao commented

2021-01-02 16:33:40 +00:00

(Migrated from github.com)

nowhere to type that pin in within Emacs.

Note after M-x nntwitter-api-route-auth, a *Warnings* window says "Please check your browser" and the minibuffer prompts "PIN".

If you are not seeing either of these, and if your waning interest can sustain it, you'd need to add print statements here to see why after firefox pops up, the above behaviors do not exhibit.

> nowhere to type that pin in within Emacs. Note after `M-x nntwitter-api-route-auth`, a `*Warnings*` window says "Please check your browser" and the minibuffer prompts "PIN". ![nntwitter-pin](https://user-images.githubusercontent.com/7578770/103461553-30864c80-4ced-11eb-8ea0-d26d245dbc74.gif) If you are not seeing either of these, and if your waning interest can sustain it, you'd need to add print statements [here](https://github.com/dickmao/nntwitter/blob/94916ad8c3e3bf697855c58257f92cd697c9521a/lisp/nntwitter-api.el#L101) to see why after firefox pops up, the above behaviors do not exhibit.

ericsfraga commented

2021-01-02 17:56:56 +00:00

(Migrated from github.com)

I saw neither the warning window nor the minibuffer prompt for the PIN. And I checked my Messages buffer just in case I missed something but there was nothing there beyond the error message shown above.
I am curious: why is my interest waning?
In any case, I'm surprised you have closed this issue. But, okay.

I saw neither the warning window nor the minibuffer prompt for the PIN. And I checked my *Messages* buffer just in case I missed something but there was nothing there beyond the error message shown above. I am curious: why is my interest waning? In any case, I'm surprised you have closed this issue. But, okay.

dickmao commented

2021-01-02 18:49:24 +00:00

(Migrated from github.com)

I cannot tell from your response whether you "saw neither the warning window nor the minibuffer prompt" when recollecting your initial attempt at nntwitter, or if you manually followed my prescription of M-x nntwitter-api-route-route-auth. If the latter, then I remain curious as to what the aforementioned print statements might reveal, but my experience is that users (myself included) rarely attempt this kind of debugging. Thus, my remark about "waning interest."

I cannot tell from your response whether you "saw neither the warning window nor the minibuffer prompt" when recollecting your initial attempt at nntwitter, or if you manually followed my prescription of `M-x nntwitter-api-route-route-auth`. If the latter, then I remain curious as to what the aforementioned print statements might reveal, but my experience is that users (myself included) rarely attempt this kind of debugging. Thus, my remark about "waning interest."

ericsfraga commented

2021-01-03 18:42:09 +00:00

(Migrated from github.com)

Ah, okay. I did not see any such windows and I did not try the command directly. I had simply started gnus. Trying the command directly gets me no further unfortunately. I have put a print statement where indicated and it appears (i.e. is executed) but no PIN prompt appears.

dickmao commented

2021-01-03 18:49:39 +00:00

(Migrated from github.com)

Then it must be erroring out. I would set M-x toggle-debug-on-error, then retry M-x nntwitter-api-route-auth.

Then it must be erroring out. I would set `M-x toggle-debug-on-error`, then retry `M-x nntwitter-api-route-auth`.

ericsfraga commented

2021-01-04 09:36:27 +00:00

(Migrated from github.com)

Yes:

Debugger entered--Lisp error: (wrong-type-argument listp "")
warning-suppress-p("" ((emacs) (undo discard-info)))
display-warning("" "Please check your browser and follow the instructi..." :warning)

Yes: ``` Debugger entered--Lisp error: (wrong-type-argument listp "") warning-suppress-p("" ((emacs) (undo discard-info))) display-warning("" "Please check your browser and follow the instructi..." :warning) ```

dickmao commented

2021-01-04 14:07:32 +00:00

(Migrated from github.com)

Sorry about that. Commit 01a6fa1. Thanks for reporting the bug.

Sorry about that. Commit 01a6fa1. Thanks for reporting the bug.

ericsfraga commented

2021-01-04 14:53:22 +00:00

(Migrated from github.com)

Thank you! I will try this later (busy with online teaching at the moment.... the joys of the pandemic).

Sign in to join this conversation.