On Fri, Oct 3, 2025 at 3:31 PM alexander_carot--- via Interest < [email protected]> wrote:
> Hej Michael and all, > > > > thanks for the feedback in this context ! > > > > >> I just ran into similar using 6.9.3. I too moved signing out of > separate step with “--deep” enabled and into > > >>macdeployqt6 without the deep option. This enabled me to successfully > notarize > > > > After updating to Qt6.10.0 I just tried the same with **only** running > > > > *macdeployqt6 my.app <http://my.app>* > > > > and then checked it via: > > > > *codesign --verify --deep --strict --verbose=2 ./my.app <http://my.app>* > > > > leading to: > > > > *./my.app <http://my.app>: valid on disk* > > *./my.app <http://my.app>: satisfies its Designated Requirement* > > > > but then notirising it via: > > > > *xcrun notarytool submit app.zip --keychain-profile myProfile --wait* > > > > leads to: > > > > *status: Invalid* > > > > In fact I received a couple of private mails with suggestions for further > action and workarounds but is this really the way the process should be ? > > > > Best > > > > Alex > > > > > Dear Alex, Hamish correctly (as always) suggested you to add: *-hardened-runtime* to macdeployqt That could resolve your issue with notarization. Kind regards, Robert Iakobashvili ............................
_______________________________________________ Interest mailing list [email protected] https://lists.qt-project.org/listinfo/interest
