Latest update of Rider bricks aps-environment (MAUI, iOS)?
After updating my Rider installation yesterday to the version 2025.1, I have to remove the aps-environment key from my Entitlements.plist to be able to build iOS apps inside a MAUI project. As Rider now wanted me to switch from Xcode 16.2 to Xcode 16.3, I was wondering if anything changed in that regard but I could not find anything.
Entitlements.plist: Error MT7137 : The app requests the entitlement 'aps-environment' with the value 'development', but the provisioning profile 'iOS Team Store Provisioning Profile: com.mycompany.mypp' grants it for the value 'production'.
This has worked fine before the update, now this error comes up until I remove said key from the entitlements which is no option as the app uses Push Notifications and the provisioning profile is set up correctly (as it works build with the previous Rider version).
Please sign in to leave a comment.
Hello everyone,
Thank you for providing details!
I have created a feature request on our tracker:
RIDER-126019 Entitlement 'aps-environment' error
Please upvote it to subscribe to the updates.
Thank you in advance.
Hello S Kruse ,
Thank you for reaching Rider Forum.
Could you please do the following:
Looking forward to hearing from you soon.
Did the solution work? I am running into the same error (but then the other way around, the request is for production where the profile allows only development)
Nvgogh no it did not work. For now, I removed the aps-environment from the entitlement because it is not critical to test stuff currently and we are preparing a new release of our apps.
I thought so. I also see the issue using vscode, so it must be dotnet in collaboration with the latest xcode since it started for me after all the update of xcode and the maui workload. I haven't seen any issues reported in the dotnet maui github.
And for now I will do the same as you did, remove the entitlement
As for a workaround, add this to the csproj:
<PropertyGroup><ValidateEntitlements>disable</ValidateEntitlements></PropertyGroup>However, I would suggest filing an issue in the dotnet/macios repository, and we'll help you figure this out.
Rolf the issue seems to be that Rider picks the wrong Provisioning Profile when set to automatic. If I pin it to specific profiles it seems to work. I could not reproduce the issue with VSCode (on same device) or Visual Studio (via network with this mac as host) so this seems to be a Rider problem.
I just wanted to add something that worked for me as I have run into a problem with entitlements after updating to dotnet 9 and latest Rider 2025.2.
My project has always used multiple entitlements.plist files for different environments. i.e. Entitlements-debug.plist, Entitlements-sandbox.plist, etc.
In the build settings in csproj I would set this using the
<CodesignEntitlements>setting. The files were always added using a build action of<None>and everything worked fine.After upgrading it seems like it was always using the Entitlements.plist (which is my prod settings) no matter what the
CodesignEntitlementshad in it.To fix, I renamed the Entitlements.plist to Entitlements-prod.plist so I have no default Entitlements.plist anymore.
I changed the build action to these to BundleResource and set conditional code in csproj like this
<BundleResource Include="Platforms\iOS\Entitlements-debug.plist" Condition="'$(Configuration)' == 'Debug'" />Now, the build process appears to be using the correct entitlements file and no more aps environment errors.
Hope this helps someone :)
I experience same issue under .NET 9 and Rider v2025.2.3. IN Rider v2025.1 + NET 8.0 it worked smoothly. Temporary workaround helps with disabling ValidateEntitlements. But for PROD validation fails despite explicitly Provision Profile name set. In the build log i see Provision Profile information as empty. Before it displayed proper name and signingkey.
Workaround from previous comment with BundleResource didn't help for me.
Alexey9685+jetbrains Thanks for the information. This issue is currently being tracked under RIDER-126019 Entitlement 'aps-environment' error. Please upvote and subscribe to it for further updates. I have requested the development team to prioritize it. We’ll share updates as soon as they become available.
S Kruse how do you set a specific Provisioning Profile? I tried doing that in the Properties of my iOS project on the Release build configuration, but it still picks up the wrong one. For context, I build the solution and then I use the Publish option on the iOS project to get my .ipa file
My problem is that everything was fine, but then refactored the build and solution configurations to only have “Debug” and “Release” for build configurations and now it doesn't pick up the right provisioning profile. I've done the syncing with XCode to get the certificates, etc.
Hello Florin Gheorghiu24 ,
If the issue still persists, is there a chance to know which refactorings were made? Also .csproj of the project in question would be helpful. Please upload it to the https://uploads.jetbrains.com and share the ID of the uploaded file.