Post not yet marked as solved
3
Views
What are the valid options for the platform parameter for vtool.
Found arm64 is a valid value but x86_64 or x64 are not.
Post not yet marked as solved
861
Views
"App Store Connect Operation Error
Failed retreiving request UUID for upload"
I don't understand why I get this error or what to do about it. I googled and there's lots of hits but that was over a year ago, nothing recent. I just recently upgraded to 11.3.1.
Oh, Apple needs to run their error messages through a spell checker. *retrieving*.
Post marked as solved
352
Views
Hello,
I ran into a big problem for which I don't know how to proceed. Every developer can create up to five Developer ID certificates. Those certificates are used if you want to release your app outside the Mac App Store.
I have an app on the Mac App Store that also offers a helper application, which is downloadable on my homepage.
I have created a new version of this helper application and wanted to send it to the notarization service of Apple.
Xcode displayed an error that I do not have a valid Devloper ID certificate (because the private key is missing) and I can not create a new one because I already created five certificates.
I can download the certificates without problem, but I can not get the private key. At least one developer certificate was created on my machine, but It does not seem to work.
Because I assumed that there is no way of getting these certificates back (always create backups!), I contacted Apple to see if they are willing to revoke any old certificates so I can create a new one (I know that at least the first two certificates are not being used, so they could be revoked, but Apple does not revoke old certificates).
Right now, Apple decides whether they grant me an exception to create additional certificates.
Let's assume Apple declines this request...what can I do? Can I create a second developer account? I don't care about the 99€, but it does not seem that this is allowed.
Big Sur will be released tomorrow and I really need to sign this app.
And yes, I know that I should keep a backup copy of my private keys in the future ;)
Is there anything I can do (especially if Apple declines the request)?
Any help is highly appreciated.
Kind Regards,
Sascha
Post not yet marked as solved
13
Views
I am notarizing SEPRemote.pkg, built following instructions here: https://knowledge.broadcom.com/external/article/181587
Notarization succeeds, but there are two warnings in the log:
{
"severity": "warning",
"code": null,
"path": "SEPRemote.pkg/SEPRemote.pkg Contents/Payload/private/tmp/Norton for Mac SKU.mpkg/SEPEG_SKU.UniversalESD.pkg Contents/Payload/Library/Application Support/Symantec/Silo/MES/SymUIAgent/Symantec.app/Contents/Resources/Norton.app",
"message": "Unable to notarize SEPRemote.pkg/SEPRemote.pkg Contents/Payload/private/tmp/Norton for Mac SKU.mpkg/SEPEG_SKU.UniversalESD.pkg Contents/Payload/Library/Application Support/Symantec/Silo/MES/SymUIAgent/Symantec.app/Contents/Resources/Norton.app",
"docUrl": null,
"architecture": null
}
and
{
"severity": "warning",
"code": null,
"path": SEPRemote.pkg/SEPRemote.pkg Contents/Payload/private/tmp/Norton for Mac SKU.mpkg/SEPEG_SKU.UniversalESD.pkg Contents/Payload/Applications/Symantec Endpoint Protection.app/Contents/Resources/ApplicationNorton.app",
"message": "Unable to notarize SEPRemote.pkg/SEPRemote.pkg Contents/Payload/private/tmp/Norton for Mac SKU.mpkg/SEPEG_SKU.UniversalESD.pkg Contents/Payload/Applications/Symantec Endpoint Protection.app/Contents/Resources/ApplicationNorton.app",
"docUrl": null,
"architecture": null
}
What are the consequences of these warnings? Will they cause problems with SEPRemote.pkg even though it reports notarization is successful?
Post not yet marked as solved
50
Views
Hello.
We have an app bundle that we package into a .pkg file. We are currently getting an error when notarizing the .pkg artifact. But running all the suggested tool vs the built bundle/package results in validating the bundle/package. We don't know what notarization service is rejecting the pkg.
The notarization failure:
Notarization Invalid
{
"logFormatVersion": 1,
"jobId": "b26ec329-409e-4a21-88f0-6f924795a6db",
"status": "Invalid",
"statusSummary": "Archive contains critical validation errors",
"statusCode": 4000,
"archiveFilename": "MY-APP.pkg",
"uploadDate": "2021-07-19T17:39:59Z",
"sha256": "019c0409eab63e68cfe6323sd2e33715f07c731d5b4192254277ed62db1b6e97d",
"ticketContents": null,
"issues": [
{
"severity": "error",
"code": null,
"path": "MY-APP.pkg",
"message": "The binary is not signed.",
"docUrl": null,
"architecture": null
}
]
}
Here is the output of codesign -v -vvv --deep --strict MY-APP.app:
...
MY-APP.app: valid on disk
MY-APP.app: satisfies its Designated Requirement
Output of pkgutil --check-signature MY-APP.pkg :
Package "MY-APP.pkg":
Status: signed by a developer certificate issued by Apple for distribution
Signed with a trusted timestamp on: 2021-07-20 08:59:11 +0000
Certificate Chain:
1. Developer ID Installer: MY COMPANY (XXXXXXXXXX)
Expires: 2024-06-26 09:35:51 +0000
SHA256 Fingerprint:
3D ...
------------------------------------------------------------------------
2. Developer ID Certification Authority
Expires: 2027-02-01 22:12:15 +0000
SHA256 Fingerprint:
7A ...
------------------------------------------------------------------------
3. Apple Root CA
Expires: 2035-02-09 21:40:36 +0000
SHA256 Fingerprint:
B0 ..
And the output of spctl -vvv --assess --raw --verbose=10 --type exec MY-APP.app:
build/MY-APP.app: accepted
origin=Developer ID Application: MY COMPANY (XXXXXXXXXX)
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>assessment:authority</key>
<dict>
<key>assessment:authority:flags</key>
<integer>2</integer>
<key>assessment:authority:row</key>
<integer>6</integer>
<key>assessment:authority:source</key>
<string>Developer ID</string>
</dict>
<key>assessment:originator</key>
<string>Developer ID Application: MY COMPANY (XXXXXXXXXX)</string>
<key>assessment:remote</key>
<true/>
<key>assessment:verdict</key>
<true/>
</dict>
</plist>
We are blocked at the moment and can't figure out why the notarization service is rejecting the .pkg file due to "binary not signed" error. any suggestions on how to solve this or analyse the root cause of the failure?
Post marked as solved
399
Views
I am trying to notarize a framework built for both platforms, arm64 and x8664 (universal).
The framework contains a static library (fat file) which can't be notarized.
I get the following errors in the log: "The binary is not signed." and "The signature does not include a secure timestamp."
When I build only for one of the two architectures (non-fat file), the notarization works without any issues.
Universal:
% file libtbarcode11.a
libtbarcode11.a: Mach-O universal binary with 2 architectures: [x8664:current ar archive] [arm64]
libtbarcode11.a (for architecture x8664): current ar archive
libtbarcode11.a (for architecture arm64): current ar archive % lipo -info libtbarcode11.a
Architectures in the fat file: libtbarcode11.a are: x8664 arm64
% codesign -v --verify libtbarcode11.a
libtbarcode11.a: valid on disk
libtbarcode11.a: satisfies its Designated Requirement arm64:
% file libtbarcode11.a
libtbarcode11.a: current ar archive % lipo -info libtbarcode11.a
Non-fat file: libtbarcode11.a is architecture: arm64 % codesign -v --verify libtbarcode11.a
libtbarcode11.a: valid on disk
libtbarcode11.a: satisfies its Designated Requirement
codesign commands I tried so far:
codesign --force --verify --verbose --sign "MyDeveloperIDApplicationCert" libtbarcode11.a
codesign --force --verify --verbose --sign "MyDeveloperIDApplicationCert" --options runtime libtbarcode11.a
codesign --force --verify --verbose --sign "MyDeveloperIDApplicationCert" --deep libtbarcode11.a
Post not yet marked as solved
586
Views
Since upgrading to Xcode 12.5, attempting to submit an app for notarization with /usr/bin/xcrun altool --notarize-app has started failing ~10% of the time with the error Upload succeeded but did not receive a RequestUUID.. Has anyone else encountered this issue?
?xml version="1.0" encoding="UTF-8"?
!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"
plist version="1.0"
dict
keyos-version/key
string11.2.0/string
keyproduct-errors/key
array
dict
keycode/key
integer-1018/integer
keymessage/key
stringUpload succeeded but did not receive a RequestUUID./string
keyuserInfo/key
dict
keyNSLocalizedDescription/key
stringUpload succeeded but did not receive a RequestUUID./string
keyNSLocalizedFailureReason/key
stringUnable to upload your app for notarization./string
/dict
/dict
/array
keytool-path/key
string/Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/Versions/A/Frameworks/AppStoreService.framework/string
keytool-version/key
string4.050.1210/string
/dict
/plist
Post not yet marked as solved
467
Views
I get the following error "Failed retrieving request UUID for upload" when I try to upload a new build for the Apple Notary service.. everything worked smoothly so far. I have this issue for more than 24 hours now...
What I tried so far:
T&C are accepted up to date
I tried to generate multiple builds with different build numbers as well...
Post not yet marked as solved
166
Views
I am trying to follow the guideline for Notarizing Apps from the Command Line
but for whatever reason I cannot see the link to generate an app-specific password in appleid portal . I am using AppleID provided by my employer, my role is Developer and I have 2-factor authentication in-place.
Seems like that this an account specific problem because I can see the link and able to generate the password while authenticating with my personal Apple ID.
Is there anything that Account Holder/Admin should tweak with the permissions so the link could appear?
As an alternative option may I use personal AppleID to submit pkg installer for notarization which was signed with my employer's Developer Installer ID certificate?
Post marked as solved
110
Views
The System Status page says that the notary service is up, but every time I try it, I get "Failed retrieving request UUID for upload". I tried with 2 apps, and both Xcode 12.5 and 13.0 beta 2.
Post not yet marked as solved
64
Views
Hi,
I just made two successfull notarizations this morning, in less than 10 minutes :
0d8a6b87-5dcc-43c8-8a1a-58d4a94d2283
d731b45e-9108-4c19-8056-06ba4e7dd16e
Suddendly the two latests ones are pending, the worst one is pending for almost an hour:
fe89d78a-21e8-4f03-96b7-19a7cc3bd9a0
What is the problem ?
S.
Post not yet marked as solved
76
Views
Is "Developer ID Notary Service" down?
I have been trying for the last hour and half. It just never returns either error or success. I waited more than 10mins and did it multiple times. It usually takes less than 3mins.
Post marked as solved
150
Views
Hi, currently I have a macOS app that contains an executable I compiled of openvpn, when I try to notarize the macOS application that contains openvpn I get the following error message.
Currently I compile openvpn like this for x86_64 (Intel):
https://gist.github.com/lecksfrawen/fab1a1690ab7b80b4acac617cb5be403
Is there a way to add to autoconf (make && make install) something similar to cmake's XCODE_ATTRIBUTE_ENABLE_HARDENED_RUNTIME to allow the project to be compiled with the hardened runtime?
Or should I use Hardened Runtime exception in Signing & Capabilities in my main app?
Thanks.
Post marked as solved
92
Views
Was under the impression that all executable components needed to be signed with the same certificate as the bundle. However I've just encountered a recently Notarized application where that isn't the case.
These components are in the "/Contents/Resources/" folder of the main bundle. While I can suggest the developer to sign these with the same identity and move them to a more suitable location.
It would appear that codesign, GateKeeper and Notarization has accepted these.
Or are these restrictions for the Mac App Store only?
Post not yet marked as solved
589
Views
Hi All,
Trying to validate some altool credentials, produces this error message.
"Failed to get authorization for username '<username/>' and password with errors:( "Error Domain=NSCocoaErrorDomain Code=0 "Status code: 0" UserInfo={NSLocalizedDescription=Status code:0, NSLocalizedFailureReason=The auth server returned a bad status code.}")
This is returned when altool is called in the following way.
xcrun altool --notarization-history 0 -u <username/> -p <password/> --output-format xml
macOS 11.2.3 and Xcode 12.5
Things that have been tried already.
Making sure the Apple system status page shows no issues.
Different networks.
Checked to see if any agreements need to be "activated".
Recreated the app-specific password multiple times.
Any other suggestions?
@Quinn - Hi Quinn, it's Sam Rowlands (again) and this is with another App Wrapper customer experiencing this issue (so not me directly).
