I’m currently working on a project (editor) that I cloned from the VPS Scavenger Hunt template available at: Niantic VPS Scavenger Hunt | 8th Wall | 8th Wall. It was working properly earlier, but now it’s no longer functioning as expected.
The VPS mesh that was scanning and working previously is no longer appearing or functioning.
Even the staging version (which was working earlier) is now not working either, so I suspect there may have been a change on the backend or with dependencies that’s affecting the functionality.
Could you please look into this or let me know if there have been any recent updates that might have impacted the project?
We haven’t made any changes that would affect this as far as I’m aware and I’m not able to reproduce this issue. Are you seeing any errors in the console? Is the location never localizing without any messages etc?
I also noticed something:
When I log the “xrprojectwayspotscanning” event details, I’m getting an empty array in the console.
Please correct me if I’m wrong, but I think the scenes are not loading properly, and as a result, the “xrprojectwayspotfound” event is not being triggered.
Hey @GeorgeButler after hours of debugging, I finally solved the issue by removing and re-adding all the wayspots in the project, and it started working correctly.
Hi ,
we have exact the same problem as @Equanimous_Technolog, so far everything has worked fine but now the event “xrprojectwayspotfound” is no longer called, the error message in the console concerns slam.js. No scenes/GLB are displayed, we have also tried to delete the waypoints in the Map Explorer as recommended and reassign them to the project, but unfortunately the problem persists.
We would be glad for a quick help as our project has to go online soon, thanks!
slam.js:1 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'length')
at I.encodeUtf8 (slam.js:1:78453)
at I.set (slam.js:1:63525)
at I. _ [as setText] (slam.js:1:60261)
at yI.setSpaceId (slam.js:1:5372615)
at slam.js:18:54490
at Array.forEach (<anonymous>)
at slam.js:18:54127
@GeorgeButler we have also noticed that the waypoint is geolocated correctly and also inserted as into the HTML. The event “xrprojectwayspotscanning” is called, but no result is returned so that “xrprojectwayspotfound” is never reached.