Xamarin app unable to access Apple On-Demand Resources

Hi all,

We have a Xamarin app that makes use of Apple On-Demand Resources that doesn’t seem to be able to access these resources when built through Rider to iOS simulator. This currently works for us with Visual Studio for Mac, though in the past it has been finicky. 

Our app code that calls the function


throws the following exception (with redacted bundle name for sharing purposes): 

Error Domain=NSCocoaErrorDomain Code=4994 "The requested application data doesn’t exist." UserInfo={NSUnderlyingError=0x6000028f3450 {Error Domain=_NSBundleResourceRequestErrorDomain Code=100 "No manifest found for bundle ID [redacted bundle name]" UserInfo={NSLocalizedFailureReason=No manifest found for bundle ID [redacted bundle name]}}}

We haven't made any code or config changes related to these files that would effect anything since switching from Visual Studio to Rider. I am using Visual Studios' Xamarin iOS SDK version and .NET SDK version 5.0.402.

Looking for any possible resolution here or is this a known limitation of Rider? Help much appreciated, thanks

Comment actions Permalink

I have also noticed there seems to be a mismatch between the simulator Rider says is the launch target vs the one actually being launched to. I For example, if I select in iOS simulator drop-down an iPhone 12 running iOS 15.2, I see in the Rider application output the following:

/Library/Frameworks/Xamarin.iOS.framework/Versions/Current/bin/mlaunch --launchsim /Users/mbecker/repos/my-app-repo/My.App/My.App.iOS/bin/MyApp/Debug/iPhoneSimulator/device-builds/iphone13.2-15.2/My.App.iOS.app --device=:v2:udid=899A5F9F-A8FB-482B-89A6-4E4BE577B528 -sdk 15.2 --argument=-monodevelop-port --argument=10002 --setenv=__XAMARIN_DEBUG_PORT__=10002 --sdkroot /Applications/Xcode.app/Contents/Developer

The app installs and is debuggable on what I actually selected (iPhone 12), but why is there a mismatch in the mlaunch command with 'iphone13.2-15.2' and what it actually installs on? 

I suspect this is related to the issue of On-Demand Resources assets not being accessible. 

Comment actions Permalink

Hi Mbecker

As we can see, you've also posted the RIDER-75904 issue and we already processed it. Please let us know if you have any other questions. 


Please sign in to leave a comment.