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. MacOS: Your app uses or references the following non-public or deprecated APIs:
Forum Updated to NodeBB v4.3 + New Features

MacOS: Your app uses or references the following non-public or deprecated APIs:

Scheduled Pinned Locked Moved Unsolved General and Desktop
7 Posts 5 Posters 984 Views 1 Watching
  • 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.
  • F Offline
    F Offline
    Francky033
    wrote on last edited by
    #1

    Hello,

    I have just proposed an application on macOS built with Qt 6.4.0 and I received a message from the technical support :

    Guideline 2.5.1 - Performance - Software Requirements

    Your app uses or references the following non-public or deprecated APIs:

    Symbols: _responsibility_get_pid_responsible_for_pid, _responsibility_spawnattrs_setdisclaim

    The use of non-public or deprecated APIs is not permitted on the App Store, as they can lead to a poor user experience should these APIs change and are otherwise not supported on Apple platforms.

    I don't understand it. How to find the modules that use these APIs _responsibility_get_pid_responsible_for_pid, _responsibility_spawnattrs_setdisclaim? I can't find any information about them.

    Thank you!

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

      Hi,

      Which modules are you using ?

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

      D 1 Reply Last reply
      0
      • SGaistS SGaist

        Hi,

        Which modules are you using ?

        D Offline
        D Offline
        danryu
        wrote on last edited by
        #3

        @SGaist I am seeing this behaviour as well with Qt 6.4.0 for macOS App Store submission.

        The app in question uses a fairly minimal Qt installation but includes QtWebView.
        (Qt is installed with aqt with args: --archives qtbase qtdeclarative qtsvg qttools --modules qtwebview)

        Let me know if I can provide further useful details.
        Project file here.

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

          Are you sure you don't have webengine getting used somehow ?

          If memory serves well, that is usually one of the main suspect for that kind of error.

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

          1 Reply Last reply
          0
          • O Offline
            O Offline
            Olivier31
            wrote on last edited by
            #5

            Same issue here with 6.4.0,

            _responsibility_get_pid_responsible_for_pid and _responsibility_spawnattrs_setdisclaim seem to located in QtCore.framework according to nm.

            1 Reply Last reply
            0
            • C Offline
              C Offline
              ChrisW67
              wrote on last edited by
              #6

              I see no direct use of these calls in the basic 6.4.0 source code.

              QTBUG-107167 refers to this issue and gives you the solution. The Qt for macOS page also refers.

              D 1 Reply Last reply
              1
              • C ChrisW67

                I see no direct use of these calls in the basic 6.4.0 source code.

                QTBUG-107167 refers to this issue and gives you the solution. The Qt for macOS page also refers.

                D Offline
                D Offline
                danryu
                wrote on last edited by
                #7

                @ChrisW67 The solution at https://bugreports.qt.io/browse/QTBUG-107167 is not effective, and was apparently closed without confirmation that it worked.
                I opened bug https://bugreports.qt.io/browse/QTBUG-109032 to address this.

                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