-
Re: Unable to Sign “invalid argument '???'”
mxcl Sep 14, 2018 8:28 AM (in response to mxcl)If I export the archive with the “Developer ID” option and then run codesign verify it is good:
$ codesign --verify --deep --strict --verbose=2 Canopy.app/ --prepared:/Users/mxcl/Desktop/Canopy-macOS 2018-09-14 11-26-40/Canopy.app/Contents/Frameworks/libswiftCoreImage.dylib --validated:/Users/mxcl/Desktop/Canopy-macOS 2018-09-14 11-26-40/Canopy.app/Contents/Frameworks/libswiftCoreImage.dylib --prepared:/Users/mxcl/Desktop/Canopy-macOS 2018-09-14 11-26-40/Canopy.app/Contents/Frameworks/libswiftObjectiveC.dylib --validated:/Users/mxcl/Desktop/Canopy-macOS 2018-09-14 11-26-40/Canopy.app/Contents/Frameworks/libswiftObjectiveC.dylib --prepared:/Users/mxcl/Desktop/Canopy-macOS 2018-09-14 11-26-40/Canopy.app/Contents/Frameworks/libswiftAppKit.dylib --validated:/Users/mxcl/Desktop/Canopy-macOS 2018-09-14 11-26-40/Canopy.app/Contents/Frameworks/libswiftAppKit.dylib --prepared:/Users/mxcl/Desktop/Canopy-macOS 2018-09-14 11-26-40/Canopy.app/Contents/Frameworks/libswiftXPC.dylib --validated:/Users/mxcl/Desktop/Canopy-macOS 2018-09-14 11-26-40/Canopy.app/Contents/Frameworks/libswiftXPC.dylib --prepared:/Users/mxcl/Desktop/Canopy-macOS 2018-09-14 11-26-40/Canopy.app/Contents/Frameworks/libswiftCoreGraphics.dylib --validated:/Users/mxcl/Desktop/Canopy-macOS 2018-09-14 11-26-40/Canopy.app/Contents/Frameworks/libswiftCoreGraphics.dylib --prepared:/Users/mxcl/Desktop/Canopy-macOS 2018-09-14 11-26-40/Canopy.app/Contents/Frameworks/libswiftMetal.dylib --validated:/Users/mxcl/Desktop/Canopy-macOS 2018-09-14 11-26-40/Canopy.app/Contents/Frameworks/libswiftMetal.dylib --prepared:/Users/mxcl/Desktop/Canopy-macOS 2018-09-14 11-26-40/Canopy.app/Contents/Frameworks/libswiftCoreData.dylib --validated:/Users/mxcl/Desktop/Canopy-macOS 2018-09-14 11-26-40/Canopy.app/Contents/Frameworks/libswiftCoreData.dylib --prepared:/Users/mxcl/Desktop/Canopy-macOS 2018-09-14 11-26-40/Canopy.app/Contents/Frameworks/libswiftDispatch.dylib --validated:/Users/mxcl/Desktop/Canopy-macOS 2018-09-14 11-26-40/Canopy.app/Contents/Frameworks/libswiftDispatch.dylib --prepared:/Users/mxcl/Desktop/Canopy-macOS 2018-09-14 11-26-40/Canopy.app/Contents/Frameworks/libswiftCoreFoundation.dylib --validated:/Users/mxcl/Desktop/Canopy-macOS 2018-09-14 11-26-40/Canopy.app/Contents/Frameworks/libswiftCoreFoundation.dylib --prepared:/Users/mxcl/Desktop/Canopy-macOS 2018-09-14 11-26-40/Canopy.app/Contents/Frameworks/libswiftDarwin.dylib --validated:/Users/mxcl/Desktop/Canopy-macOS 2018-09-14 11-26-40/Canopy.app/Contents/Frameworks/libswiftDarwin.dylib --prepared:/Users/mxcl/Desktop/Canopy-macOS 2018-09-14 11-26-40/Canopy.app/Contents/Frameworks/libswiftos.dylib --validated:/Users/mxcl/Desktop/Canopy-macOS 2018-09-14 11-26-40/Canopy.app/Contents/Frameworks/libswiftos.dylib --prepared:/Users/mxcl/Desktop/Canopy-macOS 2018-09-14 11-26-40/Canopy.app/Contents/Frameworks/libswiftQuartzCore.dylib --validated:/Users/mxcl/Desktop/Canopy-macOS 2018-09-14 11-26-40/Canopy.app/Contents/Frameworks/libswiftQuartzCore.dylib --prepared:/Users/mxcl/Desktop/Canopy-macOS 2018-09-14 11-26-40/Canopy.app/Contents/Frameworks/PromiseKit.framework/Versions/Current/. --validated:/Users/mxcl/Desktop/Canopy-macOS 2018-09-14 11-26-40/Canopy.app/Contents/Frameworks/PromiseKit.framework/Versions/Current/. --prepared:/Users/mxcl/Desktop/Canopy-macOS 2018-09-14 11-26-40/Canopy.app/Contents/Frameworks/libswiftCore.dylib --validated:/Users/mxcl/Desktop/Canopy-macOS 2018-09-14 11-26-40/Canopy.app/Contents/Frameworks/libswiftCore.dylib --prepared:/Users/mxcl/Desktop/Canopy-macOS 2018-09-14 11-26-40/Canopy.app/Contents/Frameworks/libswiftIOKit.dylib --validated:/Users/mxcl/Desktop/Canopy-macOS 2018-09-14 11-26-40/Canopy.app/Contents/Frameworks/libswiftIOKit.dylib --prepared:/Users/mxcl/Desktop/Canopy-macOS 2018-09-14 11-26-40/Canopy.app/Contents/Frameworks/libswiftFoundation.dylib --validated:/Users/mxcl/Desktop/Canopy-macOS 2018-09-14 11-26-40/Canopy.app/Contents/Frameworks/libswiftFoundation.dylib Canopy.app/: valid on disk Canopy.app/: satisfies its Designated Requirement
-
Re: Unable to Sign “invalid argument '???'”
TapZapp Sep 14, 2018 12:18 PM (in response to mxcl)I'm having this exact same problem. I was able to successfully upload the iOS version of my app. And also I was able to notarize the direct download version of my Mac app. But uploading for Mac App Store distribution gives the same error as you received.
I wonder if it's a problem on iTunes Connect? Also, I generated a new certificate and that didn't seem to make any difference.
Would love to know how to resolve this problem.
-
-
Re: [Xcode 10] Unable to Sign “invalid argument '???'”
TapZapp Sep 15, 2018 1:00 AM (in response to mxcl)Have you found a solution to this problem yet?
I tried deleting all my certificates and provisioning profiles, from App Store Connect and from my Keychain and disk. Still no joy in submitting my app update.
-
Re: [Xcode 10] Unable to Sign “invalid argument '???'”
Mr. Brightside Sep 15, 2018 1:13 PM (in response to mxcl)Having the same issue
-
Re: [Xcode 10] Unable to Sign “invalid argument '???'”
TapZapp Sep 15, 2018 5:41 PM (in response to Mr. Brightside)I submitted a request to the support people at App Store Connect. They asked me for more information and screenshots. Hopefully they can help to figure out what the problem is.
Maybe if everyone here contacted them directly they would look more closely into it. Because right now the only way I can get my app update out is to provide it to my direct download customers only.
-
-
Re: [Xcode 10] Unable to Sign “invalid argument '???'”
TapZapp Sep 15, 2018 10:50 PM (in response to mxcl)Do you have Hardened Runtime enabled on your application target by any chance?
I had that turned on, but turned it off to see if it would solve the problem and I believe it did.
I did not get the email from Apple and I was able to attach my new build to my app in App Store Connect.
So maybe that was the solution.
I had no troubles with Hardened Runtime with the direct sale version of my app. I even notarized it.
-
Re: [Xcode 10] Unable to Sign “invalid argument '???'”
mxcl Sep 16, 2018 1:44 PM (in response to TapZapp)Disabling hardened runtime did the trick. A shame since now I have to remember to enable it if I want to distribute app-store independent builds. Oh well. Thanks so much for figuring this out!
-
Re: [Xcode 10] Unable to Sign “invalid argument '???'”
TapZapp Sep 16, 2018 2:01 PM (in response to mxcl)You can have 2 targets. One with Hardened Runtime enabled and one without. That's what I do for the MAS and direct sale versions of my app.
-
-
Re: Unable to Sign “invalid argument '???'”
haikeeba Jan 8, 2019 9:49 AM (in response to TapZapp)This is now longer necessary after late September (see thread below). The problem has been fixed and apps with the hardened runtime enabled (codesign --options runtime) can be uploaded to the Mac App Store.
-
-
Re: [Xcode 10] Unable to Sign “invalid argument '???'”
gc. Sep 17, 2018 1:18 PM (in response to mxcl)You should be able to submit an app with the hardened runtime enabled to the Mac App Store.
You've found a workaround but it shouldn't be necessary. Can you please file a bug report at <https://developer.apple.com/bug-reporting> and post the bug number here?
Thanks,
--gc
-
Re: [Xcode 10] Unable to Sign “invalid argument '???'”
1024jp Sep 20, 2018 6:42 AM (in response to gc.)Since I am facing the same issue, I have just reported my issue with the Bug Reporter.
The bug number of mine is 44639748.
-
Re: [Xcode 10] Unable to Sign “invalid argument '???'”
TapZapp Sep 21, 2018 1:53 AM (in response to gc.)I submitted a bug report a couple of days ago
rdar://44617253
-
Re: [Xcode 10] Unable to Sign “invalid argument '???'”
ag_rudy Sep 21, 2018 8:04 AM (in response to gc.)any word on this? we're still seeing this happening.
rdar://problem/44663623
-
Re: [Xcode 10] Unable to Sign “invalid argument '???'”
TapZapp Sep 24, 2018 7:21 PM (in response to ag_rudy)I was contacted today by the bug reporting team and they said they fixed it on their side. So it should work now.
-
Re: [Xcode 10] Unable to Sign “invalid argument '???'”
TapZapp Sep 24, 2018 7:48 PM (in response to TapZapp)But it didn't for me when I just tested it a few moments ago. I still received the "invalid arguments ???" email.
-
-
-
-
Re: [Xcode 10] Unable to Sign “invalid argument '???'”
Jason Sep 25, 2018 4:16 PM (in response to mxcl)As of this post, the issue reported here should now be resolved. Please try submitting your app again.
-
Re: [Xcode 10] Unable to Sign “invalid argument '???'”
1024jp Sep 26, 2018 7:04 AM (in response to Jason)I've just confirmed that this issue is now solved. Thank you for addressing it, although it is a bit too late.
-