0

I have a legacy safari extension which I need to convert into Safari App Extension to submit into Extension Gallery. I am new to Xcode therefore, not familiar with it's build and run process. I tried looking into official documentation from developer.apple.com but it is so abstract.

  1. Why do we need to create a parent app in Xcode before creating a safari extension target?

  2. If so what parent app template should I choose? Cocoa App?

  3. Where I can find starter tutorials on Xcode?
  4. What is the submission process to Extension Gallery?
  5. How can add the extension under development to my safari through xcode for testing?
  6. I heard they need the URL for extension to approval, when we are submitting extension through developer account why to host it on URL?

Any documentation or answers to the above questions would be very helpful. Thank you.

Chanikya Mohan
  • 47
  • 6

2 Answers2

1

On 2. and 3, I had the same struggles - I wrote up a tutorial on basic style sheet injection in Safari App Extensions here: https://ulyngs.github.io/blog/posts/2018-11-02-how-to-build-safari-app-extensions/

Ulrik Lyngs
  • 98
  • 1
  • 5
0

I'm converting the legacy safari extension to safari app extension too and have some answers for your questions:

  1. Because app extension is more as functional extension then safari browser extension and could bring more features to you. And as per Apple says: safari app extension gives more communication and data exchange between Safari and your native app, docs. But I have no more ideas if you only want an extension for safari why this is only way to do extensions.
  2. Yes, you should use the Cocoa App template. If you don't need the window for your app, you can remove it simply in Main.storyboard or make app as a "service".
  3. A lot of docs from Apple I've read but understood a bit then expected. So I found some youtube channels (they are 2 or more years old but some things seems don't changed) Some vieos here and the Osx Dev Daily playlist on this channel. And of course official swift docs if you select swift for your app as PL.
  4. I haven't read about this, but think it must be submitted with your Cocoa App.
  5. First of all you should to run your app target and only after this you should run your extension target and choose "Safari" in showed window to run in. If you have no the signing at the moment so ensure to enable "Allow unsigned extensions" in Development > Allow unsigned extensions in Safari app.
  6. Don't meet this info, could you share it, pls? (sry, don't have enough knowledges)

Hope, it helps to you!

P.S. also recomend to see the converting docs, but it may be insufficient for converting :)

EDIT: it's seems to be incorrect to remove app window or change the default menus created by Cocoa App template for app submit for App Store. Some people got negative decision of app submit because of menus changes of redundant items or app have poor functionality or has not it at all. So consider to read the submit docs.

Please, share your experience when you'll have success app submit!

EDIT 2: Today I found template in Xcode 10.1 that can be used for Safari Extensions directly. It is as previous workflow (template Cocoa App + add extension target) but there is safari extension target already included enter image description here The app window and menu is simplified for developers: enter image description here

So you don't need work with your app and you can concentrate on extension only.

Community
  • 1
  • 1
seclace
  • 98
  • 7