Xamarin-macios: [Mac] Couldn't find platform family in Info.plist CFBundleSupportedPlatforms or Mach-O LC_VERSION_MIN for Mono.Security.dll.dylib

[jamesmontemagno]

Steps to Reproduce

1. Build Xamarin.Mac app
2. Configure AOT for release build ( I tried Core, SDK, and All)
3. Submit to Apple

Expected Behavior

Actual Behavior

Application uploader fails with: Couldn't find platform family in Info.plist CFBundleSupportedPlatforms or Mach-O LC_VERSION_MIN for Mono.Security.dll.dylib

Environment

https://gist.github.com/jamesmontemagno/c3dedd5bfb800c1b09744afdf9ae1d58

Build Logs

Example Project (If Possible)

https://github.com/jamesmontemagno/MyStreamTimer/tree/macos

[chamons]

@spouliot Make sure we add this case to the new submission tests.

[jamesmontemagno]

Turning AOT off worked just fine, but was not ideal i don't think.

[spouliot]

I added AOT on the submission tests but it did not fail (at least on d16-2). I'll run the same, updated, test on stable

_edit_ it was d16-2 not master which fails with https://github.com/xamarin/xamarin-macios/issues/5954

[spouliot]

I can duplicate the issue, from Xcode, with XM 5.8.0.0 and the GitHub project

[spouliot]

hmm... submitting the same app manually (using altool) works :|

[ARogister10]

I want to put my application on the AppStore since Monday and I have the same error :

Could not find platform family in Info.plist CFBundleSupportedPlatforms or Mach-O LC_VERSION_MIN for BouncyCastle.CryptoExt.dll.dylib

I compile my project in AOT but even if I do not put this option, I have the same problem. What can I do ?

[ARogister10]

How did you put the app on the AppStore using altool so I could try ?

[spouliot]

@ARogister10 something else is wrong. If you turn off AOT then you won't have *.dll.dylib files. Please try again, do a clean before and make sure tour "Release" configuration also has AOT set to None

You can try altool from the command line, like this:

xcrun altool -f myapp.pkg -t osx -u [email protected] -p your-password --upload-app

you'll get upload result (which only means it was uploaded, not that it's correct) similar to

2019-05-07 15:17:14.128 altool[35021:1368375] No errors uploading myapp.pkg'

The go to the AppConnect web site to see the result (and continue your submission)

[ARogister10]

For your info, I finally could use Application Loader to upload my application on the AppStore.

My application is compiled in AOT.

When I managed to use Application Loader (with the password of the application because I am in 2 factors), it worked.

Here, the problem happens when I want to upload via xCode the archive that I generated with Visual Studio.

For me, there is a problem with the archive or others but it is not normal that it works when using Application Loader and not xCode.

FYI, with my iOS app, I did exactly the same procedure and I had no problems.

Can you test that ?

[desunit]

I have the same issue when trying to compile it with AOT. Any workarounds except manually uploading it with altool?

[ARogister10]

try this. compile your project in AOT. do the pkg to post on the appstore and after, you use Application Loader to put your project because with XCode, it does not work

Alain

Le 19 juil. 2019 à 09:32, Sergey Bogdanov [e-mail] a écrit :

I have the same issue when trying to compile it with AOT. Any workarounds?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[desunit]

Yeah, Application Loader works for me. Thanks! The altool just hangs though ...

[desunit]

Just received email from Apple about Invalid Signature for all dlls:

ITMS-90238: Invalid Signature - The executable at path TestApp.app/Contents/MonoBundle/System.Core.dll.dylib has following signing error(s): code object is not signed at all In architecture: x86_64 . Refer to the Code Signing and Application Sandboxing Guide at http://developer.apple.com/library/mac/#documentation/Security/Conceptual/CodeSigningGuide/AboutCS/AboutCS.html and Technical Note 2206 at https://developer.apple.com/library/mac/technotes/tn2206/_index.html for more information.

ITMS-90238: Invalid Signature - The executable at path TestApp.app/Contents/MonoBundle/System.Data.dll.dylib has following signing error(s): code object is not signed at all In architecture: x86_64 . Refer to the Code Signing and Application Sandboxing Guide at http://developer.apple.com/library/mac/#documentation/Security/Conceptual/CodeSigningGuide/AboutCS/AboutCS.html and Technical Note 2206 at https://developer.apple.com/library/mac/technotes/tn2206/_index.html for more information.

ITMS-90238: Invalid Signature - The executable at path TestApp.app/Contents/MonoBundle/System.Memory.dll.dylib has following signing error(s): code object is not signed at all In architecture: x86_64 . Refer to the Code Signing and Application Sandboxing Guide at http://developer.apple.com/library/mac/#documentation/Security/Conceptual/CodeSigningGuide/AboutCS/AboutCS.html and Technical Note 2206 at https://developer.apple.com/library/mac/technotes/tn2206/_index.html for more information.

