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. Qt Creator 7 MacOS permissions
Forum Updated to NodeBB v4.3 + New Features

Qt Creator 7 MacOS permissions

Scheduled Pinned Locked Moved Unsolved General and Desktop
5 Posts 2 Posters 622 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.
  • R Offline
    R Offline
    Rory_1
    wrote on last edited by
    #1

    On Mac ARM64 computers, applications run from Qt Creator on MacOS Monteray required acquiring permissions every time. This is supposed to be fixed in Qt Creator 7. In the release blog: "On macOS Qt Creator now uses the systems dark mode when setting a dark theme, and we fixed that user applications inherited access permissions from Qt Creator. If your application accesses restricted resources, this will be better reflected now while developing the application with Qt Creator."

    This does work when the application is run in release mode, but in my case, not when in debug mode. Is this something I am doing wrong, or has it not been completely fixed?

    1 Reply Last reply
    0
    • R Offline
      R Offline
      Rory_1
      wrote on last edited by
      #2

      Any help on this would be appreciated. Can you let me know if it can be reproduced?

      1 Reply Last reply
      0
      • D Offline
        D Offline
        DerReisende
        wrote on last edited by
        #3

        I do not experience the problem but you could try to sign your Qt Creator app again locally and see if this fixes the problem with inherited permissions. Code signature on macOS is sometimes strange.
        Use this command: codesign -s - --deep ~/Qt/Qt\ Creator.app

        R 1 Reply Last reply
        0
        • D DerReisende

          I do not experience the problem but you could try to sign your Qt Creator app again locally and see if this fixes the problem with inherited permissions. Code signature on macOS is sometimes strange.
          Use this command: codesign -s - --deep ~/Qt/Qt\ Creator.app

          R Offline
          R Offline
          Rory_1
          wrote on last edited by
          #4

          @DerReisende Thanks - I had tried that, and before Creator 7, it solved the problem in release mode. It does not help in Debug mode.

          1 Reply Last reply
          0
          • R Offline
            R Offline
            Rory_1
            wrote on last edited by
            #5

            Okay, I've narrowed down when proper MacOS signing is not occurring. If I build for either x86 or arm then I do not have a permissions problem, BUT when I build for both x86 and arm to create a universal binary then the resulting app is not signed. Here is the problem build setting when the qmake details are expanded:

            8a961c90-36b6-4709-b890-ddc366b48b22-image.png

            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