Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Where/How to populate information for Problem Report?
Forum Update on Monday, May 27th 2025

Where/How to populate information for Problem Report?

Scheduled Pinned Locked Moved Unsolved General and Desktop
14 Posts 3 Posters 1.3k Views
  • 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.
  • SPlattenS Offline
    SPlattenS Offline
    SPlatten
    wrote on last edited by
    #1

    I have a problem report for an application I'm developing on MacBook Pro Apple M1. The report contains a lot of information some of which is not populated:

    Identifier:    com.yourcompany.XMLMPAM
    Version:       ????
    

    How do I supply the information for these?

    Kind Regards,
    Sy

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

      Hi,

      I would venture that some of them are read out of your application's .plist file which is generated for you by default. The version of the application you can define in your .pro file.

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

      SPlattenS 1 Reply Last reply
      1
      • SGaistS SGaist

        Hi,

        I would venture that some of them are read out of your application's .plist file which is generated for you by default. The version of the application you can define in your .pro file.

        SPlattenS Offline
        SPlattenS Offline
        SPlatten
        wrote on last edited by SPlatten
        #3

        @SGaist , thank you, like:

        VERSION_MAJOR = 1
        VERSION_MINOR = 2
        VERSION_BUILD = 1
        VERSION = $${VERSION_MAJOR}.$${VERSION_MINOR}.$${VERSION_BUILD}
        QMAKE_TARGET_BUNDLE_PREFIX = com.syberdynesystems
        

        After modifying there .pro file, this is a copy of the output:

        Process:               XMLMPAM [10715]
        Path:                  /Users/USER/*/XMLMPAM.app/Contents/MacOS/XMLMPAM
        Identifier:            com.syberdynesystems.XMLMPAM
        Version:               ???
        Code Type:             ARM-64 (Native)
        Parent Process:        Exited process [10716]
        User ID:               501
        
        Date/Time:             2022-08-16 08:06:31.8711 +0100
        OS Version:            macOS 12.5 (21G72)
        Report Version:        12
        Anonymous UUID:        FBBB437B-FB50-D3BE-66D6-752C0698B11B
        
        Sleep/Wake UUID:       186467C9-1ECA-4E19-970F-893DEAF10D09
        
        Time Awake Since Boot: 3100 seconds
        Time Since Wake:       2409 seconds
        
        System Integrity Protection: enabled
        
        Crashed Thread:        0  Dispatch queue: ls-notificationxpcq
        
        Exception Type:        EXC_CRASH (SIGABRT)
        Exception Codes:       0x0000000000000000, 0x0000000000000000
        Exception Note:        EXC_CORPSE_NOTIFY
        

        As you can see Identifier has now been set-up. But version has not.

        Kind Regards,
        Sy

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

          Did you check the content of the generated .plist file ?

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

          SPlattenS 1 Reply Last reply
          0
          • SGaistS SGaist

            Did you check the content of the generated .plist file ?

            SPlattenS Offline
            SPlattenS Offline
            SPlatten
            wrote on last edited by
            #5

            @SGaist Where would I find that file? I've searched the entire project folder including the build folders and I don't see any .plist files.

            Kind Regards,
            Sy

            J.HilkJ 1 Reply Last reply
            0
            • SPlattenS SPlatten

              @SGaist Where would I find that file? I've searched the entire project folder including the build folders and I don't see any .plist files.

              J.HilkJ Offline
              J.HilkJ Offline
              J.Hilk
              Moderators
              wrote on last edited by
              #6

              @SPlatten IIRC if you don't provide one via QMAKE_INFO_PLIST than you will only ever find the binary variant inside the generated AppBundle

              But you can open that one via Xcode. Xcode should be able to parse it and show it in a human readable format


              Be aware of the Qt Code of Conduct, when posting : https://forum.qt.io/topic/113070/qt-code-of-conduct


              Q: What's that?
              A: It's blue light.
              Q: What does it do?
              A: It turns blue.

              SPlattenS 1 Reply Last reply
              1
              • J.HilkJ J.Hilk

                @SPlatten IIRC if you don't provide one via QMAKE_INFO_PLIST than you will only ever find the binary variant inside the generated AppBundle

                But you can open that one via Xcode. Xcode should be able to parse it and show it in a human readable format

                SPlattenS Offline
                SPlattenS Offline
                SPlatten
                wrote on last edited by SPlatten
                #7

                @J-Hilk said in Where/How to populate information for Problem Report?:

                QMAKE_INFO_PLIST

                Thank you, googled this, but not clear how to use it, must found this:

                http://www.bim-times.com/qt/Qt-5.11.1/qtdoc/platform-notes-ios.html

                Reading now.... I tried adding:

                ios {
                    QMAKE_INFO_PLIST = info.plist
                }
                

                To my .pro file then ran qmake, clean and Build, I still can't see any .plist files.

                Kind Regards,
                Sy

                J.HilkJ 1 Reply Last reply
                1
                • SGaistS Offline
                  SGaistS Offline
                  SGaist
                  Lifetime Qt Champion
                  wrote on last edited by
                  #8

                  Do you have an info.plist file in your sources ?

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

                  SPlattenS 1 Reply Last reply
                  0
                  • SGaistS SGaist

                    Do you have an info.plist file in your sources ?

                    SPlattenS Offline
                    SPlattenS Offline
                    SPlatten
                    wrote on last edited by
                    #9

                    @SGaist , there are no .plist files in the project folder or any of its sub-folders which includes the build folders.

                    Kind Regards,
                    Sy

                    1 Reply Last reply
                    0
                    • SPlattenS SPlatten

                      @J-Hilk said in Where/How to populate information for Problem Report?:

                      QMAKE_INFO_PLIST

                      Thank you, googled this, but not clear how to use it, must found this:

                      http://www.bim-times.com/qt/Qt-5.11.1/qtdoc/platform-notes-ios.html

                      Reading now.... I tried adding:

                      ios {
                          QMAKE_INFO_PLIST = info.plist
                      }
                      

                      To my .pro file then ran qmake, clean and Build, I still can't see any .plist files.

                      J.HilkJ Offline
                      J.HilkJ Offline
                      J.Hilk
                      Moderators
                      wrote on last edited by J.Hilk
                      #10

                      @SPlatten
                      ok, do you compile for MacOS or for iOS ?

                      ios { // iOS ONLY
                      
                      }
                      
                      macx { //MAC OS ONLY
                      
                      }
                      

                      2ndly, I said: you will only ever find the binary variant inside the generated AppBundle this is true for macOS builds, iOS builds should generate an Xcode project files and a info.plist file in the build directory

                      let me show you a picture:
                      1d9f4212-e64c-4ad3-a99f-75ea51862080-image.png ![0_1660803472171_5bd40c08-45b5-4c9d-ba29-7c6ed3f48cf2-image.png](Uploading 100%)
                      9016dfd8-e60e-45cd-ace3-4da893e1ef5d-image.png


                      Be aware of the Qt Code of Conduct, when posting : https://forum.qt.io/topic/113070/qt-code-of-conduct


                      Q: What's that?
                      A: It's blue light.
                      Q: What does it do?
                      A: It turns blue.

                      SPlattenS 1 Reply Last reply
                      2
                      • J.HilkJ J.Hilk

                        @SPlatten
                        ok, do you compile for MacOS or for iOS ?

                        ios { // iOS ONLY
                        
                        }
                        
                        macx { //MAC OS ONLY
                        
                        }
                        

                        2ndly, I said: you will only ever find the binary variant inside the generated AppBundle this is true for macOS builds, iOS builds should generate an Xcode project files and a info.plist file in the build directory

                        let me show you a picture:
                        1d9f4212-e64c-4ad3-a99f-75ea51862080-image.png ![0_1660803472171_5bd40c08-45b5-4c9d-ba29-7c6ed3f48cf2-image.png](Uploading 100%)
                        9016dfd8-e60e-45cd-ace3-4da893e1ef5d-image.png

                        SPlattenS Offline
                        SPlattenS Offline
                        SPlatten
                        wrote on last edited by SPlatten
                        #11

                        @J-Hilk , thank you, I am building and testing on iMAC and MacBook Pro so macOS is the correct OS. Will make change now.

                        When rebuilding I now see in the Issues:

                        :-1: warning: Could not resolve Info.plist: 'info.plist'. Check if QMAKE_INFO_PLIST points to a valid file.
                        

                        This is with:

                        macx {
                            QMAKE_INFO_PLIST = info.plist
                        }
                        

                        In my .pro file.

                        Kind Regards,
                        Sy

                        J.HilkJ 1 Reply Last reply
                        0
                        • SPlattenS SPlatten

                          @J-Hilk , thank you, I am building and testing on iMAC and MacBook Pro so macOS is the correct OS. Will make change now.

                          When rebuilding I now see in the Issues:

                          :-1: warning: Could not resolve Info.plist: 'info.plist'. Check if QMAKE_INFO_PLIST points to a valid file.
                          

                          This is with:

                          macx {
                              QMAKE_INFO_PLIST = info.plist
                          }
                          

                          In my .pro file.

                          J.HilkJ Offline
                          J.HilkJ Offline
                          J.Hilk
                          Moderators
                          wrote on last edited by
                          #12

                          @SPlatten well, does QMAKE_INFO_PLIST point to a valid info.plist file ? :D

                          @J-Hilk said in Where/How to populate information for Problem Report?:

                          @SPlatten IIRC if you don't provide one via QMAKE_INFO_PLIST than you will only ever find the binary variant inside the generated AppBundle

                          But you can open that one via Xcode. Xcode should be able to parse it and show it in a human readable format

                          I should have added here, the info.plist file you find inside the appbundle is in binary format. Thats why QtCreator can't but Xcode can interpret it.
                          the file QMAKE_INFO_PLIST points to should/must be the human readable format one.

                          I used to create my own info.plist file via Xcode and include that then in QtCreator.

                          But I took the time to research where Qt has the templates stowed. For me, I found it here:
                          /.../Qt/5.15.10/clang_64/mkspecs/macx-clang

                          confusingly named Info.plist.app

                          Copy that one to your project folder, rename it, and let QMake_Info__plist point to it.


                          Be aware of the Qt Code of Conduct, when posting : https://forum.qt.io/topic/113070/qt-code-of-conduct


                          Q: What's that?
                          A: It's blue light.
                          Q: What does it do?
                          A: It turns blue.

                          SPlattenS 1 Reply Last reply
                          1
                          • J.HilkJ J.Hilk

                            @SPlatten well, does QMAKE_INFO_PLIST point to a valid info.plist file ? :D

                            @J-Hilk said in Where/How to populate information for Problem Report?:

                            @SPlatten IIRC if you don't provide one via QMAKE_INFO_PLIST than you will only ever find the binary variant inside the generated AppBundle

                            But you can open that one via Xcode. Xcode should be able to parse it and show it in a human readable format

                            I should have added here, the info.plist file you find inside the appbundle is in binary format. Thats why QtCreator can't but Xcode can interpret it.
                            the file QMAKE_INFO_PLIST points to should/must be the human readable format one.

                            I used to create my own info.plist file via Xcode and include that then in QtCreator.

                            But I took the time to research where Qt has the templates stowed. For me, I found it here:
                            /.../Qt/5.15.10/clang_64/mkspecs/macx-clang

                            confusingly named Info.plist.app

                            Copy that one to your project folder, rename it, and let QMake_Info__plist point to it.

                            SPlattenS Offline
                            SPlattenS Offline
                            SPlatten
                            wrote on last edited by SPlatten
                            #13

                            @J-Hilk Sorry for the long delay, I've been busy with other projects and now returning to this, still getting:

                            :-1: warning: Could not resolve Info.plist: 'info.plist'. Check if QMAKE_INFO_PLIST points to a valid file.
                            

                            Why is this an issue, what causes it?

                            [Edit] I commented out:

                            #macx {
                            #    QMAKE_INFO_PLIST = info.plist
                            #}
                            

                            From the .pro file, cleaned and rebuilt, no more problems.

                            Kind Regards,
                            Sy

                            J.HilkJ 1 Reply Last reply
                            1
                            • SPlattenS SPlatten

                              @J-Hilk Sorry for the long delay, I've been busy with other projects and now returning to this, still getting:

                              :-1: warning: Could not resolve Info.plist: 'info.plist'. Check if QMAKE_INFO_PLIST points to a valid file.
                              

                              Why is this an issue, what causes it?

                              [Edit] I commented out:

                              #macx {
                              #    QMAKE_INFO_PLIST = info.plist
                              #}
                              

                              From the .pro file, cleaned and rebuilt, no more problems.

                              J.HilkJ Offline
                              J.HilkJ Offline
                              J.Hilk
                              Moderators
                              wrote on last edited by
                              #14

                              Hi @SPlatten , don't worry, I was away too :D

                              anyway usually its Info.plist not info.plist should technically not matter on macOS but the qmake tool is handwritten and my be case sensitive


                              Be aware of the Qt Code of Conduct, when posting : https://forum.qt.io/topic/113070/qt-code-of-conduct


                              Q: What's that?
                              A: It's blue light.
                              Q: What does it do?
                              A: It turns blue.

                              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