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.