MAS Application Loader XojoFramework ERROR ITMS-90334: Bundle identifier mismatch

  1. ‹ Older
  2. 3 months ago

    Horst J

    Aug 9 Pre-Release Testers, Xojo Pro Europe, Germany, Stuttgart

    Since today I got the same error:

    [2018-08-10 01:05:30 MESZ] <main> DBG-X: parameter Success = false
    [2018-08-10 01:05:30 MESZ] <main> ERROR: ERROR ITMS-90334: "Invalid Code Signature Identifier. The identifier "com.xojo.framework" in your code signature for "XojoFramework" must match its Bundle Identifier "com.xojo.XojoFramework""
    [2018-08-10 01:05:30 MESZ] <main> DBG-X: The error code is: 1102
    [2018-08-10 01:05:30 MESZ] <main> INFO: Done performing authentication.
    [2018-08-10 01:05:30 MESZ] <main> INFO: JSON:{"msg":{"phase":"Upload","count":3,"description":"Operation failed","index":3},"messageType":"VerifyProgress"}
    [2018-08-10 01:05:30 MESZ] <main> DBG-X: Returning 1

    In the current AppWrapper release 3.8.7 /256) the switch for "Use same identifier for all components" is unchecked and not enabled.

  3. Horst J

    Aug 9 Pre-Release Testers, Xojo Pro Europe, Germany, Stuttgart

    I don't know what apple is checking this values. After 10 times to try upload to MAS it was now accepted.

  4. Horst J

    Aug 16 Pre-Release Testers, Xojo Pro Europe, Germany, Stuttgart

    Yesterday I got the same error while transfering my app to MAS.

    [2018-08-10 01:05:30 MESZ] <main> ERROR: ERROR ITMS-90334: "Invalid Code Signature Identifier. The identifier "com.xojo.framework" in your code signature for "XojoFramework" must match its Bundle Identifier "com.xojo.XojoFramework""
    [2018-08-10 01:05:30 MESZ] <main> DBG-X: The error code is: 1102

    I must try 20-30 times to transfer my app to MAS. Has anobody the same problem?

  5. Christian S

    Aug 16 Pre-Release Testers, Xojo Pro, XDC Speakers Germany

    did you sign the Xojo framework yourself?

  6. Horst J

    Aug 16 Pre-Release Testers, Xojo Pro Europe, Germany, Stuttgart

    I use AppWrapper release 3.8.7 (256).

  7. Sascha S

    Aug 16 Pre-Release Testers, Xojo Pro Germany/W'haven

    @Horst J I use AppWrapper release 3.8.7 (256).

    Please make sure you do not have "Use same identifier for all components" checked in the Code signature Settings. ;)

  8. Horst J

    Aug 16 Pre-Release Testers, Xojo Pro Europe, Germany, Stuttgart

    This setting is currently OFF and disabled in AppWrapper

  9. Michael D

    Aug 16 Pre-Release Testers, Xojo Pro
    Edited 3 months ago

    @Horst J com.xojo.framework [...] must match [...] com.xojo.XojoFramework

    Do the two items really differ in upper/lowercase?

  10. Horst J

    Aug 16 Pre-Release Testers, Xojo Pro Europe, Germany, Stuttgart
    Edited 3 months ago

    Same result in 2018R1, 2018R1.1 and 2018R2

    After AppWrapper:
    Into folder "AppName/Contents/Frameworks"
    codesign -vvv -d XojoFramework.framework

    Identifier=com.xojo.XojoFramework
    Format=bundle with Mach-O thin (x86_64)
    CodeDirectory v=20200 size=46966 flags=0x0(none) hashes=1460+5 location=embedded
    Hash type=sha256 size=32
    CandidateCDHash sha1=eb4b09f1f763847593a85bf00351ef39098f3572
    CandidateCDHash sha256=0524e92dadfeaa74483a7ed45263ebf06ac6a49c
    Hash choices=sha1,sha256
    CDHash=0524e92dadfeaa74483a7ed45263ebf06ac6a49c
    Signature size=4812
    Authority=3rd Party Mac Developer Application: H#### J#### (########)
    Authority=Apple Worldwide Developer Relations Certification Authority
    Authority=Apple Root CA
    Signed Time=15.08.2018, 23:02:28
    Info.plist entries=19
    TeamIdentifier=R93ZF35NX9
    Sealed Resources version=2 rules=13 files=45
    Internal requirements count=1 size=204

    Before AppWrapper:
    Identifier=com.xojo.framework
    Format=bundle with Mach-O universal (i386 x86_64)
    CodeDirectory v=20200 size=46898 flags=0x0(none) hashes=1460+3 location=embedded
    Hash type=sha256 size=32
    CandidateCDHash sha1=6c554ca060b6d8797b6a1e080b60b472f31c177e
    CandidateCDHash sha256=590fa7fbbd375710727026b0541fdfeb7ef24a80
    Hash choices=sha1,sha256
    CDHash=590fa7fbbd375710727026b0541fdfeb7ef24a80
    Signature size=8923
    Authority=Developer ID Application: Xojo, Incorporated (########)
    Authority=Developer ID Certification Authority
    Authority=Apple Root CA
    Timestamp=03.08.2018, 00:52:43
    Info.plist entries=19
    TeamIdentifier=6MG2NQJ3FZ
    Sealed Resources version=2 rules=13 files=67
    Internal requirements count=1 size=180

    AppWrapper settings:
    -image-

  11. Horst J

    Aug 16 Pre-Release Testers, Xojo Pro Europe, Germany, Stuttgart
    Edited 3 months ago

    And also special parameter for packaging are not set.

    -image-

  12. Horst J

    Aug 16 Pre-Release Testers, Xojo Pro Europe, Germany, Stuttgart

    My next application has the same problem. I think it is a problem from AppWrapper.

    ERROR ITMS-90334: "Invalid Code Signature Identifier. The identifier "com.xojo.framework" in your code signature for "XojoFramework" must match its Bundle Identifier "com.xojo.XojoFramework""

  13. Tim P

    Aug 16 Pre-Release Testers feedback://46303

    I mean, I have zero problems with AppWrapper and listing apps in the app store. You should reach out to Sam by email if you really think it's AppWrapper. Try to provide as much as you can to show why you think it's AppWrapper, because if it is indeed, it benefits us all to get it fixed :)

  14. Sam R

    Aug 17 Pre-Release Testers, Xojo Pro Hengchun, Pingtung, Taiwan

    I am not at home for the next few days, so my ability to answer e-mails is somewhat hampered (am in Singapore for a friends wedding).

    This problem has come and gone over the years, I don't fully understand why either. Often when people have this problem, simply trying to resubmit at a later time, it goes through.

    However I am assuming that somethings changed at Apple's end and now they want it done differently; there is nothing I can do for the next few days and I'm sorry about that. I'll be back home on Monday (at stupid o'clock) and probably be alive at some point on Tuesday afternoon. I'll get right on to it then.

  15. Sam R

    Aug 20 Pre-Release Testers, Xojo Pro Hengchun, Pingtung, Taiwan
    Edited 3 months ago

    Okay, I am back and I'm looking into this. Are you still getting it?

    Message Edited:

    So I've checked the latest documentation, had to search to find it as they've not updated the documentation I was using and don't link you to the newer docs. They have changed the procedure, I need to do a code audit before I can redesign how it signs Frameworks (they're quite complicated and Apple's docs over simplify).

    From your e-mail I can see that you're using High Sierra 10.13.6, but could you please tell me, which version of Xcode and which version of Xojo. I want to double check some things, to see if I can reproduce the incorrect bundle identifer and design my solution to make sure that it doesn't occur any more.

  16. Sam R

    Aug 20 Pre-Release Testers, Xojo Pro Hengchun, Pingtung, Taiwan

    Addendum:
    I have tested it with App Wrapper 3.8.7, on macOS 10.11.6 with Xcode 8.2.1 and the bundle identifier is matching. I'm going to add some code to the diagnostics that will make it easy to see the code signed bundle identifier from within App Wrapper, also for it to check them.

    Lastly, I vaguely recall that there is the ability to store a bundle identifier directly within an executable file, so I will check this too. Incase there is, and it's different.

  17. Horst J

    Aug 20 Pre-Release Testers, Xojo Pro Europe, Germany, Stuttgart

    Xojo 2018R1.1 and 2018R2
    xCode: 9.4.1 (9F2000)
    Application Loader 3.7.1 (1047)
    macOS 10.13.6

  18. Sam R

    Aug 21 Pre-Release Testers, Xojo Pro Hengchun, Pingtung, Taiwan
    Edited 3 months ago

    So after spending a lot of time yesterday and staying up late, I was unable to find anything in the signed application that referenced "com.xojo.framework".

    @Horst J has also confirmed that attempting to resubmit yesterday, worked. So in my opinion this is either an issue with the file system (Don't forget I had an issue where an empty language folder wasn't being included and after repairing the disk it magically worked), or this is a an error at Apple's end, which happens also.

    After many testes with App Wrapper (using API), Terminal and a 3rd Party product, I could find no mention of the incorrect bundle identifier. My final test, was to use the terminal command grep -lr "com.xojo.framework" <pathtoappbundle>. On the unsigned version it highlighted 3 files (2 were symbolic links). However the wrapped version listed no files.

    Either way, after many hours, I'm unable to find it and left not understanding how this can occur.

  19. Greg O

    Aug 21 Xojo Inc

    @Sam R By default the Xojo bundle is signed with the incorrect bundle identifier, I've created a feedback report here Feedback Case #53069. It's possible that Apple is storing the old identifier somewhere, encoded or encrypted (otherwise the grep would find it).

    Sam, Why do you think that the bundle identifier is incorrect?

  20. Sam R

    Aug 21 Pre-Release Testers, Xojo Pro Hengchun, Pingtung, Taiwan

    @Greg OLone Sam, Why do you think that the bundle identifier is incorrect?

    The bundle identifier (according to the XojoFramework's plist) is "com.xojo.XojoFramework", however the bundle identifier in the code signature (when you click on Build in Xojo) is "com.xojo.framework". It doesn't match the actual bundle identifier of the framework.

    Please don't misunderstand me, I am not blaming Xojo for this. I am simply trying to figure out what causes this problem. It comes and goes, and each time I am none the wiser. I have a list of conspiracy theories, that could be potential POF, one of them is that it's storing the replaced code signature data somewhere and sharing that with Apple.

    p.s. An incorrect bundle identifier will (currently) pass end user verification, however it doesn't pass Apple's server side verification. I realize it's technically not an issue as we have to re-codesign the bundle anyway, but I thought that this should be fixed.

  21. Sam R

    Aug 22 Pre-Release Testers, Xojo Pro Hengchun, Pingtung, Taiwan

    So in an attempt to gather some more data to solve this situation, I've modified the application diagnostics and added a "Verify" button to the Wrapping Window. This should help confirm if the wrapping was successful, so just before you submit to Apple, click the "Verify" button and make sure theres no code signing issues.

    http://www.ohanaware.com/appwrapper/appWrapper3update388.dmg

or Sign Up to reply!