Cannot get past "Confirm Login Account" page on Eduroam Wifi Network

[lucasisnotcool]

Describe the bug
After opening catcher, setting the session, and signing in via Github, the catcher screen is stuck at "Confirm Login Account" page. After a while, an error message is displayed (see screenshot).

The CATCHer repo was also not created. Already retried in Safari incognito, Chrome, and with site data cleared.

Also tried: Clear site data + Revoke GitHub authentication token + redo steps 1-3 on Safari
Outcome: Re-authenticated, token was recreated, but still stuck on same page.

Logs from Safari:

====== New CATcher v3.6.0 Session Log ======
3/28/2025, 2:56:16 PM
AppComponent: AppConfig,[object Object]
AppComponent: Mode web
SessionSelectionComponent: Selected Settings Repo: nus-cs2103-AY2425S2/catcher-smoke-test
AuthService: Starting authentication
AuthService: Redirecting for Github authentication

====== New CATcher v3.6.0 Session Log ======
3/28/2025, 2:56:32 PM
AppComponent: AppConfig,[object Object]
AppComponent: Mode web
AuthComponent: Obtained authorisation code from Github
AuthComponent: Retrieving access token from Github
AuthComponent: Error in data fetched from access token URL: TypeError: Load failed
ErrorHandlingService: TypeError: Load failed
ErrorHandlingService: Error: Uncaught (in promise): TypeError: undefined is not an object (evaluating 'e.split')
cleanStack@https://catcher-org.github.io/CATcher/main.d044ed035976a6a5.js:196:432794
handleError@https://catcher-org.github.io/CATcher/main.d044ed035976a6a5.js:196:432607
@https://catcher-org.github.io/CATcher/main.d044ed035976a6a5.js:196:499083
onInvoke@https://catcher-org.github.io/CATcher/main.d044ed035976a6a5.js:1:195476
run@https://catcher-org.github.io/CATcher/polyfills.699b5bbb59238bcc.js:1:2641
@https://catcher-org.github.io/CATcher/polyfills.699b5bbb59238bcc.js:1:17482
onInvokeTask@https://catcher-org.github.io/CATcher/main.d044ed035976a6a5.js:1:195296
runTask@https://catcher-org.github.io/CATcher/polyfills.699b5bbb59238bcc.js:1:3263
_@https://catcher-org.github.io/CATcher/polyfills.699b5bbb59238bcc.js:1:9890

Logs from Chrome:

====== New CATcher v3.6.0 Session Log ======
3/28/2025, 3:17:19 PM
AppComponent: AppConfig,[object Object]
AppComponent: Mode web
SessionSelectionComponent: Selected Settings Repo: nus-cs2103-AY2425S2/catcher-smoke-test
AuthService: Starting authentication
AuthService: Redirecting for Github authentication

====== New CATcher v3.6.0 Session Log ======
3/28/2025, 3:17:26 PM
AppComponent: AppConfig,[object Object]
AppComponent: Mode web
AuthComponent: Obtained authorisation code from Github
AuthComponent: Retrieving access token from Github

====== New CATcher v3.6.0 Session Log ======
3/28/2025, 3:20:16 PM
AppComponent: AppConfig,[object Object]
AppComponent: Mode web
AuthComponent: Error in data fetched from access token URL: TypeError: Failed to fetch
ErrorHandlingService: TypeError: Failed to fetch

To Reproduce
Follow instructions as prescribed by CATCHER smoke test until step 3

Expected behavior
Be able to log in

Screenshots
Safari:

Chrome:

Github Settings:

Desktop (please complete the following information):

• OS: MacOS
• Browser Safari and Chrome
• Version Safari 18.1, Chrome 134.0.6998.166 (Official Build) (arm64)

Additional context
Both safari and chrome were set to allow both popups and third party cookies

[lucasisnotcool]

Issue was resolved after switching to NUS_STU network, but it is still a major issue that wifi networks can affect functionality of the web app. If this is an intended feature, it should have been included in the instructions provided by the user guide.

[damithc]

@aekyr Thanks for reporting this.
Some of the earlier semesters, we had 1-2 students facing this kind of issue that got resolved by switching the network. My guess is it is due a network protection mechanism detecting a false positive and blocking the access.
We'll wait to see if the problem affects more students. You can also try again another day to see if the problem recurs.
In the meantime, the CATcher team will look through the error message you supplied to identify the exact failure point.