Xcode 16 saves profiles in different folder and Rider doesn't see them

Hello, I just updated my Mac to MacOs 15.0.1 with new XCode 16 and I have the same problem. 

Hi, I have the same problem, same versions Mac OS 15.0.1 and XCode 16.

same problem here

Hello Davide Copulutti , Daniele Liguori , Constantin Madalin, M Wannenwetsch , 

Thank you for reaching the Rider Forum.

Could you please each share the Rider version you are using? 

It seems a lot like a bug which has been already fixed: 

RIDER-115516 Can't deploy iOS app with Xcode 16 and iOS 18 Beta because of profiler's location

Could you please try Rider EAP? 

Hi Anna Morozyuk ,

My Rider version is:

JetBrains Rider 2024.2.7
Build #RD-242.23726.100, built on October 22, 2024
Licensed to Aton S.p.A. Società Benefit / Davide Copulutti
Subscription is active until June 11, 2025.
Runtime version: 21.0.4+13-b509.26 aarch64 (JCEF 122.1.9)
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Toolkit: sun.lwawt.macosx.LWCToolkit
macOS 15.0.1
.NET Core v8.0.4 ARM64 (Server GC)
GC: G1 Young Generation, G1 Concurrent GC, G1 Old Generation
Memory: 2048M
Cores: 8
Metal Rendering is ON
Registry:
 ide.experimental.ui=true
 i18n.locale=
Non-Bundled Plugins:
 com.intellij.plugins.visualstudioformackeymap (242.20224.159)
 com.intellij.resharper.HeapAllocationsViewer (2024.2.0)
 color.scheme.Visual Studio Light (1.4.0)
 com.jetbrains.rider.android (242.23726.100)
 com.intellij.ml.llm (242.23726.20)
 com.intellij.resharper.azure (4.2.4)
 

Do you have already fix it?

Thank you.

Hello Anna Morozyuk ,

the link to the bug does not work for me. 

I have tested it with the current version 2024.3 EAP 4 and still get the error. My understanding is that this has nothing to do with the iOS version. It's just that Rider is looking for the profiles in the wrong place.

I am currently using version 2024.2.6 productively

Kind regards
Marc

Hi Anna Morozyuk,

this is my version

JetBrains Rider 2024.2.7
Build #RD-242.23726.100, built on October 22, 2024
Licensed to Aton S.p.A. Società Benefit / Constantin Madalin Giuran
You have a perpetual fallback license for this version.
Subscription is active until October 1, 2025.
Runtime version: 21.0.4+13-b509.26 aarch64 (JCEF 122.1.9)
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Toolkit: sun.lwawt.macosx.LWCToolkit
macOS 15.0.1
.NET Core v8.0.4 ARM64 (Server GC)
GC: G1 Young Generation, G1 Concurrent GC, G1 Old Generation
Memory: 2048M
Cores: 12
Metal Rendering is ON
Registry:
 ide.experimental.ui=true
 i18n.locale=
Non-Bundled Plugins:
 com.jetbrains.rider.android (242.23726.100)
 com.intellij.ml.llm (242.23726.20)
 

i cant open the link you provided but from the title it look like something else ,not the problem we encounter ,basically look like Rider points to the old path of xcode (xcode 15.4) used for profiles (~/User/Library/MobileDevice/Provisioning Profiles.) ,but when you import new profiles( xcode 16) point to a whole different path (~/User/Library/Developer/Xcode/UserData/Provisioning Profiles).

isn't any way we set manually the source for the profiles? 

Could you please try installing .NET 9 RC2 and try reproducing the issue again? 

Looking forward to hearing from you soon. 

Hello Anna Morozyuk ,

Can you explain why you think that updating to .NET 9 RC2 will solve the problem?
I still think that Rider is looking in the wrong place for the files. Or does the location change again with .NET 9 RC?

I would be pleased if you could provide some more information here

Hi Anna Morozyuk,

The problem is on Xamarin.iOS projects, i think that it has nothing to do with .NET 8 / .NET 9.

Hi Anna Morozyuk, are there any news here? What is the current status of the ticket?

I have just spent hours trying to build a Xamarin.iOS app only to find there is a known issue that has not been addressed. 

What's the status? 

The workaround of copying files does not work for me. 

I agree with David. The workaround still doesn't work and we are all stuck. When will we get a response from support?

Hello everyone, 

Sorry for the delay in the reply. 

Let me please clear some points here: 

Can you explain why you think that updating to .NET 9 RC2 will solve the problem?

Because .NET 9 was changing the parameter in question in  the RC version. Hence, since .NET 9 RC2 it has been fixed. 

The problem is on Xamarin.iOS projects, i think that it has nothing to do with .NET 8 / .NET 9.

Xamarin has been affected as well. 

Also, please note that for this change a new Xamarin SDK is required and the last officially supported version is Xcode 15. 

As for the further troubleshooting, I would suggest the following: 

1. Update the .NET 9 to the current version.
2. Check if the issue is related to Rider by deploying the application from the command line: open Terminal and run dotnet build -t:Run -f net9.0-ios command. 
3. If the application runs from the command line just fine but is not running in Rider, please try re-running it in a new Rider version and/or EAP version. 
4. If it is still not working, please submit a bug report to our bugtracker.

Hope, my response was helpful. 

Hi Anna Morozyuk 

Based on your last response, is it the only way to resolve this issue is to upgrade the project to .NET 9?

Thanks,
Kenny.

Hello Kian, 

Let me summarize the issue and share possible options.

The issue occurred with the Xcode 16 release. The problematic change in Xcode 16 moved the location for provisioning profiles from ~/Library/MobileDevice/Provisioning\ Profiles to ~/Library/Developer/Xcode/UserData/Provisioning\ Profiles.

There is a corresponding issue on xamarin-macios repository: XCode 16 stores provisioning profiles in new location #20771
And there is a corresponding fix: Bump Xamarin.MacDev to get fix for xamarin/Xamarin.MacDev#20771.
This fix was delivered in this release: .NET 8.0.1xxx - Xcode 16.0 Support (8303)

It says you need at least 8.0.402 (or above) to be printed in the terminal checking dotnet --version, so that installing iOS workload would deliver a proper version. Unless you target .Net 9, you need .Net 8 SDK 8.402 or above. For .Net 9, you need an actual version of .Net 9 SDK. (see the instructions on the release page). 

Other possible options are: 

• to create a symbolic link as stated in the issue-related thread.
• to use an Xcode 15. 

Hope it helps. Have a nice day!

Hi Dmitry Kazantsev 

Thank you for the response & solution provided. Symbiotic link sounds good to us due to we are not planning to upgrade .NET version in short period of time.

Thanks,
Kenny.