Daniel Lidberg
08/09/2023, 9:24 AMdocker 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. 🙏Kathy Satterlee
08/09/2023, 2:58 PMproductsign 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.Tim Lee
08/09/2023, 5:51 PMproductsign)Daniel Lidberg
08/10/2023, 9:05 AMDaniel Lidberg
08/10/2023, 10:39 AMproductsign ... 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 🙏Kathy Satterlee
08/10/2023, 4:29 PMfleetctl natively?Tim Lee
08/10/2023, 6:34 PMDaniel Lidberg
08/14/2023, 8:04 AMWhat error did you get when signing with fleetctl natively?See screenshot, this is how I ran the fleetctl command 🙏
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> --notarizeDaniel Lidberg
08/14/2023, 8:06 AMThere's some setup involved which needs app store connect creds, have you seen this? https://fleetdm.com/docs/using-fleet/fleetd#macos-signing-notarizationI 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 🙂
Tim Lee
08/22/2023, 3:52 PMproductsign error?Daniel Lidberg
08/28/2023, 1:13 PM