Howdy, Trying to get notarization working using a...
# fleet
d
Howdy, Trying to get notarization working using a M1 build host and fleetdm docker image. This is the docker command I run:
docker run --env-file .env --v "{PWD} --platform linux/amd64 fleetdm/fleetctl package --type=pkg --fleet-url=<https://redacted.tld> --enroll-secret=<> --sign-identity <> --notarize --fleet-desktop
This produces the following error:
productsign: executable file not found in $PATH
. I'm sure I'm making some trivial mistake, any thoughts appreciated, I know very little about OSX notarization. 🙏
k
Hey @Daniel Lidberg. The
productsign
package used for the signing and notarization isn't present in the Docker Container. Building a signed package should be done natively rather than with Docker.
t
make sure you're building on macOS with XCode installed (includes
productsign
)
d
@Kathy Satterlee that makes a ton of sense now (I thought there was some magic sauce in the docker) thank you for clearing things up 🙂 . I'll try to build and sign the package directly instead. 🙏
Doing it native also failed, so I just did it in steps this way. 1. fleetctl (latest ver) to generate pkg 2. Signing it using
productsign ...
worked like a charm 3. however notarization with
xcrun altool
gives
Unable to generate an Apple Connect token at this time due to a general error (1611)
Any thoughts appreciated 🙏
k
What error did you get when signing with
fleetctl
natively?
t
There's some setup involved which needs app store connect creds, have you seen this? https://fleetdm.com/docs/using-fleet/fleetd#macos-signing-notarization
d
What error did you get when signing with fleetctl natively?
See screenshot, this is how I ran the fleetctl command 🙏
Copy code
AC_USERNAME=<my_devid> AC_PASSWORD=<my generated app pass> AC_TEAM_ID=<our org id> ./fleetctl package --type=pkg --fleet-url=<http://fleet.example.com|fleet.example.com> --enroll-secret=<> --sign-identity <developer id installer id> --notarize
There's some setup involved which needs app store connect creds, have you seen this? https://fleetdm.com/docs/using-fleet/fleetd#macos-signing-notarization
I have seen it and hopefully but might have missed / misread some step since I'm new to notarization in the Apple echo system. Using a build machine we have which already has the signing identities. Any thoughts appreciated on how to best debug this further 🙂
t
are you still seeing the same
productsign
error?
d
Unfortunately yes, will try and dig further next week but this week it's all about signing msi 😉