Hi - we have a quick #urgent question to isolate an issue that we are experiencing on a project due to go live next week. We facing a few warnings and wanted to ask if anything changed in the library from yesterday (07/06/2024 -DD/MM/YYYY) to today?
Hi there! We did push some updates to our engine this morning. Let’s continue troubleshooting together in our existing email thread with support@8thwall.com.
We are seeing the same issues on a currently live project rendering the project unusable which is causing huge problems for us. I have emailed support already so please can someone get back to me with solutions on this ASAP.
Also why would you push an update like this live on a Friday vs waiting till Monday? It seems complete madness & is really unacceptable
Hi @John_Macbeth - I’m sorry that you experienced an issue related to this engine update. To resolve the immediate impact I can revert your project to the previous engine version, 24.1.10.2165 while we investigate this issue.
Can you please share the project name with me (either here or via email)?
Thanks Joel, project is 8th Wall
Will that be possible to revert today?
@John_Macbeth - The project should be frozen on engine version: 24.1.10.2165
Hi @Joel @Evan!
Can you please revert our version to 24.1.10.2165, we too are totally unable to start the project, with the error XR8 is undefined. This is really urgent, we have a demo coming up in 30 mins. We have mailed the same please take urgent action.
Hi @Pranav_Yellayi, we have rolled back the engine version for the project specified in your team’s email to support@8thwall.com
Hey! So I still can’t see my engine version back to 24.1.10.2165
Am I supposed to something from my side as well?
Does your device have a dev token? If so, visit https://apps.8thwall.com and click “remove dev token” - then view the public URL of your project and I’d expect to see the frozen engine version in console logs
I tried doing that as well, but no luck. It shows the same version as above.
Anyway, the project is locally hosted and deployed on a public url, I don’t understand how removing the dev token of my device helps with the public URL
And if this is not working then provide an alternative solution for the error above, we already have taken a big setback with the client, and can’t afford to delay more.
TIA
So i dug into the issue, and seems like the aframe version is not compatible with the new engine
i am using aframe : 1.5.0 aframe-extras: 7.4.0 and three: 0.160.0
I tried aframe 1.3.0 which gave some different errors.
The same errors are replicated in your own examples(placeground)
Please see if there in lies the problem.
Thank you for your notes, I have passed these along to our engineering team.
Hi @Evan
Can you please revert our version to 24.1.10.2165? I have many issue (with model flickering for example on face tracking) I did not get this issue before. another project is reloading 1-2 times before load normally
Hey Evan!
Is there any update regarding the error above. We are building another project with a-frame and still am having the same issue.
If not fixed yet, please revert the engine for the this project to 24.1.10.2165 as well.
This issue needs to be resolved asap, because we can’t be asking you to revert the engine version back to 24 for every project on 8th wall.
This issue should be fixed on all versions of A-Frame with the latest engine version (27.0.2.427s). Please let us know if you uncover any other issues!
This topic was automatically closed 4 days after the last reply. New replies are no longer allowed.