-
Notifications
You must be signed in to change notification settings - Fork 704
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot read properties of undefined (reading 'getLogger') #989
Comments
I just noticed this too. Seems to be due to a change last week in index.tsx. If I change the isAuthAAD if block to extend to line 63 (instead of stopping at 50) it seems to work without configuring AAD. I will want to do the AAD auth, but wanted to start learning it without first. |
Hi @JasonHaley that actually works. Thanks |
This solved my issues with multiple "Uncaught TypeError" appearing on start. Thanks! |
thanks~ |
Thanks @JasonHaley that worked |
Fixed with #994 |
Describe the bug
The webapp in macos has issues running,
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The following error appears in the browser
Uncaught runtime errors:
ERROR
Cannot read properties of undefined (reading 'getLogger')
TypeError: Cannot read properties of undefined (reading 'getLogger')
at http://localhost:3000/static/js/bundle.js:203651:21
at mountMemo (http://localhost:3000/static/js/bundle.js:152517:23)
at Object.useMemo (http://localhost:3000/static/js/bundle.js:152902:20)
at useMemo (http://localhost:3000/static/js/bundle.js:168700:25)
at MsalProvider (http://localhost:3000/static/js/bundle.js:203650:64)
at renderWithHooks (http://localhost:3000/static/js/bundle.js:151745:22)
at mountIndeterminateComponent (http://localhost:3000/static/js/bundle.js:155029:17)
at beginWork (http://localhost:3000/static/js/bundle.js:156325:20)
at HTMLUnknownElement.callCallback (http://localhost:3000/static/js/bundle.js:141341:18)
at Object.invokeGuardedCallbackDev (http://localhost:3000/static/js/bundle.js:141385:20)
Screenshots
Platform
The text was updated successfully, but these errors were encountered: