Troubleshooting
In this section you will find common issues that you may face when setting up your Beans iD embedded
landing page. Alongside this, you will also find instructions on how to use the debugging tool
contained within our <script> to help with diagnosing and fixing issues.
Debugging Tool
Our <script> is able to diagnose common issues that may occur when implementing our script. For
this functionality to work the <script> must be loaded into the page.
Once loaded into the page, the <script> will try to embed your landing page, but if it is unable
to do so it will attempt log an error into your browser console. This error will inform you of what
went wrong, and will provide a link to one of the issues listed below to help you get the issues
resolved.
To access these error messages simply open the developer console in your browser using ctrl +
shift + j on Windows, or cmd + shift + j on Mac. If the <script> was able to identify
any issues you will be able to find a message similar to the one below, detailing the issue and
linking to our documentation which will detail a fix.
Common Issues
Below are listed some common issues you may face when implementing your embedded landing page. Some of these issues will be automatically detected by the debugging tool referenced above which can help to make it easier to understand which issue you may be facing.
- Missing Slug
- Invalid Slug
- Missing Territory
- Invalid Territory
- Invalid Language
- Content Security Policy errors / "refused to connect"
Legacy Issues
We still support a legacy implementation of the script that has much more limited error reporting. The two errors that can be raised by the legacy implementation are listed below.
If you are seeing legacy issues then you are using an outdated implementation.
We strongly recommend upgrading to our most current implementation documented here.