-
Notifications
You must be signed in to change notification settings - Fork 1k
React-router (hash routing) is not working directly after login #8845
Copy link
Copy link
Closed
Labels
area:spfxCategory: SharePoint Framework (not extensions related)Category: SharePoint Framework (not extensions related)type:archive-old-issueIssues which are closed as tool old for active workIssues which are closed as tool old for active worktype:bug-suspectedSuspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs.Suspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs.
Metadata
Metadata
Assignees
Labels
area:spfxCategory: SharePoint Framework (not extensions related)Category: SharePoint Framework (not extensions related)type:archive-old-issueIssues which are closed as tool old for active workIssues which are closed as tool old for active worktype:bug-suspectedSuspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs.Suspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Developer environment
None
What browser(s) / client(s) have you tested
Additional environment details
Describe the bug / error
I have the same issue, how is it resolved and in what version?
Steps to reproduce
Open a browser where you are already logged-in to SharePoint Online, everything is working as expected.
If you are not already logged-in to SharePoint Online, the call to Page.aspx#/my/route/1 redirects you to login.microsoftonline.com. After logging in, you are redirected back to Page.aspx but without the hash route.
Expected behavior
I have an SPFx 1.13.0 web part which uses react hash routing. So you can open the page with a specific route to navigate to a specific part within the web part. E.g. Page.aspx#/my/route/1
It shoud be possible to open the link directly, for example from an email.