Problème de publication sur l'Appstore

[Tazooou]

Bonjour à tous,

Je suis presque à la fin de l’upload de mon application sur l’appstore mais je rencontre un soucis lors de l’upload sur l’appstore connect.

Quand je clique sur Distribute, je reçois au bout de quelques minutes un message d’erreur sur la signature de l’application et de certains chemins.

Après avoir vérifié les informations, j’ai fait un clean et j’ai relancé le build mais j’ai toujours la même erreur …

Ils conseillent de « delete the “build” directory in the Finder » mais de quel dossier exactement il parle ?

Si quelqu’un peut m’aider là dessus, ça serait chouette. Ma bière est au frais dans le frigo en attendant de fêter ma première publication sur l’appstore et j’ai peur qu’elle trouve le temps long …

Asset validation failed
Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “Runner.app/Frameworks/App.framework/App” is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose “Clean All” in Xcode, delete the “build” directory in the Finder, and rebuild your release target. For more information, please consult Code Signing Resources | Apple Developer Forums. (ID: 8e358b1a-9aa4-44c1-91cb-d55472940a91)
Asset validation failed
Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “Runner.app/Frameworks/Flutter.framework/Flutter” is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose “Clean All” in Xcode, delete the “build” directory in the Finder, and rebuild your release target. For more information, please consult Code Signing Resources | Apple Developer Forums. (ID: e02a06fc-c36d-4773-80bf-5c01d01d7495)

Asset validation failed
Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “Runner.app/Frameworks/flutter_native_splash.framework/flutter_native_splash” is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose “Clean All” in Xcode, delete the “build” directory in the Finder, and rebuild your release target. For more information, please consult Code Signing Resources | Apple Developer Forums. (ID: 601c919f-6d78-4ea2-b2e3-660b136e7bdb)

Asset validation failed
Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “Runner.app/Frameworks/flutter_secure_storage.framework/flutter_secure_storage” is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose “Clean All” in Xcode, delete the “build” directory in the Finder, and rebuild your release target. For more information, please consult Code Signing Resources | Apple Developer Forums. (ID: b57e0ea5-bc5a-42eb-bdb4-2854edc47fe3)

Asset validation failed
Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “Runner.app/Frameworks/isar_flutter_libs.framework/isar_flutter_libs” is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose “Clean All” in Xcode, delete the “build” directory in the Finder, and rebuild your release target. For more information, please consult Code Signing Resources | Apple Developer Forums. (ID: 4eb1bb10-98d8-4daa-8437-f6dc3635519a)

Asset validation failed
Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “Runner.app/Frameworks/location.framework/location” is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose “Clean All” in Xcode, delete the “build” directory in the Finder, and rebuild your release target. For more information, please consult Code Signing Resources | Apple Developer Forums. (ID: 865e3785-4356-4967-bedd-7daf07a780cc)

Asset validation failed
Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “Runner.app/Frameworks/path_provider_foundation.framework/path_provider_foundation” is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose “Clean All” in Xcode, delete the “build” directory in the Finder, and rebuild your release target. For more information, please consult Code Signing Resources | Apple Developer Forums. (ID: 3043f76d-2e1f-45d7-98b9-904bbd372d0d)

Asset validation failed
Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “Runner.app/Frameworks/shared_preferences_foundation.framework/shared_preferences_foundation” is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose “Clean All” in Xcode, delete the “build” directory in the Finder, and rebuild your release target. For more information, please consult Code Signing Resources | Apple Developer Forums. (ID: 35c2a364-04ab-4c96-9362-c154964b8a2d)

Asset validation failed
Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “Runner.app/Runner” is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose “Clean All” in Xcode, delete the “build” directory in the Finder, and rebuild your release target. For more information, please consult Code Signing Resources | Apple Developer Forums. (ID: e6581f69-3c17-4a42-9c03-74ebd0b23c3f)

[Tazooou]

J’ai essayé de mettre à jour des recommandations de Xcode sur mon projet et je me retrouve maintenant avec une erreur de compilation :

