Frontend broken - giving Google OAuth errors

[michela]

Re. f056d99 using default frontend .env settings the frontend breaks with this error on Chrome Version 133.0.6943.99 (Official Build) (64-bit)

index-8e24b991.js:40 Error: Google OAuth components must be used within GoogleOAuthProvider
    at Yxt (index-8e24b991.js:1392:34541)
    at m6t (index-8e24b991.js:1392:34786)
    at Z (GCSModal-945fd369.js:1:712)
    at wj (index-8e24b991.js:38:17030)
    at MT (index-8e24b991.js:40:3143)
    at $K (index-8e24b991.js:40:44632)
    at DK (index-8e24b991.js:40:39819)
    at que (index-8e24b991.js:40:39745)
    at cE (index-8e24b991.js:40:39596)
    at ZT (index-8e24b991.js:40:35959)

Backend is running and is serving assets fine

http://localhost:8080/assets/public-sans-700-bold-normal-39dc2fce.woff2

Frontend loads with Edge Version 133.0.3065.69 (Official build) (64-bit)

[michela]

CORRECTION same error on Edge - after clearing cache

[kartikpersistent]

Hi @michela in the frontend env remove the gcs from VITE_REACT_APP_SOURCES= variable and rebuild in the docker compose we never mentioned gcs in the VITE_REACT_APP_SOURCES

[kartikpersistent]

In the frontend example env we never mentioned gcs in VITE_REACT_APP_SOURCES
exampleenv

[michela]

I'm just using example.env as provided. I haven't added any gcs config or seen where it's getting this from.

Noting the requirement for a top level root .env file which appears to be gone in recent commits, that .env didn't have any reference to GCS or Google anything either.

[kartikpersistent]

Hi @michela to avoid the confusion we removed the example in the top level root folder for frontend specific errors refer example.env present in the frontend folder

[michela]

That was a good idea to remove top level .env but there's still an issue building from clean start with the docs. Neither Dockerfile or manual setup works in latest

[michela]

Can anyone recommend a stable tag to roll back to? Would be great to get back to being able to run this.

This project was a fantastic demonstrator but main HEAD remains broken for me following the docs.

[michela]

@jexp any suggestions on this one?

[kartikpersistent]

Hi @michela we recently tested the docker-compose on main the application is running the frontend ui Is changed we are fixing that in dev we will move to main once it completes

[redshift75]

@michela I also had this problem - I was able to get frontend working by adding gcs to

VITE_REACT_APP_SOURCES="local,gcs"

and adding VITE_GOOGLE_CLIENT_ID

[michela]

Disappointed this is closed. Surely you can engineer this to not default to requiring GCS setup (credentials, SSL) etc when the docs suggest this is optional. It's an unnecessary barrier for local usage