-
Notifications
You must be signed in to change notification settings - Fork 214
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
manage.authorize promise is not resolved or rejected #41
Comments
Yes, what version are you using? Try passing a second argument. Does that fix it? |
I was trying with 2.1.11. I just tried 2.1.13 with and without a second argument and the promise is still not resolved or rejected. I'm not sure what to pass as a second argument though. I just passed an empty object. |
I'm having the same issue but with Google Oauth. I am able to allow access to the app, but google does not redirect me back into the app and the promise never resolves. |
I was able to get it working for Google. Looks like the only scope I'm able to pass is 'email'. The url to pass as an argument for manager.makeRequest is 'https://www.googleapis.com/plus/v1/people/me' |
Closing in favor of #42. You need to make sure you have the app set up properly. I'll add a checklist on the README to discuss this. |
I followed the readme except for when I enabled Keychain Sharing Entitlement in Capabilities I got an error icon next to "Add the Keychain Sharing feature to your App ID" and a message under it saying "Failed to create provisioning profile". Anyway, I was (possibly incorrectly) hoping I could ignore it and see if I could get further into my prototype. I got the rest of the setup done but when my code executes
manager.authorize
, the resulting promise never gets resolved or rejected. I don't get any kind of error in the debugging console and I don't see requests go to Twitter in the network tab.My code looks like this:
I tried debugging deeper into the
authorize
code but it got to where it queues up the call to the native code and lost me after that. Could this be a bug or am I missing something? Thanks!The text was updated successfully, but these errors were encountered: