Posts

Post not yet marked as solved
3 Replies
1.1k Views
In Safari 13 (both in macOS Catalina and Safari Technology Preview builds on Mojave), I'm encountering a major issue when having my Safari App Extension communicate with Safari. For example - my app's toolbar popover has an option to enable or disable certain functionality for the extension. In Safari 12.1, I am able to use page?.dispatchMessageToScript to send messages from my App Extension to the injected script to immediately reflect the user's change in the foreground tab. This also works in Safari 13, but only at first launch. After Safari has been running for some time, all further attempts to use this functionality fail silently. The only indication of the error is found by checking the console, where I'm seeing:Error connecting back to host app: NSCocoaErrorDomain, code: 4099I actually filed a Radar/feedback about this several months back, but have not heard any updates and have not seen this issue improve since June. I see this was also mentioned in a previous thread, but there was no further response. Is anyone else seeing this, or does anyone at Apple have any clarification regarding what's happening? This significantly impacts some useful features of my app/extension (such as being able to make changes in the core app and have them quickly reflected in Safari), so I'd really like to see this addressed before Safari 13 ships.
Posted
by mfreuden.
Last updated
.