Where/How to populate information for Problem Report?
-
-
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.
-
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.
@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.
-
Did you check the content of the generated .plist file ?
-
@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.
@SPlatten IIRC if you don't provide one via
QMAKE_INFO_PLIST
than you will only ever find the binary variant inside the generated AppBundleBut you can open that one via Xcode. Xcode should be able to parse it and show it in a human readable format
-
@SPlatten IIRC if you don't provide one via
QMAKE_INFO_PLIST
than you will only ever find the binary variant inside the generated AppBundleBut you can open that one via Xcode. Xcode should be able to parse it and show it in a human readable format
@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.
-
Do you have an info.plist file in your sources ?
-
@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.
@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 directorylet me show you a picture:

-
@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 directorylet me show you a picture:

@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-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.
@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 AppBundleBut 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-clangconfusingly named
Info.plist.app
Copy that one to your project folder, rename it, and let QMake_Info__plist point to it.
-
@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 AppBundleBut 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-clangconfusingly named
Info.plist.app
Copy that one to your project folder, rename it, and let QMake_Info__plist point to it.
@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-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.