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?
Desmond van der Meer
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
From
Delft, Nederland
Post
Replies
Boosts
Views
Activity
Now that provisioning has been added to the App Store Connect API I was wondering if support for enterprise developer accounts will also be added. As of yet there is no way to generate API keys for enterprise accounts.