ITMS-90238: Invalid Signature - The executable at path TestApp.app/Contents/MonoBundle/System.Runtime.CompilerServices.Unsafe.dll.dylib has following signing error(s): code object is not signed at all In architecture: x86_64 . Refer to the Code Signing and Application Sandboxing Guide at http://developer.apple.com/library/mac/#documentation/Security/Conceptual/CodeSigningGuide/AboutCS/AboutCS.html and Technical Note 2206 at https://developer.apple.com/library/mac/technotes/tn2206/_index.html for more information.

ITMS-90238: Invalid Signature - The executable at path TestApp.app/Contents/MonoBundle/System.Runtime.Serialization.dll.dylib has following signing error(s): code object is not signed at all In architecture: x86_64 . Refer to the Code Signing and Application Sandboxing Guide at http://developer.apple.com/library/mac/#documentation/Security/Conceptual/CodeSigningGuide/AboutCS/AboutCS.html and Technical Note 2206 at https://developer.apple.com/library/mac/technotes/tn2206/_index.html for more information.

ITMS-90238: Invalid Signature - The executable at path TestApp.app/Contents/MonoBundle/System.ServiceModel.Internals.dll.dylib has following signing error(s): code object is not signed at all In architecture: x86_64 . Refer to the Code Signing and Application Sandboxing Guide at http://developer.apple.com/library/mac/#documentation/Security/Conceptual/CodeSigningGuide/AboutCS/AboutCS.html and Technical Note 2206 at https://developer.apple.com/library/mac/technotes/tn2206/_index.html for more information.

ITMS-90238: Invalid Signature - The executable at path TestApp.app/Contents/MonoBundle/System.dll.dylib has following signing error(s): code object is not signed at all In architecture: x86_64 . Refer to the Code Signing and Application Sandboxing Guide at http://developer.apple.com/library/mac/#documentation/Security/Conceptual/CodeSigningGuide/AboutCS/AboutCS.html and Technical Note 2206 at https://developer.apple.com/library/mac/technotes/tn2206/_index.html for more information.

ITMS-90238: Invalid Signature - The executable at path TestApp.app/Contents/MonoBundle/Xamarin.Mac.dll.dylib has following signing error(s): code object is not signed at all In architecture: x86_64 . Refer to the Code Signing and Application Sandboxing Guide at http://developer.apple.com/library/mac/#documentation/Security/Conceptual/CodeSigningGuide/AboutCS/AboutCS.html and Technical Note 2206 at https://developer.apple.com/library/mac/technotes/tn2206/_index.html for more information.

ITMS-90238: Invalid Signature - The executable at path TestApp.app/Contents/MonoBundle/libMonoPosixHelper.dylib has following signing error(s): code object is not signed at all In architecture: x86_64 . Refer to the Code Signing and Application Sandboxing Guide at http://developer.apple.com/library/mac/#documentation/Security/Conceptual/CodeSigningGuide/AboutCS/AboutCS.html and Technical Note 2206 at https://developer.apple.com/library/mac/technotes/tn2206/_index.html for more information.

ITMS-90238: Invalid Signature - The executable at path TestApp.app/Contents/MonoBundle/mscorlib.dll.dylib has following signing error(s): code object is not signed at all In architecture: x86_64 . Refer to the Code Signing and Application Sandboxing Guide at http://developer.apple.com/library/mac/#documentation/Security/Conceptual/CodeSigningGuide/AboutCS/AboutCS.html and Technical Note 2206 at https://developer.apple.com/library/mac/technotes/tn2206/_index.html for more information.

It turns out that disabling "Enable hybrid AOT compiler" solves the problem. @spouliot Any ideas why?

Environment

https://gist.github.com/desunit/58f82c2f52ac522b84a81df48ed92ba6

[ARogister10]

You must to compile your project with appstore (not release) with a certifucat for the appstore

Alain

Le 19 juil. 2019 à 11:37, Sergey Bogdanov [e-mail] a écrit :

Just received notification from Apple:

ITMS-90238: Invalid Signature - The executable at path TestApp.app/Contents/MonoBundle/System.Core.dll.dylib has following signing error(s): code object is not signed at all In architecture: x86_64 . Refer to the Code Signing and Application Sandboxing Guide at http://developer.apple.com/library/mac/#documentation/Security/Conceptual/CodeSigningGuide/AboutCS/AboutCS.html and Technical Note 2206 at https://developer.apple.com/library/mac/technotes/tn2206/_index.html for more information.

