This is from one of our partner dev teams, they’re building a game with Niantic SDK for Unity & VPS, and they also have other client work using 8th Wall. They messaged me about a surprise they had on one of their 8th Wall projects.
Can you look into this please?
Here are the notes:
We’ve had a weird occurrence where a live and deployed 8th Wall experience has suddenly stopped working. Are you able to shed any light?
On the 8th January 2025 we deployed an experience duplicated from a previous experience we had created. On deploy, the app was working fine however it has since stopped working in the past couple of days.
Were there any changes made to 8th Wall in the last week that would have caused the app to stop working? There hasn’t been any changes to the deployed version of the code since it was deployed 8 days ago.
The original experience was based on the “React App” project form the 8th Wall library, however we had to use external versions of react (18.3.1), react-dom (18.3.1) and react-router-dom (6.27.0) as the included versions were quite old.
Since it stopped working, we have tried to use the included 8thwall:package versions of react and react-dom (both 18.3.1), however the included version of react-router-dom is too old (the maximum seems to be v5). Using a newer version of react-router-dom from unpkg.com does not seem to work.
It sounds like there may be a version mismatch or a dependency conflict with React and React Router. While 8th Wall rarely introduces breaking changes without notice, recent updates in the libraries you’re pulling from (e.g. unpkg) can cause conflicts. Check your browser console for error messages—they often pinpoint missing or mismatched dependencies.
Because the included 8th Wall React libraries are fixed to certain versions, using a newer react-router-dom from an external source can break compatibility if the React version is mismatched. Ensure that your React, React DOM, and React Router DOM versions align. Also confirm you’re using the correct import syntax for react-router-dom v6 (e.g. <Routes> vs. <Switch>).
If possible, rebuild or bundle all React libraries together (React, React DOM, and React Router DOM) rather than mixing versions from the 8th Wall package with unpkg. This usually provides more consistent results.
At this point you’ll still see a white screen and that’s because your views and router are setup for version 6 syntax whereas the version we need to use is version 5. You’ll want to go through each of your components / scenes that use the router and change them to be version 5 syntax.
If you run into any trouble with this let me know!
Thank you!