MacOS High Sierra下OpenGL应用出现未知乱码权限弹窗求助

Hey there, let's dig into this strange permission dialog issue you're facing with your custom OpenGL app on macOS High Sierra. Based on the symptoms you shared—garbled text, your app's icon, no thread blocks in the debugger, no impact when clicking "Don't Allow", and a blank help window when hitting the question mark—here are the most likely causes and actionable checks:

1. Missing or Misconfigured Permission Descriptions in Info.plist #

This is the most common culprit for garbled permission dialogs. macOS requires that any permission your app requests (even accidentally) has a corresponding human-readable description in your Info.plist file. If your app's Info.plist includes a permission key like NSCameraUsageDescription, NSMicrophoneUsageDescription, or even less obvious ones like NSDesktopFolderUsageDescription—but you haven't filled in a valid string value, or the localized strings file is missing—the system will display garbled text instead.

• Check your Info.plist: Look for all keys ending with UsageDescription and ensure each has a clear, non-empty string value.
• Verify localization: Make sure your app's en.lproj/InfoPlist.strings (or other language folders) contain translated values for these permission keys. A missing entry here can also lead to garbled text.

2. Accidental Entitlements or Signature Issues #

Even if you didn't explicitly add permissions, a faulty code signature or unintended entitlements can trigger system permission checks. High Sierra is particularly strict about app signatures for non-App Store apps.

• Inspect your app's entitlements: Run this terminal command to list active entitlements:

  codesign -d --entitlements - /path/to/your/application.app
  

  Look for any unexpected entitlements (e.g., com.apple.security.device.camera) that you didn't intend to include.
• Re-sign your app: If the signature is incomplete or corrupted, re-signing might fix the issue. Use a developer ID if you have one, or a self-signed certificate:

  # Self-sign example
  codesign -s - /path/to/your/application.app
  

3. Corrupted System Caches (Launch Services or TCC Database) #

macOS relies on caches to track app permissions and metadata. When these caches get corrupted, it can lead to false permission prompts or garbled UI.

• Reset Launch Services: This refreshes how macOS identifies and indexes your app. Run in terminal:

  /System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -kill -r -domain local -domain system -domain user
  

• Reset TCC Permissions: The Transparency, Consent, and Control (TCC) database stores app permissions. Resetting it for your app will let macOS re-prompt for permissions correctly (if needed):

  tccutil reset All com.yourcompany.yourappbundleid
  

  Replace com.yourcompany.yourappbundleid with your app's actual bundle ID (found in Info.plist under CFBundleIdentifier).

4. Third-Party Software Injection or Interference #

Since you confirmed the dialog isn't from your code, it might be triggered by a third-party tool injecting into your app's process—like antivirus software, screen recorders, or performance monitoring tools.

• Test in Safe Mode: Boot your Mac into Safe Mode (hold Shift during startup) and run your app. If the dialog doesn't appear, a third-party utility is the cause. Uninstall recently added software or disable system extensions to find the culprit.

5. High Sierra-Specific System Bug #

High Sierra has a few known quirks with permission dialogs for unsigned or semi-signed apps. In some cases, the system incorrectly associates a permission request with your app due to a framework-level bug. If all other steps fail, try:

• Updating High Sierra to the latest available patch (Apple released fixes for permission-related issues in later High Sierra updates).
• Creating a fresh test user account and running your app there—this rules out user-specific cache or configuration issues.

Start with checking your Info.plist and entitlements first—those are the fastest fixes for this kind of issue. If that doesn't resolve it, move on to resetting system caches or testing in Safe Mode.

内容的提问来源于stack exchange，提问作者O'Rooney