Notarisation warning safariextz file is present inside app bundle

Question

swethach OP

Created Jan ’20

Replies 3

Boosts 0

Participants 2

Hi,

Our app has safari legacy extension(***.safarietz), which is packaged inside bundle at custom directory under resources(***.app/Contents/Resources/Components/***.safariextz), when trying notarise the app bundle, there is a warning that ***.safariextz is not a valid product / component package.

Couple of questions:

How can we resolve this warning.( To support older version of safari we need this extension)

Will this warning become error after Feb 3rd 2020, when all submitted software must meet the original notarization prerequisites?

Boost

Answer 1

DTS Engineer OP

Apple

Jan ’20

Is there a reason you used

Contents/Resources/Components/

? In general, you shouldn’t nest code inside

Contents/Resources/

. A better place for this would be

Contents/PlugIns/

.

Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

0

Answer 2

swethach OP

Jan ’20

This is a legacy code and I don't think there is any specific reason for using /Resources/Components/

We tried placing the legacy extension in Content/PlugIns, but the warning is still not resolved. (***.safariextz is not a valid product / component package.)

Any other inputs that we could try.

0

Answer 3

DTS Engineer OP

Apple

Jan ’20

We tried placing the legacy extension in
Content/PlugIns
, but the warning is still not resolved.

Bummer. That’s the last of my simple suggestions. At this point I’m going to recommend that you open a DTS tech support incident so that I can allocate time to look into this in depth.

Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

0