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 or GitHub 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.
Created attachment 13758 [details]
Xamarin.Forms project created with Xamarin Studio to demonstrate the crash
*** Overview ***
When loading an URL using a Xamarin.Forms.WebView on iOS,
the application will crash it the URL contains special characters such as the Swedish "Å" even when escaped with Uri.EscapeDataString
Error message is:
Unhandled managed exception:
Could not initialize an instance of the type 'Foundation.NSUrl': the native 'initWithString:' method returned nil.
It is possible to ignore this condition by setting MonoTouch.ObjCRuntime.Class.ThrowOnInitFailure to false. (System.Exception)
*** Steps to Reproduce ***
Run the sample project and click on the button that creates the crash.
*** Environment Info ***
Mac OS 10.11.1
Xamarin Studio Version 5.9.8 (build 0)
Xcode 7.1 (9079) Build 7B91b
Version: 126.96.36.199 (Business Edition)
Note that this issue is similar to #29274 https://bugzilla.xamarin.com/show_bug.cgi?id=29247
In #29274 the issue was with Device.OpenUri
There is no problem opening the URL with Device.OpenUri.
The problem only occurs when loading it in a WebView.
Should be fixed in 1.5.2-pre3
I have tried with 188.8.131.5278-pre3 and still get the crash.
Sorry this didn't get into 2.0, will be in the next release 2.0.1-pre1
I don't see this bug mentioned in 2.0.1-pre1 release notes, was it indeed included in 2.0.1-pre1 or pushed back to another version?
Yes is fixed on pre1 , but missed from the release notes.
I've just tested and can confirm that the crash is fixed on 184.108.40.20692-pre1
Crash still occurs with german umlauts in the URI on 220.127.116.1129