macOS builds without an Xcode project end up with a broken code signature (Apple.Core edits the .app after Unity signs it)

Ouverte
#132 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
55/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
Active
Stack technique
csharp, macos, unity

Piste de recherche

Start with AppleBuild.OnPostProcessBuild and the Info.plist, frameworks, and entitlements steps described in the issue; check how the build target and Xcode project setting are detected. Reproduce with a plain macOS .app and run codesign --verify --deep --strict --verbose=2 on it. Done means the resulting app verifies successfully and follows the issue’s expected handling of settings, bundles, and signing.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

bug Plugin-in - Core

Describe the bug
When building for macOS with "Create Xcode Project" off (a plain .app, e.g. for Steam), AppleBuild.OnPostProcessBuild changes the .app after Unity has already signed it, and nothing signs it again:

  • Automate Info.plist rewrites Contents/Info.plist (adds ITSAppUsesNonExemptEncryption, plus LSMinimumSystemVersion when Apple Build Settings has a minimum macOS version).
  • The frameworks step copies AppleCoreNativeMac.bundle, GameKitWrapper.bundle and their .dSYM folders into Contents/PlugIns.
  • Automate Entitlements writes <Product Name>.entitlements next to the .app, where nothing uses it.

In one of our Steam builds, the Info.plist hash stored in the main executable's ad-hoc signature no longer matches Contents/Info.plist, and _CodeSignature/CodeResources lists every bundle in Contents/PlugIns except AppleCoreNativeMac.bundle and GameKitWrapper.bundle.

To Reproduce

  1. Project with Apple.Core and Apple.GameKit, Automate Info.plist and Automate Entitlements on (the defaults).
  2. Build for macOS with Create Xcode Project off.
  3. Run codesign --verify --deep --strict --verbose=2 on the built .app. It fails.

Expected behavior
The .app Unity produced stays validly signed. The Info.plist keys and the entitlements file are App Store settings a plain .app can't use, so skip them in this case (or apply them before Unity signs). Keep .dSYM folders out of Contents/PlugIns, and re-sign the .app after copying the plug-in bundles into it.

Environment
Unity 6000.6, macOS Standalone (Apple Silicon), Create Xcode Project off. Seen with Apple.Core 3.2.0 / Apple.GameKit 4.0.1; the code is unchanged in 3.3.0 / 4.1.0 (27.0, ffe6174) and on main (96e4a04).

Additional context
What we patch into our embedded copy:

bool isPlainMacApp = buildTarget == BuildTarget.StandaloneOSX && !AppleNativeLibraryUtility.IsXcodeProjectGeneratedForMac;
// skip the Info.plist and entitlements regions when isPlainMacApp, then after the finalize step:
if (isPlainMacApp)
{
    // runs /usr/bin/codesign --force --sign - "<app>" (ad-hoc, the way Unity signed it)
    ResignPlainMacApp(generatedProjectPath);
}
Langage dominant
C#
Étoiles
1k
Forks
257
Métriques de merge des PR
Aucune PR mergée en 30 j

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de apple/unityplugins

Toutes les issues de apple/unityplugins

Issues similaires

Plus d'issues C#

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.