We are experiencing an unusual issue with the parse hash functionality in our angular.js apps in IE 11 and Edge. After being redirected back from the Auth0 hosted login page on successful login we are calling the parseHash function angularAuth0.parseHash({ hash: window.location.hash }, function (e…

Issue seems to be related to the way Angular.js routing was rewriting the url in Edge and IE causing the parseHash function to be called twice. Updating the location provider seems to have fixed the issue. $locationProvider.html5Mode({ enabled: true, requireBase: false, …

Parse Hash not working for Angular.js in IE 11 & Edge

Get Help

system Closed August 10, 2019, 11:35am 4

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Hash get's lost on Safari/Webkit browsers Get Help angular , custom-login , hash , browser , webkit	9	14523	October 23, 2018
Angular parseHash returns undefined Get Help angular , angular-2 , parsehash	2	5004	August 27, 2019
parseHash doesn't seem to work with non-empty hash prefixes Get Help angular , parsehash	2	4040	March 2, 2018
Parsehash CORS blocked after logging in Get Help	2	3458	August 26, 2019
Invalid hash after Angular 6 update Get Help	4	4125	June 12, 2019

Parse Hash not working for Angular.js in IE 11 & Edge

Related topics