In most cases, 1Blocker works seamlessly, exchanging data with Safari with no issues. However, our app, as well as the browser, can give several types of errors if they cannot handle the data processing.
In this short overview, we will give you the steps to follow if you come across an error message or a crash. In addition, we will describe the most typical error types.
How to Report?
Some error messages contain a brief description telling you what exactly is wrong. It may help solve these issues without our assistance, but if they are too vague, feel free to contact us. We will do our best to put 1Blocker back on track!
Here's how you can contact us, report any issues or share your feedback:
- using the "Report" section available in 1Blocker Safari extension;
- using the "Send Feedback" button which you can find in the Settings tab or in 1Blocker Safari extension;
- via our email - firstname.lastname@example.org;
- via Twitter.
Please, opt for built-in report and feedback buttons, if possible. It's the fastest and most convenient way of reporting sites because such messages automatically include page URL, device and 1Blocker version.
What Information Should Be Included in a Report?
If there is an error message popping up, or the app is occasionally crashing, and you are going to report it, please, consider including the following information:
- describe as detailed as possible the steps to reproduce the issue;
- mention the buttons you've pressed, categories affected, the rules you've edited or the websites you've visited just before the problem occurred;
- feel free to attach any screenshots as they are usually helpful;
Some Common Error Messages
WKErrorDomain error message usually appears while working with custom rules, hiding web elements or syncing rules with Safari. This is not a 1Blocker message, but the browser's one. It appears when Safari cannot parse the rules properly. In most cases, it simply means that one of the custom rules contains a syntax error, so it is crucial to find out which rule triggers it.
How to troubleshoot WKErrorDomain?
We need to find the broken custom rule first, and when you are ready, you can send the screenshot or the rule itself to us, so that we will check and fix it.
Just start turning off all categories and groups of rules one by one in the "Custom" section starting from the categories containing the most recent changes. As soon as you turn off the category that contains the problematic rule, the error won't show up anymore.
This is an important intermediate result because now you know which category contains the problematic rule. It's time to go deeper. Now you need to re-enable the category and check all the rules inside it by turning them off one by one just the same way you've done with categories.
When the broken rule is detected, and the message disappears, you can either try to fix it yourself or contact us, and we will help.
If you see this message either in the app or the Visual Editor while creating a custom rule, it probably means that Safari cannot process the rule. It is worth making sure that our extensions and the category responsible for this particular rule are enabled both in 1Blocker and in Safari settings. Toggling all custom categories in the app may also work for you.
If the error persists, please, try to troubleshoot it following the steps from the paragraph about WKErrorDomain issue.
Failed to modify some records
This error might appear in rare cases. Actually, we have seen it just a couple of times. This is how the system behaves when it cannot process or store information. It is a temporary issue that usually can be fixed by reloading the application. However, it is also possible that you will need to re-install 1Blocker if the message persists.