Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Installation and Deployment
  4. Deploy Qt4 Framework on Mac does not sign
Forum Updated to NodeBB v4.3 + New Features

Deploy Qt4 Framework on Mac does not sign

Scheduled Pinned Locked Moved Unsolved Installation and Deployment
38 Posts 3 Posters 10.3k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • SGaistS SGaist

    IIRC, the id of your plugins should be updated to match where they are currently located.

    S Offline
    S Offline
    SherifOmran
    wrote on last edited by
    #16

    @SGaist what is IIRC?

    1 Reply Last reply
    0
    • SGaistS Offline
      SGaistS Offline
      SGaist
      Lifetime Qt Champion
      wrote on last edited by
      #17

      IIRC = If I Recall Correctly

      Interested in AI ? www.idiap.ch
      Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

      S 1 Reply Last reply
      0
      • SGaistS SGaist

        IIRC = If I Recall Correctly

        S Offline
        S Offline
        SherifOmran
        wrote on last edited by
        #18

        @SGaist
        do you know how to update the id of the plugin?

        1 Reply Last reply
        0
        • SGaistS Offline
          SGaistS Offline
          SGaist
          Lifetime Qt Champion
          wrote on last edited by
          #19

          install_name_tool -id

          Interested in AI ? www.idiap.ch
          Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

          S 1 Reply Last reply
          0
          • SGaistS SGaist

            install_name_tool -id

            S Offline
            S Offline
            SherifOmran
            wrote on last edited by
            #20

            @SGaist
            I read about install_name_tool but confused between change and id
            could you please give me example?

            1 Reply Last reply
            0
            • SGaistS Offline
              SGaistS Offline
              SGaist
              Lifetime Qt Champion
              wrote on last edited by
              #21

              install_name_tool -id /path/to/lib

              Interested in AI ? www.idiap.ch
              Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

              1 Reply Last reply
              0
              • S Offline
                S Offline
                SherifOmran
                wrote on last edited by
                #22

                I made the following to the libraries and frameworks except plugins

                install_name_tool -id @executable_path/../Frameworks/libcrypto.1.0.0.dylib MyApp.app/Contents/Frameworks/libcrypto.1.0.0.dylib 
                

                when i give make codesign it still fails

                1 Reply Last reply
                0
                • S Offline
                  S Offline
                  sandy.martel23
                  wrote on last edited by
                  #23

                  @SherifOmran said:

                  codesign] Error 1

                  Stupid question, but can you actually codesign something else ?

                  S 1 Reply Last reply
                  0
                  • S sandy.martel23

                    @SherifOmran said:

                    codesign] Error 1

                    Stupid question, but can you actually codesign something else ?

                    S Offline
                    S Offline
                    SherifOmran
                    wrote on last edited by
                    #24

                    @sandy.martel23
                    Very good, it is not studpid question, I tried to sign the library manually and it turned that i then signed each file in the plugin manually and then when i give
                    make codesign (it works)

                    codesign --sign '3rd Party Mac Developer Application: Sherif Omran (R3JGXHN3B3)' --keychain ~/Library/Keychains/login.keychain ./libcrypto.1.0.0.dylib
                    
                    

                    Thank you..

                    Next step, i need to create the package .. Could you please help me with the command?
                    when i give
                    make package -> it has error

                    1 Reply Last reply
                    0
                    • S Offline
                      S Offline
                      SherifOmran
                      wrote on last edited by
                      #25

                      But after i codesigned it, the app does not start
                      Process: TypingTutor [10399]
                      Path: /Users/USER/Desktop/*/TypingTutor.app/Contents/MacOS/TypingTutor
                      Identifier: com.PCfone.ArabicTypingTutor
                      Version: 1.0.0 (5.1)
                      Code Type: X86-64 (Native)
                      Parent Process: ??? [1]
                      Responsible: TypingTutor [10399]
                      User ID: 501

                      Date/Time: 2016-02-05 20:39:38.405 +0100
                      OS Version: Mac OS X 10.11.3 (15D21)
                      Report Version: 11
                      Anonymous UUID: 70210516-2C20-592D-A84C-DD5E4F2AE6C1

                      Sleep/Wake UUID: D83EB830-6064-42B2-B9B1-2693E5916DDF

                      Time Awake Since Boot: 25000 seconds
                      Time Since Wake: 1600 seconds

                      System Integrity Protection: enabled

                      Crashed Thread: 0

                      Exception Type: EXC_BAD_ACCESS (Code Signature Invalid)
                      Exception Codes: 0x0000000000000032, 0x00000001004f5000
                      Exception Note: EXC_CORPSE_NOTIFY

                      kernel messages:
                      -1 sec CODE SIGNING: cs_invalid_page(0x1004f5000): p=10399[TypingTutor] final status 0x3000200, denying page sending SIGKILL
                      -1 sec CODE SIGNING: process 10399[TypingTutor]: rejecting invalid page at address 0x1004f5000 from offset 0x0 in file "/Users/USER/Desktop/*/TypingTutor.app/Contents/Frameworks/QtSql.framework/Versions/4/QtSql" (cs_mtime:1454627177.0 == mtime:1454627177.0) (signed:1 validated:1 tainted:1 wpmapped:0 slid:0)

                      1 Reply Last reply
                      0
                      • S Offline
                        S Offline
                        SherifOmran
                        wrote on last edited by SherifOmran
                        #26

                        Report: This is a general report for somebody who may search later

                        main problem was validation process of appstore. I took 2 approaches
                        1- using make codesign (QT)
                        2- using xcode

                        in the first approach: The problem was make codesign fails, because it turned that i needed to codesign each file on its own. Then i reached a correct make codesign but make product fails to package the app.

                        In the second approach: The problem was framework embedding inside the application. App is written with Qt 4.8.7_2 and apple requests a new structure for the framework, in which there is a folder called A inside Versions folder, which does not exist and thus it failed. Note that, there is a folder called 4 inside which there is the framework, if we change this folder name from 4 to A as apple want, the app will crash.
                        Solution : Placed the frameworks inside a special folder and from xcode requested to embed the frameworks from this folder. From Terminal, i restructured the framework directory and made internal symbolic links inside the folder (Versions/A -> 4 and Versions/Current->4). In another works, created 2 symbolic links, one called A and the other called Current and both point to A.
                        Now Xcode, could validate and codesign, the output file uploaded to Appstore failed with Invalid build. Appstore send me an email stating what is failed. I will check, work on and let you know.

                        After correcting all error listed in the automatic email from Appstore that i could understand. There is only 1 error still and i would appreciate your help.

                        Final error -

                        Invalid Signature - The main app bundle TypingTutor at path TypingTutor.app has following signing error(s): --prepared:/Volumes/data01/app_data/dstr/mz_3951107737348925641dir/mz_287010058513639019dir/com.PCfone.ArabicTypingTutor.pkg/Payload/TypingTutor.app/Contents/Frameworks/libcrypto.1.0.0.dylib --validated:/Volumes/data01/app_data/dstr/mz_3951107737348925641dir/mz_287010058513639019dir/com.PCfone.ArabicTypingTutor.pkg/Payload/TypingTutor.app/Contents/Frameworks/libcrypto.1.0.0.dylib --prepared:/Volumes/data01/app_data/dstr/mz_3951107737348925641dir/mz_287010058513639019dir/com.PCfone.ArabicTypingTutor.pkg/Payload/TypingTutor.app/Contents/Frameworks/libssl.1.0.0.dylib --validated:/Volumes/data01/app_data/dstr/mz_3951107737348925641dir/mz_287010058513639019dir/com.PCfone.ArabicTypingTutor.pkg/Payload/TypingTutor.app/Contents/Frameworks/libssl.1.0.0.dylib --prepared:/Volumes/data01/app_data/dstr/mz_3951107737348925641dir/mz_287010058513639019dir/com.PCfone.ArabicTypingTutor.pkg/Payload/TypingTutor.app/Contents/Frameworks/QtCore.framework/Versions/Current/. /Volumes/data01/app_data/dstr/mz_3951107737348925641dir/mz_287010058513639019dir/com.PCfone.ArabicTypingTutor.pkg/Payload/TypingTutor.app: unsealed contents present in the root directory of an embedded framework In subcomponent: /Volumes/data01/app_data/dstr/mz_3951107737348925641dir/mz_287010058513639019dir/com.PCfone.ArabicTypingTutor.pkg/Payload/TypingTutor.app/Contents/Frameworks/QtCore.framework . 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.

                        1 Reply Last reply
                        0
                        • SGaistS Offline
                          SGaistS Offline
                          SGaist
                          Lifetime Qt Champion
                          wrote on last edited by
                          #27

                          Did you check the content of the Info.plist files ?

                          Interested in AI ? www.idiap.ch
                          Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                          1 Reply Last reply
                          0
                          • S Offline
                            S Offline
                            SherifOmran
                            wrote on last edited by
                            #28

                            The info plist seems correct ..
                            I doubt another thing, i use to create an Archive-> then open it manually and add the plugin folder and another dylib files to the framework and then validate with xcode and send to appstore ..

                            I am trying to find a way to include the files within the xcode validation.

                            1 Reply Last reply
                            0
                            • S Offline
                              S Offline
                              SherifOmran
                              wrote on last edited by
                              #29

                              current problem is : unsealed content in QtCore.framework (root)

                              1 Reply Last reply
                              0
                              • SGaistS Offline
                                SGaistS Offline
                                SGaist
                                Lifetime Qt Champion
                                wrote on last edited by
                                #30

                                Do you have more details coming with that ? e.g. current vs expected ?

                                Interested in AI ? www.idiap.ch
                                Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                                1 Reply Last reply
                                0
                                • S Offline
                                  S Offline
                                  SherifOmran
                                  wrote on last edited by SherifOmran
                                  #31

                                  After long search, i found that this mistakes comes from redundance loop of a symbolic link
                                  Inside the QtCore.framework/.../Resources, i found i made a symbolic link to the resources folder by mistake ..
                                  Solution: I removed this symbolic link and resigned the files ..

                                  For info how to code sign an already signed file is as follows:-

                                  codesign --force --sign '3rd Party Mac Developer Application: Sherif Omran (R3JGXHN3B3)' --keychain ~/Library/Keychains/login.keychain ./AppFile.app 
                                  
                                  

                                  I ll let you know of the output of the upload as soon as i get the email report

                                  1 Reply Last reply
                                  0
                                  • S Offline
                                    S Offline
                                    SherifOmran
                                    wrote on last edited by
                                    #32

                                    I still get the unsealed content error

                                    Sherif:Applications sherifomran$ codesign --verify --deep --verbose=2 TypingTutor.app/
                                    --prepared:/Users/sherifomran/Library/Developer/Xcode/Archives/2016-02-07/TypingTutor 07-02-16 00.45.xcarchive/Products/Applications/TypingTutor.app/Contents/Frameworks/libcrypto.1.0.0.dylib
                                    --validated:/Users/sherifomran/Library/Developer/Xcode/Archives/2016-02-07/TypingTutor 07-02-16 00.45.xcarchive/Products/Applications/TypingTutor.app/Contents/Frameworks/libcrypto.1.0.0.dylib
                                    --prepared:/Users/sherifomran/Library/Developer/Xcode/Archives/2016-02-07/TypingTutor 07-02-16 00.45.xcarchive/Products/Applications/TypingTutor.app/Contents/Frameworks/libssl.1.0.0.dylib
                                    --validated:/Users/sherifomran/Library/Developer/Xcode/Archives/2016-02-07/TypingTutor 07-02-16 00.45.xcarchive/Products/Applications/TypingTutor.app/Contents/Frameworks/libssl.1.0.0.dylib
                                    --prepared:/Users/sherifomran/Library/Developer/Xcode/Archives/2016-02-07/TypingTutor 07-02-16 00.45.xcarchive/Products/Applications/TypingTutor.app/Contents/Frameworks/QtCore.framework/Versions/Current/.
                                    TypingTutor.app/: unsealed contents present in the root directory of an embedded framework
                                    In subcomponent: /Users/sherifomran/Library/Developer/Xcode/Archives/2016-02-07/TypingTutor 07-02-16 00.45.xcarchive/Products/Applications/TypingTutor.app/Contents/Frameworks/QtCore.framework

                                    1 Reply Last reply
                                    0
                                    • S Offline
                                      S Offline
                                      SherifOmran
                                      wrote on last edited by
                                      #33

                                      I found the following information, but i don't understand it :
                                      codesign says I have 'unsealed content' somewhere.
                                      Do not put files or directories into the top directory of an app or framework bundle
                                      All content must be inside Contents or Versions respectively as described earlier.
                                      What do they mean?

                                      My Framework structure is as follows:
                                      QtGui.framework/
                                      QtGui -> Versions/Current/QtGui
                                      Resources -> Versions/Current/Resources/
                                      Versions

                                      1 Reply Last reply
                                      0
                                      • S Offline
                                        S Offline
                                        SherifOmran
                                        wrote on last edited by
                                        #34

                                        update 1:
                                        I downloaded Qt5.5 and used the macdeployqt from version 5.5.1. It created the framework in a restructured way. However, it is missing the A folder inside the Versions. I created a symbolic link for it pointing to folder 4. I ve xcode project for recompiling and packaging. Xcode tries to sign the A folder.
                                        codesign --force --sign 016A9E58DED20AC63F1157926166C4082C925F47 --preserve-metadata=identifier,entitlements --timestamp=none /MyApp.app/Contents/Frameworks/QtNetwork.framework/Versions/A

                                        result----
                                        bundle format unrecognized, invalid, or unsuitable
                                        Command /usr/bin/codesign failed with exit code 1.

                                        When i codesign the folder with
                                        codesign --sign '3rd Party Mac Developer Application: XXXX XXXX (R3JGXHN3B3)' --keychain ~/Library/Keychains/login.keychain ./Versions/A
                                        It works and xcode does not produce the same error but then when i submit, AppStore complains at unsigned framework at the root.

                                        Question: Why doesnot this work? how to debug it?
                                        codesign --force --sign 016A9E58DED20AC63F1157926166C4082C925F47 --preserve-metadata=identifier,entitlements --timestamp=none /MyApp.app/Contents/Frameworks/QtNetwork.framework/Versions/A

                                        1 Reply Last reply
                                        0
                                        • SGaistS Offline
                                          SGaistS Offline
                                          SGaist
                                          Lifetime Qt Champion
                                          wrote on last edited by
                                          #35

                                          What framework at the root ?

                                          Interested in AI ? www.idiap.ch
                                          Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                                          1 Reply Last reply
                                          0

                                          • Login

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular
                                          • Users
                                          • Groups
                                          • Search
                                          • Get Qt Extensions
                                          • Unsolved