Testing errors

🧑‍💻 Technical Support
, ,
1

Is there any way to test errors and error screens? We’re getting ready to launch a site for a client and there has been a few rare cases where the cameraSelectionWorldTrackingError comes up. We’re wanting to replace the screen with a custom one but although I’ve added CSS to do so, the RARE case we’re able to replicate it (abundant refreshes on an overheating iPhone), it isn’t working. Is there a way to force errors for testing / design purposes? Also… the only reason we found the error content was from the github repo (web/xrextras/src/loadingmodule/loading-module.html at master · 8thwall/web · GitHub), it isn’t in the documentation that we’ve seen.

2

Have you tried throwing errors?

3

This is more specifically the error screens that are built-into 8th wall. Your error pages that occur outside of the normal operation of an application.
These errors:

I’d like to find the best way to optimally test the different screens reliably since although we have created CSS rules to override your designs, they don’t seem to be applying.

4

I think you’re referring to the runtime error module - try overriding the CSS of these elements instead.

You can simulate a runtime error by throwing an error from a camera pipeline module:

const onxrloaded = () => {
  XR8.addCameraPipelineModule({
    name: 'throw-error',
    onAttach: () => {
      throw new Error()
    },
  })
}

window.XR8 ? onxrloaded() : window.addEventListener('xrloaded', onxrloaded)
1 Like
5

This helps. And yes, it seems you’re right, that is the one we were having. Thank you.

6

This topic was automatically closed 4 days after the last reply. New replies are no longer allowed.