[Bug]: Facebook appending #_=_ to redirected url

[pchrominski]

Version

20.0.2

Please provide a link to a minimal reproduction of the bug

No response

Please provide the exception or error you saw

No action after facebook login. Page stuck in landing url.
Url after redirect from facebook authorize url is something like:

https://example.com/auth-callback?state=...&iss=...&code=...#_=_

More info about this facebook behavior: https://stackoverflow.com/a/41917323/3791820

Also I found question on SO with the same problem: https://stackoverflow.com/questions/79310174/angular-auth-oidc-client-with-facebook

Steps to reproduce the behavior

A clear and concise description of what you expected to happen.

I think in UrlService you should compare redirectUrl and  currentUrl without QueryParams AND fragment

Additional context

No response

[Lexa-tech]

Hello!
I think I have the same issue when I try to use implicit Flow , there is a fragment #access_token in the redirectUrl, so when the service compare urls without queryParams, the fragment is not removed , and the urls don't match.
So I agree, we should compare redirectUrl and currentUrl without QueryParams AND fragment

[NicolasR]

Hello
I have this issue since i migrated from v17 to v20.