ITMS-90238: Invalid Signature - The executable at path TestApp.app/Contents/MonoBundle/System.Data.dll.dylib has following signing error(s): code object is not signed at all In architecture: x86_64 . Refer to the Code Signing and Application Sandboxing Guide at http://developer.apple.com/library/mac/#documentation/Security/Conceptual/CodeSigningGuide/AboutCS/AboutCS.html and Technical Note 2206 at https://developer.apple.com/library/mac/technotes/tn2206/_index.html for more information.

ITMS-90238: Invalid Signature - The executable at path TestApp.app/Contents/MonoBundle/System.Memory.dll.dylib has following signing error(s): code object is not signed at all In architecture: x86_64 . Refer to the Code Signing and Application Sandboxing Guide at http://developer.apple.com/library/mac/#documentation/Security/Conceptual/CodeSigningGuide/AboutCS/AboutCS.html and Technical Note 2206 at https://developer.apple.com/library/mac/technotes/tn2206/_index.html for more information.

ITMS-90238: Invalid Signature - The executable at path TestApp.app/Contents/MonoBundle/System.Runtime.CompilerServices.Unsafe.dll.dylib has following signing error(s): code object is not signed at all In architecture: x86_64 . Refer to the Code Signing and Application Sandboxing Guide at http://developer.apple.com/library/mac/#documentation/Security/Conceptual/CodeSigningGuide/AboutCS/AboutCS.html and Technical Note 2206 at https://developer.apple.com/library/mac/technotes/tn2206/_index.html for more information.

ITMS-90238: Invalid Signature - The executable at path TestApp.app/Contents/MonoBundle/System.Runtime.Serialization.dll.dylib has following signing error(s): code object is not signed at all In architecture: x86_64 . Refer to the Code Signing and Application Sandboxing Guide at http://developer.apple.com/library/mac/#documentation/Security/Conceptual/CodeSigningGuide/AboutCS/AboutCS.html and Technical Note 2206 at https://developer.apple.com/library/mac/technotes/tn2206/_index.html for more information.

ITMS-90238: Invalid Signature - The executable at path TestApp.app/Contents/MonoBundle/System.ServiceModel.Internals.dll.dylib has following signing error(s): code object is not signed at all In architecture: x86_64 . Refer to the Code Signing and Application Sandboxing Guide at http://developer.apple.com/library/mac/#documentation/Security/Conceptual/CodeSigningGuide/AboutCS/AboutCS.html and Technical Note 2206 at https://developer.apple.com/library/mac/technotes/tn2206/_index.html for more information.

ITMS-90238: Invalid Signature - The executable at path TestApp.app/Contents/MonoBundle/System.dll.dylib has following signing error(s): code object is not signed at all In architecture: x86_64 . Refer to the Code Signing and Application Sandboxing Guide at http://developer.apple.com/library/mac/#documentation/Security/Conceptual/CodeSigningGuide/AboutCS/AboutCS.html and Technical Note 2206 at https://developer.apple.com/library/mac/technotes/tn2206/_index.html for more information.

ITMS-90238: Invalid Signature - The executable at path TestApp.app/Contents/MonoBundle/Xamarin.Mac.dll.dylib has following signing error(s): code object is not signed at all In architecture: x86_64 . Refer to the Code Signing and Application Sandboxing Guide at http://developer.apple.com/library/mac/#documentation/Security/Conceptual/CodeSigningGuide/AboutCS/AboutCS.html and Technical Note 2206 at https://developer.apple.com/library/mac/technotes/tn2206/_index.html for more information.

ITMS-90238: Invalid Signature - The executable at path TestApp.app/Contents/MonoBundle/libMonoPosixHelper.dylib has following signing error(s): code object is not signed at all In architecture: x86_64 . Refer to the Code Signing and Application Sandboxing Guide at http://developer.apple.com/library/mac/#documentation/Security/Conceptual/CodeSigningGuide/AboutCS/AboutCS.html and Technical Note 2206 at https://developer.apple.com/library/mac/technotes/tn2206/_index.html for more information.

ITMS-90238: Invalid Signature - The executable at path TestApp.app/Contents/MonoBundle/mscorlib.dll.dylib has following signing error(s): code object is not signed at all In architecture: x86_64 . Refer to the Code Signing and Application Sandboxing Guide at http://developer.apple.com/library/mac/#documentation/Security/Conceptual/CodeSigningGuide/AboutCS/AboutCS.html and Technical Note 2206 at https://developer.apple.com/library/mac/technotes/tn2206/_index.html for more information.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[desunit]

@ARogister10 Yeah, I did that - otherwise I won't be able to submit app without "Enable hybrid AOT compiler". The problem appears only with that checkbox.