'arrow_back_ios' is shown instead of a button which leads me back to the previous page

[vigneshsankariyer1234567890]

Describe the bug
This seems like a UI bug, where moments after I click on the default session to login to, I see a view where there is some text rendered called 'arrow_back_ios'. It seems like it could be a CSS classname that is being rendered, but this warrants further investigation. I think that a button should instead be rendered, leading the user back to the previous page, which was the Login page.

To Reproduce
Steps to reproduce the behavior:

1. Start the app from the master branch.
2. Attempt to log in.
3. When logging in with your GitHub account, it momentarily displays a view as shown below where the client is awaiting for the response from GitHub. At the current moment, the CORS issue as linked by CORS issue on heroku when attempting to log in #1070 is still not allowing me to complete my authentication and authorisation to use the default catcher account.

Expected behavior
A normal 'Back' button should be rendered instead.

Desktop (please complete the following information):

• OS: macOS Monterey
• Browser: chrome

Additional context
Add any other context about the problem here.

[kkangs0226]

Thank you for reporting this issue! However I am unable to reproduce this bug, I have a normal arrow being rendered. Are other developers are experiencing a similar problem?

[vigneshsankariyer1234567890]

@kkangs0226 Coming back to this issue again. I face this issue regularly when recompiling the project frequently. Upon inspection, 'arrow_back_ios' is the name of a mat-icon that is used. I have a feeling this issue is caused when there are outgoing requests to get the relevant HTML for the icon itself. However, the display of the icon title is often momentary and fleeting.

[cheehongw]

Since the icon is fetched from the google api font library, I was able to reproduce this by blocking fonts.googleapis.com

@vigneshsankariyer1234567890 do you still face this problem? I think this might be a one-off issue with network latency on your side. If not we can close this.