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 9.9k 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.
  • 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
                  • S Offline
                    S Offline
                    SherifOmran
                    wrote on last edited by
                    #36
                    • Previous problem was solved and i can now sign the app. The following link, helped me to solve it.
                      [link Signing problem due to WWDR certificate](link https://www.reddit.com/r/iOSProgramming/comments/45siza/this_certificate_has_an_invalid_issuer/)

                    Current Issue is the following:
                    The framework folder has version folder and inside the version folder there is folder called 4. This 4 must be changed into A for apple to accept it. If we change it to A, the app will crash. This is even not integrated in macdeloyqt 5.5.

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

                      In that case change the folder to A and call install_name_tool to fix the paths your application dependencies.

                      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
                        #38

                        Now i could create an archive that is correctly signed with Xcode and if i open the archive and see the content and run the app, it runs. Notice that i ve put both frameworks 4 and A. When i export to generate a package to submit for appstore and submit it. It gets rejects. If i install the application locally, using otool, i see that the app links to frameworks that exist in /usr/..../ folders. But i managed to get the frameworks copied to the package but it still does not run. I get kill 9.

                        -- Report --
                        To clarify, the app fails to launch as it is linking to frameworks that are missing.
                        The frameworks that are missing are:
                        '/usr/local/opt/openssl/lib/libcrypto.1.0.0.dylib'
                        '/usr/local/opt/openssl/lib/libssl.1.0.0.dylib'
                        '/usr/local/opt/qt/lib/QtCore.framework'
                        '/usr/local/opt/qt/lib/QtGui.framework'
                        '/usr/local/opt/qt/lib/QtNetwork.framework'
                        '/usr/local/opt/qt/lib/QtSql.framework'

                        Best Mac OS X development practices suggest using (in order)

                        @executable_path/
                        @loader_path/
                        @rpath/

                        For more information about linking frameworks, please see the following documents:

                        • Run-Path Dependent Libraries section of Dynamic Library Programming Topics
                        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