Sandbox: rsync.samba(88275) deny(1) file-write-create /Users/kevinyard/Library/Developer/Xcode/DerivedData/Runner-aepaprauoslerxenxgkqerrzjfqk/Build/Products/Release-iphonesimulator/XCFrameworkIntermediates/isar_flutter_libs/.libisar.a.HSmxb3

Du coup, j’ai modifié mes réglages dans le build Setting en passant tout à non sur le user script sandboxing mais j’ai toujours la même erreur de compilation :

Help

[Quentin]

Salut @Tazooou,

Ton problème vient peut être du certificat de distribution Apple pour publier ton app. J’espère que tu trouveras la solution ici.

[Tazooou]

Suite au coaching d’hier soir, j’ai remis à jour mon dossier iOS. Il y avait quelques changements mais rien de fou. Mon application se recompile bien sans problème.
J’ai retenté un distribute mais j’ai toujours le même problème de signature.
J’ai tenté de jouer avec les signatures dans le build setting mais ca n’a rien donné :

Je continue d’investiguer …

[Tazooou]

Je me suis rendu compte d’une chose bizarre dans l’App Store Connect. J’avais deux identifiants enregistrés dont celui de l’appstore oO et deux applications possédant chacune l’un de deux certificats. J’ai supprimé la mauvaise application pour ne garder que celle avec le bon certificat mais je n’ai pas réussi à supprimer le mauvais certificat.
Lorsque j’ai retenté une validation, j’ai remarqué que Xcode utilisait pour la signature le mauvais certificat.

Et j’ai vu que je pouvais en sélectionner un sur l’écran avant la distribution :

J’ai relancé avec le bon certificat avec un clean juste avant et toujours la même erreur …

[Tazooou]

J’ai recommencé la manip de supprimer le dossier iOS et de le regénérer via le flutter create . pour supprimer les références au mauvais identifiant mais il reprend systématiquement la mauvaise référence sur le fichier project.pbxproj :

Quelqu’un sait où Flutter se source pour retrouver ce certificat ?

[Tazooou]

Hello tout le monde,
J’ai finalement réussi à recréer un dossier iOS sans le mauvais bundle identifier.
En changeant les deux références sur les fichiers build.graddle et MainActivity.kt qui sont normalement dédiés à Android, le nouveau dossier iOS ne contenait plus que le bon bundle id.
J’ai refait un clean sur VSCode et Xcode relançait en passant par Xcode et par le transporter et rien ne change j’ai toujours le même problème de signature.
Lorsque j’ouvre la target Pods, je peux voir toutes mes dépendances et j’ai certains paramètres qui me posent problèmes :

Le bundle identifier n’est pas le mien et grisé, pas de team, pas de signature automatique, …
Est-ce que c’est normal ?

[Tazooou]

J’ai vu également que Xcode me recommandait une mise à jour des settings et justement en rapport avec la signature mais si j’accepte l’ensemble des recommandations mon projet ne compile plus.
Est ce que je devrais en sélectionner que certains ?

[Tazooou]

Hello @Quentin,
Impossible pour le moment d’effectuer cette manipulation. J’ai bien un certificat de distribution et je l’ai installé sur ma machine en passant par Xcode. Mais quand je tente de créer un profil de distribution, je sélectionne distribution AppStore Connect, je sélectionne l’app id et il me demande de créer un nouveau certificat en ignorant celui qui existe …

[Tazooou]

Le soucis venait bien de mes certificats. J’ai créer un certificat iOS distribution que j’ai installé dans mon trousseau d’accès de mon Mac et tous mes problèmes de signatures ont disparus

1er étape : Demander un certificat à une autorité de certification via l’application Trousseau d’accès de votre Mac
2ème étape : Aller sur l’appstore connect et générer un certificat de distribution iOS App Store et Ad Hoc
3ème étape : Enregistrer le certificat généré sur le trousseau de clé de votre Mac

Le lien qui explique tous les détails (Je me suis arrêté juste aux premières étapes jusqu’à l’enregistrement du certificat sur mon Mac): https://support.mobincube.com/hc/fr/articles/200511933-Comment-obtenir-le-fichier-p12-et-le-profil-Provisioning-pour-publier-une-application-sur-l-App-Store