Share via

Adding Entitlements.plist crashes the IOS publish

Jai Holloway 65 Reputation points
2026-05-06T09:44:16.3966667+00:00

I have just upgraded a .NET 8 MAUI app to .NET 10 and one of the requirements is that I have an Entitlements.plist file for access to the keychain.

My publish is failing with a missing ResourceRule.plist file, but I followed all the instructions of adding an entitlements.plist file. As a note, I created a new app and added Entitlements.plist to that, with the same entitelement and it crashed on the publish too.

I cannot publish and this is now urgent. Any help would be appreciated.

Developer technologies | .NET | .NET Multi-platform App UI

2 answers

Sort by: Most helpful
  1. Michael Le (WICLOUD CORPORATION) 11,325 Reputation points Microsoft External Staff Moderator
    2026-05-11T08:43:44.0566667+00:00

    Hello @Jai Holloway ,

    Thank you for the update. I’m glad you were able to get the IPA installed and the app running.

    I already found the Stack Overflow thread that suggested moving the keychain-access-groups entry to Info.plist and saw your comment on that thread. However, I just want to clarify for future readers that I don’t think Info.plist is what actually grants the keychain entitlement.

    Based on the MAUI and Apple documentation, keychain-access-groups is an entitlement and is normally applied through Entitlements.plist during code signing. So my suspicion is that the previous keychain-access-groups entry in Entitlements.plist may have been unnecessary or mismatched for the provisioning profile/device deployment. After it was removed from Entitlements.plist, it was no longer embedded as a signing entitlement.

    That said, since your app is now running, it sounds like the entitlement/signing issue is resolved for your current deployment path.

    Thank you for your time in troubleshooting this issue.

    Was this answer helpful?

    0 comments No comments

  2. Michael Le (WICLOUD CORPORATION) 11,325 Reputation points Microsoft External Staff Moderator
    2026-05-07T11:13:59.5433333+00:00

    Hello @Jai Holloway ,

    So I have looked through what you have shared on the other thread, and I do have some suspicion something is still referencing ResourceRules.plist during bundle resource preparation. To confirm this, can you please share:

    1. Your full .csproj, or at least every section containing:
          ResourceRules
          CodesignResourceRules
          BundleResource
          MauiAsset
          None
          Content
          CodesignEntitlements
      
    2. A “find in files” screenshot for:
          ResourceRules
      
          CodesignResourceRules
      
      You can use the Code Search in VS with Ctrl + T or Find with Ctrl + Shift + F and make sure to check all files in the project.User's image User's image
    3. And check your project properties to make sure the custom resources rules is defined.User's image
    4. Also, because the error path is under: ~/Library/Caches/maui/PairToMac/Builds/, please try clearing the Pair to Mac build cache on the mac:
          rm -rf ~/Library/Caches/maui/PairToMac/Builds/
      
      If you previously built Xamarin/iOS projects on the same mac, also check whether this exists and clear it:
          rm -rf ~/Library/Caches/Xamarin/mtbs/builds/
      
      Then disconnect/reconnect Pair to Mac from Visual Studio, delete bin and obj locally, and try archive again.

    Thank you for your time.

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.