Posts

Post marked as solved
1 Replies
684 Views
We currently have a working Safari App Extension that was converted from a Chrome extension. We want to migrate to a Safari Web Extension so that we can have a unified code base. My question is with packaging the extension in the container app. Ideally we'd like to package both the old App Extension and the new Web Extension in the same container app, so that we can support both Safari 13 and 14. However, when users are using Safari 14 we'd like them to see only the Web Extension and not the old App Extension. Is there a way to do this?
Posted Last updated
.