Troubleshooting

Redirect URLs

When using redirect or deviceRedirect, the URL must be accessible from the scanning device. The following will not work:

• localhost
• 127.0.0.1
• 0.0.0.0

Use a network IP address or domain name accessible to the scanning device.

Callback Naming

When using DeviceAssure.qr(), your callback can have any name — the library internally wires it to the global _deviceAssureResultReceived function.

However, if you use the raw snippet directly (without the library wrapper), you must define the callback with the exact name _deviceAssureResultReceived:

<script src="https://qr-code.deviceatlas.com/v2/api/snippet.js?dv-licenceKey=<LICENCE_KEY>"></script>
<script>
  function _deviceAssureResultReceived(result) {
    console.log('Result:', result);
  }
</script>

Content Security Policy (CSP)

If your site uses a Content Security Policy, the following domains must be allowed for QR code functionality:

Content-Security-Policy: frame-src 'self' https://qr-code.deviceatlas.com;
                         script-src 'self' https://cdn.devicevalidation.io https://qr-code.deviceatlas.com;
                         connect-src 'self' https://api1.devicevalidation.io https://api2.devicevalidation.io https://api3.devicevalidation.io;

See Also

• Quick Start Guide - Getting started with QR code verification
• Examples - Implementation examples
• Configuration Options - All available parameters