@AlexZhZZ See QTBUG-120196

@Christian-Ehrlicher Yeah, I'm trying to build Qt-6.6.1 from console. It looks there are some 3rdparty libraries that have Python interfaces to be built. Particularly: qtwebengine-chromium qtwebengine [46/24233] ACTION //third_party/catapult/tracing:generate_about_tracing(/opt/qt/qtwebengine/build/src/core/target_toolchain:target) FAILED: gen/content/browser/tracing/about_tracing.js gen/content/browser/tracing/about_tracing.html /home/lvision/.pyenv/shims/python3 ../../../../../src/3rdparty/chromium/third_party/catapult/tracing/bin/generate_about_tracing_contents --outdir gen/content/browser/tracing Traceback (most recent call last): File "/opt/qt/qtwebengine/src/3rdparty/chromium/third_party/catapult/common/py_vulcanize/py_vulcanize/html_module.py", line 28, in Parse parser_results = parse_html_deps.HTMLModuleParser().Parse(self.contents) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/qt/qtwebengine/src/3rdparty/chromium/third_party/catapult/common/py_vulcanize/py_vulcanize/parse_html_deps.py", line 298, in Parse return HTMLModuleParserResults(html) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/qt/qtwebengine/src/3rdparty/chromium/third_party/catapult/common/py_vulcanize/py_vulcanize/parse_html_deps.py", line 164, in __init__ self._soup = bs4.BeautifulSoup(html, 'html5lib') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/qt/qtwebengine/src/3rdparty/chromium/third_party/catapult/third_party/beautifulsoup4-4.9.3/py3k/bs4/__init__.py", line 243, in __init__ raise FeatureNotFound( bs4.FeatureNotFound: Couldn't find a tree builder with the features you requested: html5lib. Do you need to install a parser library? During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/qt/qtwebengine/build/src/core/Release/x86_64/../../../../../src/3rdparty/chromium/third_party/catapult/tracing/bin/generate_about_tracing_contents", line 14, in <module> sys.exit(generate_about_tracing_contents.Main(sys.argv[1:])) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/qt/qtwebengine/src/3rdparty/chromium/third_party/catapult/tracing/tracing_build/generate_about_tracing_contents.py", line 32, in Main load_sequence = vulcanizer.CalcLoadSequenceForModuleNames(names) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/qt/qtwebengine/src/3rdparty/chromium/third_party/catapult/common/py_vulcanize/py_vulcanize/project.py", line 146, in CalcLoadSequenceForModuleNames modules = [self.loader.LoadModule(module_name=name, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/qt/qtwebengine/src/3rdparty/chromium/third_party/catapult/common/py_vulcanize/py_vulcanize/resource_loader.py", line 145, in LoadModule m.Parse(excluded_scripts) File "/opt/qt/qtwebengine/src/3rdparty/chromium/third_party/catapult/common/py_vulcanize/py_vulcanize/html_module.py", line 30, in Parse raise Exception('While parsing %s: %s' % (self.name, str(ex))) Exception: While parsing tracing.ui.extras.about_tracing.about_tracing: Couldn't find a tree builder with the features you requested: html5lib. Do you need to install a parser library? [95/24233] CXX obj/third_party/cld_3/src/src/cld_3/nnet_language_identifier.o ninja: build stopped: subcommand failed. make[2]: *** [src/core/CMakeFiles/QtWebEngineCore_Release_x86_64.dir/build.make:77: src/core/Release/x86_64/QtWebEngineCore.stamp] Error 1 make[2]: Leaving directory '/opt/qt/qtwebengine/build' make[1]: *** [CMakeFiles/Makefile2:1472: src/core/CMakeFiles/QtWebEngineCore_Release_x86_64.dir/all] Error 2 make[1]: Leaving directory '/opt/qt/qtwebengine/build' make: *** [Makefile:149: all] Error 2

For the future generations of humanity: QJniObject toast = QJniObject::callStaticObjectMethod( "android/widget/Toast", "makeText", "(Landroid/content/Context;Ljava/lang/CharSequence;I)" "Landroid/widget/Toast;", QNativeInterface::QAndroidApplication::context(), displayText.object<jstring>(), timeout ); if (toast.isValid()) { qDebug() << "Toast is valid"; toast.callMethod<void>("show"); } else { qDebug() << "Toast JNI object not valid"; }

I've submitted a Qt bug report for this: https://bugreports.qt.io/browse/QTBUG-119614 "SSL initialization is around 10 to 100 times slower in Qt 6"

@Tiny-Leaf Try the following code. The length of three segments should be same. drawLine(ctx, 50, 50, 150, 50); drawLine(ctx, 150, 50, 50, 50); drawLine(ctx, 150, 100, 50, 100); function drawLine(ctx, x1, y1, x2, y2) { ctx.beginPath() ctx.moveTo(x1, y1) ctx.lineTo(x2, y2) ctx.stroke() } BTW: you may somehow avoid to draw a line twice if possible. It is not efficient.

I must answer my own question. Sometimes I miss the obvious. A Settings.bundle is simply a resource and must be copied to the Resources. Since Apple changed the directory chirarchy in the app bundle, all Resources are files or directories in the root directory. After I realized this, it was simple. Here is a small excerpt of my CMakeLists.txt file: set(settings_bundle "Settings.bundle") qt_add_executable(tpanel MANUAL_FINALIZATION ${PROJECT_SOURCES} "${settings_bundle}" ) target_sources(tpanel PRIVATE "${settings_bundle}") set_source_files_properties(${settings_bundle} PROPERTIES MACOSX_PACKAGE_LOCATION Resources) The above code assume, that the Settings.bundle is in the root of the distribution. If this is not the case, then the relative path must be defined as part of the variable settings_bundle. That's it!

Turns out I was using an old version of crashpad that was explicitly adding in those old libs in the .pri file.

Then why don't you resize the widget item created to fit the view ?

For anyone coming across this thread, the answer is... tl;dr: You need to add the runFullTrust capability. With Qt 5, there was support for UWP apps. This made it possible for Windows apps to be delivered through the Microsoft Store. (This is how my app was built and delivered.) Then Microsoft opened up the Microsoft Store for Win32 apps too; i.e. standard desktop apps. As a developer you have a choice of either packaging your own installer and delivering that through the Microsoft Store, or just your app, letting Microsoft Store handle installation. The latter option behaves more like the handling of a UWP app and Microsoft handles the code-signing certificate for you. As a consequence, Qt decided to drop support for UWP as of Qt 6. This was done with no public notification to the Qt community 🤬, with just a message on the Qt development mailing list. I eventually found this out via a convoluted bug report. What Qt themselves did not realise is that if you submit a Win32 app via the Microsoft Store, because it is a desktop app and does not sit nicely in a sandbox like a UWP app, you need to add the runFullTrust capability. If you don't do this, you get the weird behaviour of the application window opening in a separate window described above. However be aware that when you add runFullTrust Microsoft will require you to justify why your app needs access to the whole Windows system. I was able to pass certification with a message along the lines of "My app is built with the Qt framework that only generates Win32 apps. My app does not operate outside the sandbox and behaves nicely." One more gotcha if you're going this route. The path QStandardPaths::AppDataLocation was different for UWP apps than Win32 apps. The following only applies if you had a UWP app in Qt 5 and stored data there as the path will be wrong for your Win32 app in Qt 6. To fix this, I use the following: https://gist.github.com/paulmasri/75dcd3386a4e8eaf705058240ef547d1

@Enayat I see mediaFormat mentioned in the doc for MediaRecorder but the documentation appears to be incomplete. Perhaps dig into this a bit?

@Axel-Spoerl Yes, I have but not this one. Thank you for the link!!