Almost every test build I need to re-allow & enable my extension

Question

jw732 OP

Created Dec ’20

Replies 3

Boosts 0

Views 1.1k

Participants 3

Almost every single test build I run with my extension, I need to:

open extension preferences
click the checkbox for my extension
double click my apple watch to approve
click 'turn on' button after approved

To be clear, I am told my extension interferes with clicking - that is why I need to go through two steps to re-allow the extension and I theorize that is also why my extension becomes disabled after every test run.

This isn't ideal since I tend to build/test my extension quite a bit as I am developing. This adds a lot of time to that process.

Is there anyway, as the developer, to stop getting these prompts and just keep the extension enabled and allowed during development?

Thank you.

Answered by jw732 in 656451022

Sorry for the late replies. This is not about web extensions.

I believe I figured out why this was happening. Since I have the current (non-development) build of my extension on my development machine, I always disable the extension before testing. When I test new builds, I test in Safari and a fresh instance of Safari is initialized, which has my non-development extension disabled.

That means every time I re-build, I have to re-enable the extension. If I do not disable the extension before building development versions, I seem not to encounter this.

It all sounds rather long winded and confusing, but since realizing this, I haven't encountered the issue, so far.

Boost

Answer 1

climb OP

Dec ’20

Is is this about safari extensions?

It probably depends on the access you request in manifest.json (if it's a web extension). If you narrow the scope then there won't be any approval requests.

0

Answer 2

Frameworks Engineer OP

Apple

Dec ’20

You shouldn't need to re-enable the extension each build, just rebuilding in Xcode will reload an enabled extension in Safari.

To be clear, your extension isn't interfering with clicking, some other software on your Mac is. Sometimes this can be a screen recorder, or some other third-party application that has invisible windows over the whole screen.

0

Answer 3

jw732 OP

Jan ’21

Accepted Answer

Sorry for the late replies. This is not about web extensions.

I believe I figured out why this was happening. Since I have the current (non-development) build of my extension on my development machine, I always disable the extension before testing. When I test new builds, I test in Safari and a fresh instance of Safari is initialized, which has my non-development extension disabled.

That means every time I re-build, I have to re-enable the extension. If I do not disable the extension before building development versions, I seem not to encounter this.

It all sounds rather long winded and confusing, but since realizing this, I haven't encountered the issue, so far.

0