Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-141418

AssetDownloader static library is copied by the deployment process while it's not used

XMLWordPrintable

    • macOS

      AssetDownloader path is copied to the resource folder within the application package.

      From the customer:

      I found a strange folder in my Qt 6.9.3 distribution for macOS. ~/Qt/6.9.3/macos/qml/Qt/labs/assetdownloader This folder contains not the typical *.dylib but a static *.a lib and a folder named objects-RelWithDebInfo with object files. This does not harm when debugging my application on macOS. But when deploying the app and signing and notarizing the package installer with Apples tools, notarization fails due to the not signed/invalid object files. Removing the assetdownloader before calling macdeployqt solves the issue, but cmake will fail without assetdownloader.
      ----------------------
      I don’t need Qt.labs.assetdownloader at all, and my project is not based on CarConfiguratorDemo!The problem is that when I deploy the application for macOS, macdeployqt6 will copy the ../qml/Qt/labs/assetdownloader folder to the Resources folder within the application package.As the content of a macOS application package must be conform to Apple rules, there should be no object files as QmlAssetDownloaderplugin_init.cpp.o (located in folder assetdownloader/objects-RelWithDebInfo)When trying to notarize this application package (required for trusted distribution), this will fail due to the unsigned object file.

      That might be something that's copied by qt_generate_deploy_qml_app_script

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            kkohne Kai Köhne
            ali.kianian Ali Kianian
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:

                There are no open Gerrit changes