Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The authorization flow opens the linkedin app and never returns to the callback url (IPHONE) #66

Closed
Lastimoso opened this issue Sep 15, 2021 · 1 comment

Comments

@Lastimoso
Copy link

Lastimoso commented Sep 15, 2021

Problem
When trying to sign_up/login from an Iphone it opens the linkedin app and do nothing else. Same thing using Chrome and Safari. On the contrary, it works perfectly:

  • When on desktop
  • If the linkedin app is not installed in the iphone
  • If we use an incognito browser in the iphone (either Safari or Chrome)

Context

  • In my logs I see Started POST "/users/auth/linkedin" for IP. DEBUG -- omniauth: (linkedin) Request phase initiated. and nothing else.
  • I've disabled Turbo and even javascript but the issue remains.
  • Same thing is happening in development, staging and production.
  • I tried debugging in safari to see if I saw a clue in network or even console logs, but nothing. Any ideas?
  • and Ruby 3.0.1

More context

  • I tried using rails redirection to the url https://www.linkedin.com/oauth/v2/authorization?all_the_needed parameters and works as expected.
  • The Gem is actually creating the Rack response correctly.
  • I tried changing the status of the rack response to 303 or 302 but the issue remains.

Stack

  • Rails (6.1.3.2)
  • Ruby (3.0.1)
  • Rack (2.2.3)
  • omniauth (2.0.4)
  • oauth2 (1.4.7)
  • omniauth-linkedin-oauth2 (1.0.0)
  • Devise (4.8.0)

Any Idea? I looked very hard trying to find people reporting this issue but without any luck. I start to think that may be related to my ruby or rails version but haven't check. Both apps use same stack...

@Lastimoso
Copy link
Author

Lastimoso commented Sep 20, 2021

Apparently, Linkedin already confirmed this is an issue on their side. I spent several days debugging this! 😱

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant