You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using both Laravel Socialite and Laravel Fortify to authenticate my users.
Registration in Laravel Fortify has integrated perfectly with this Package, but Login has (if I can call it) a loop hole.
When I attempt to Login a user whose Mobile is not Verified, the browser returns a "too many redirects" error.
The same case happens to Laravel Socialite. Socialite does not provide the system with a user's mobile number, I have to fetch it directly from the user using a form. Adding a form that fetches this info and sending it to the route "mobile.verify" does not do anything. It directs to Home and then returns the 'too many redirects" error.
Perhaps:
If the package could have a fall back route for when a user is not verified it would fix the too many redirects issue.
If the package could point out a dedicated view for which users can manually enter their mobile numbers and send it to a specific controller, one that Validates then triggers the event(new Registered($user)); Event, it would work for even users logged in via Laravel Socialite.
Have encountered an issue related to this.
I am using both Laravel Socialite and Laravel Fortify to authenticate my users.
Registration in Laravel Fortify has integrated perfectly with this Package, but Login has (if I can call it) a loop hole.
When I attempt to Login a user whose Mobile is not Verified, the browser returns a "too many redirects" error.
The same case happens to Laravel Socialite. Socialite does not provide the system with a user's mobile number, I have to fetch it directly from the user using a form. Adding a form that fetches this info and sending it to the route "mobile.verify" does not do anything. It directs to Home and then returns the 'too many redirects" error.
Perhaps:
Kindly, let me know your thoughts.
Originally posted by @thedanmwangi in #27 (comment)
The text was updated successfully, but these errors were encountered: