Hi,

The system style are free to ignore hints in order to stay coherent with the OS guide lines so you are likely hitting that.

One possible way is to create a QProxyStyle.

@JonB thx. I input was wrong.

Looks like a build error, no ?

Are you using a pre-built version of Qt ?

After the advice from @SGaist I started to experiment a bit with settings of the build steps: problem disappeared after I did these three steps one by one (after each I checked if the problem is gone - it disappeared after the last step:

turning off QML debugging and profiling switch (default was "leave default", effective call showed CONFIG+=qml_debug now it is CONFIG-=) turning off QtQuick compiler (default was "leave default, effective call showed CONFIG+=qtquickcompiler now it is CONFIG-=) deleting shadow build folders (I do it routinely once a week or so anyway).

Now the problem is gone, I am marking the topic as "solved".

I made it work by removing this flag: Qt::WindowDoesNotAcceptFocus

hi,

I think you miss to activate HIGH DPI support in your info.plist ?

<key>NSPrincipalClass</key> <string>NSApplication</string> <key>NSHighResolutionCapable</key> <string>True</string>

Have look here

"make module-qtbase" worked!

@wraitii Thanks for information! You've probably meant libstdc++ and libc++, because libc is kinda different thing

Hi,

There's only one official compiler on macOS and it's clang coming with Xcode. There are others than you can get using macports for example but you'll be on your own in case of trouble.

As for the IDE, if you want to have a common development experience, then I'll recommend going with Qt Creator so you don't have to do big switches when changing development OSs. The interface will stay the same so you'll feel more quickly at home.

@Ilja
Super good to hear.
Thank you for the feedback.
happy programming.

Thanks for the link !

What does the debugger say ?
It can crash in many ways.

Maybe you could use a large static buffer:
char dest[1000];
and use vsnprintf, vswprintf instead.

I traced the build failure down to pyside commit eb28469e - "Fix QtQuick bindings generation". I haven't had a chance to triage the root cause but pyside builds on macOS up through the previous commit.

https://bugreports.qt.io/browse/QTBUG-57072

@wesblake Hello,
Using the information you've provided I've managed to upload my package to the appstore using Transporter, however even after inserting com.apple.application-identifier and com.apple.developer.team-identifier to my .entitlements file, I still get "Not Available for Testing" status in TestFlight.

Could you share any other entries in the entitlements file, or any other leads to resolve this issue?

If you mean that macdeployqt still gives you the same error, then that's normal. We run it before modifying these libraries.

If you want macdeployqt to not scream at these libraries, you can change the original files and put the whole path to them with -change.

Thanks for your help ! I will take a look a that, and post another thread if I have a lot of problems.