Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
The following code works just fine when compiling for Windows. However, when I compile for an iOS device, GetMainifestResourceStream() always returns null. I have added the 4 files below to my project as 'Embedded Resource' and 'Do Not Copy'. GetManifestResourceStream returns null when running on my iPad device:
Assembly assembly = Assembly.GetExecutingAssembly();
List<Stream> streams = new List<Stream>
I tried to use the GetManifestResourceStreammethod on my iphone device to load an txt file as the 'Embedded Resource' and it works for me.
Could you please tried it on the latest build and if the issue is still there, could you provide a small test case.
Hello Bo, I am following up on this bug and attempting to reproduce the
issue with the latest stable build of our Xamarin Visual Studio product
(3.11.666) and so far I have been unable to reproduce the issue and can load an embedded resource on an iPhone successfully.
Please try to upgrade to the latest stable XVS build and if you are still
experiencing the same problem please reply and I'd be more than happy to setup
a screen sharing session to debug the issue.
Also, if possible can you please include your solution file / project file assets so I can more easily reproduce the issue in our environments.
Marking as resolved not_reproducible.
Please feel free to reopen the issue if you can still reproduce it with current bits.