Post not yet marked as solved
Well, today both Xcode and altool are working again. No changes on my side.
Post not yet marked as solved
Thank you. I’ll give notarytool a try.
Any suggestions on how to resolve the Xcode issue? I have no pending agreements, all agreements are signed and there’s only one team.
Post not yet marked as solved
I just started getting the same error in Xcode and I'm NOT a member of multiple teams. I also don't have any outstanding agreements to be signed.
If it helps, altool is giving me this error when trying to notarize a .pkg (the same workflow was working two days ago):
java.io.IOException: Server returned HTTP response code: 504 for URL: https://contentdelivery.itunes.apple.com/transporter/lib/osgibootstrapper.jar
at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source)
at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
at java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Unknown Source)
at java.base/java.net.URL.openStream(Unknown Source)
at com.apple.transporter.launcher.Application.start(Application.java:340)
at com.apple.transporter.launcher.Application.main(Application.java:947)
java.lang.reflect.InvocationTargetException
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.base/java.lang.reflect.Method.invoke(Unknown Source)
at com.apple.transporter.launcher.Application.start(Application.java:450)
at com.apple.transporter.launcher.Application.main(Application.java:947)
Caused by: org.osgi.framework.BundleException: Could not resolve module: com.apple.transporter.starter [17]
Unresolved requirement: Import-Package: javax.annotation; version="[3.0.0,4.0.0)"; resolution:="optional"
Unresolved requirement: Import-Package: com.apple.transporter.launcher.asu; version="[1.0.0,2.0.0)"
at org.eclipse.osgi.container.Module.start(Module.java:463)
at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:440)
at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:459)
at com.apple.transporter.bootstrap.BootstrapperPhase2.bootstrapBundles(BootstrapperPhase2.java:321)
at com.apple.transporter.bootstrap.BootstrapperPhase2.start(BootstrapperPhase2.java:153)
at com.apple.transporter.bootstrap.BootstrapperPhase1.startOSGiFramework(BootstrapperPhase1.java:319)
at com.apple.transporter.bootstrap.BootstrapperPhase1.bootstrap(BootstrapperPhase1.java:99)
at com.apple.transporter.bootstrap.BootstrapperPhase1.bootstrap(BootstrapperPhase1.java:59)
at com.apple.transporter.launcher.Launcher.launchBootstrapper(Launcher.java:37)
... 6 more
Out:
*** Error: Notarization failed for '<EDITED>.pkg'.
*** Error: An error occurred uploading to Apple Services. (-10000)
Post not yet marked as solved
Same here. Notarizing using altool.
It first complained it couldn't find metadata.xml. Now it's complaining it's not finding the .dmg, which is the file I'm trying to notarize. Same script has worked for months with no problems. Retrying is not helping.
I'm running altool on Big Sur 11.2.3 (Intel and M1, same results).
Any ideas?
Thank you, Quinn. That was exactly what needed to be done.
Adrian
For what it's worth it, I ended up migrating the creation of the installers from PackageMaker to product build//pkgbuild (while using the same contents, resources, etc.), which I had to do anyway, and notarization works perfectly.
Post not yet marked as solved
Hi sean.rich.dev,
Did you find a solution? I'm facing the same problem. The tracking separator doesn't seem to "track" the sidebar divider and therefore the toolbar items don't align as they should.
Thanks.
Thank you!I tried your steps and notarization worked as expected. I then went and tried the same steps but instead of packaging the test app, I packaged my app. It also worked. So, something about the way I'm building the package must be the reason for this to fail.I was using PackageMaker (yes, I know) but when I started encountering this issue, I switched to Packages (a 3rd party app) for building the package (which I understand uses productbuild). The .pkg I'm creating is pretty much standard, except that it includes a couple of post-install scripts. I wonder if that's what's causing the problem. I'll have to play around with productbuild and see if I can find what exactly is making notarization report the package is corrupt. Or maybe if I use productbuild to construct the package the problem will go away.Adrian
Just to add to the post, I tried notarizing again a .pkg installer that I had already notarized successfully a few weeks ago and I got the same problem, so unless I'm missing something obvious here, there was a change in Apple's side that is now causing this problem.In the meantime, I'm going to try to notarize the app first, then package it, and then notarize the .pkg file.
