Skip to content
This repository has been archived by the owner on Sep 20, 2023. It is now read-only.

Unable to comment on any issue or PR #2402

Closed
bkase opened this issue Nov 4, 2018 · 7 comments
Closed

Unable to comment on any issue or PR #2402

bkase opened this issue Nov 4, 2018 · 7 comments
Labels
❔ question Question pending discussion or card yet to be correctly triaged

Comments

@bkase
Copy link

bkase commented Nov 4, 2018

Whenever I try to comment on an issue or PR, I get a "Something went wrong" error message and the message doesn't send.

If it matters: This is on a public repo within an organization that has not been granted access to githawk ( https://github.com/CodaProtocol/coda ).

Please let me know if you need any more info. Thanks!

Bug Report Dump (Auto-generated)
Version 1.22.0 (1534395229)
Device: iPhone X (iOS 12.0)
TestFlight: false
@rnystrom
Copy link
Member

rnystrom commented Nov 4, 2018

@bkase could you try the TestFlight build and see if this still occurs? Also we have Flex enabled so we can get the raw response if necessary.

https://testflight.apple.com/join/QIVXLkkn

@rnystrom rnystrom added the ❔ question Question pending discussion or card yet to be correctly triaged label Nov 4, 2018
@ijm8710
Copy link

ijm8710 commented Nov 4, 2018

@rnystrom this probably relates to the credential stuff. I’ve been seeing this a lot

@bkase
Copy link
Author

bkase commented Nov 4, 2018

Although you appear to have the correct authorization credentials, the CodaProtocol organization has enabled OAuth App access restrictions, meaning that data access to third-parties is limited. For more information on these restrictions, includeing how to whitelist this app, visit https://help.github.com/articles/restricting-access-to-your-organization-s-data/

So I guess I need to authorize Githawk in order to post? Any advice for justifying access to my organization?

@bkase
Copy link
Author

bkase commented Nov 4, 2018

(the quote was the error message when posting in the test-flight build)

@Huddie
Copy link
Collaborator

Huddie commented Nov 4, 2018

@rnystrom this probably relates to the credential stuff. I’ve been seeing this a lot

@ijm8710 my thoughts

Sent with GitHawk

@rnystrom
Copy link
Member

rnystrom commented Nov 5, 2018

Yup, closing in favor of #2165

@bkase if you sign out and sign back in using a PAT w/ repo+user+notification scopes it'll go away. Atm appears to be an auth issue w/ the GraphQL API.

screen shot 2018-11-04 at 7 09 14 pm

@rnystrom rnystrom closed this as completed Nov 5, 2018
@bkase
Copy link
Author

bkase commented Nov 5, 2018

Thanks @rnystrom , that works!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
❔ question Question pending discussion or card yet to be correctly triaged
Projects
None yet
Development

No branches or pull requests

4 participants