Sometimes I get ReferenceError in my sentry with this instantSearchSDKJSBridgeClearHighlight. Google says nothing.
All I found is and that may be related to my issue.

I got 53 issues from 5 different users and all of them Edge Mobile on iphone. Maybe someone knows what this thing is (or know method how to know)?

Edit: I also found this issue using github search. Same issue as mine and created by bot

Sometimes I get ReferenceError in my sentry with this instantSearchSDKJSBridgeClearHighlight. Google says nothing.
All I found is https://github.com/algolia/instantsearch-android and https://github.com/algolia/instantsearch-ios that may be related to my issue.

I got 53 issues from 5 different users and all of them Edge Mobile on iphone. Maybe someone knows what this thing is (or know method how to know)?

Edit: I also found this issue using github search. Same issue as mine and created by bot

• javascript
• ios
• microsoft-edge
• sentry

• 3 Started seeing the same thing in our Sentry logs. I sort of assumed it has to do with a browser extension? – Ray Suelzer Commented Sep 20, 2021 at 23:41
• 1 You can also try to send feedback to the relevant team. Click the three dot icons (...) at the bottom of the browser, select the send feedback option, and edit the content to send. – Xudong Peng Commented Sep 22, 2021 at 7:20
• @XudongPeng Sure, thank you. I'll install it and report error – zerdox Commented Sep 22, 2021 at 19:28
• So only guys from microsoft know what is this... Also I got no success getting answer from them about this issue – zerdox Commented Oct 10, 2021 at 17:20

1 Answer 1

This is a bug in the Bing Instant Search feature in Edge on iOS; the feature tries to call a function that no longer exists. Thanks for the bug; I've passed it along to the feature owners.

The basic idea is that for Edge on iOS the actual web engine is not our normal one (Blink); it is instead Safari's WkWebView.

In order to implement features like Bing's instant search, we have to inject JavaScript into the pages we load. Then our outer browser calls those JavaScript functions we injected.

Here, someone goofed and got rid of (or renamed) the injected JavaScript function, but failed to remove/update the browser code that tries to call that injected JavaScript.

So users who are watching the browser's error logs see an error message saying "Hey, there's no such function."

This is normally harmless, but if you have "Sentry" code that watches for error messages and complains about them to the website developers, it starts complaining about this error message we're causing.