angular-lock doesn’t seem to be grabbing the access_token because when I use authManager.isAuthenticated() I don’t get anything back. I have another issue with my app not grabbing the session and seeing my user as logged in though. I created another user with just user/pass auth which seems to redirect just fine. So I think its an issue with using social connections in a dev environment. Should that be showing the client associated to the clientID that was used? Could that be the issue? One thing I noticed was that the “client” column of the logs shows N/A. Get involved and suggest your own topics to discuss as well. Logs show that it was a successful login but technical details shows a general error. Learn from other Arlo users like you and experts that are offering up best practices and answering some common questions. Try logging in again from the application and if the problem persists please contact the administrator. Invalid_request: You may have pressed the back button, refreshed during login, opened too many login dialogs, or there is some issue with cookies, since we couldn’t find your session. If your SPYPOINT app is encountering hanging or crashing while using. ![]() It may help to fix the ‘SPYPOINT app not working’ issue. Let’s completely delete/uninstall the SPYPOINT app and again install from the Google Play or App Store. ![]() I am developing locally so my address to my app is which is also listed as one of my allowed callback URL’s. If none of the above solutions didn’t work so far. I’m able to login via Auth0 but when it successfully logs in and redirects I get a big error message saying: I have an Angular app using the angular-lock module.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |