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.
My Shared project Forms application uses the proximity setting in the AppDelegate.cs file of the iOS project:
UIDevice.CurrentDevice.ProximityMonitoringEnabled = true;
The Shared project has multiple pages, one with a Picker control on it. The proximity sensor works perfectly on all the pages until a selection is made with the Picker. Once an item is selected in the Picker control, the proximity sensor is disabled. As a work around, I've hooked up an event handler to reset the proximity setting:
protected void OnPickerControlSelectedIndexChanged(object sender, EventArgs args)
MonoTouch.UIKit.UIDevice.CurrentDevice.ProximityMonitoringEnabled = true;
I have checked this issue but I am not able to reproduce this. Could you please provide us sample project/steps and environment info so that I can reproduce this issue at my end.
You can get environment info via (Xamarin Studio->About Xamarin Studio->Show details->Copy information and paste)
Sorry for the delayed response - I was away on vacation.
I am using Visual Studio (2013 Update 4) with Forms 220.127.116.11. I ran the application through the VS debugger on my iPhone 6.
Please let me know if you need any additional information.
Thank you for taking the time to submit the bug. Going forward, we're asking customers to attach reduced reproductions to the bugs. Ideally, the reproduction would be created by starting with a clean Xamarin.Forms project and adding just the code necessary to demonstrate the issue. We know not everyone has time to do this and it's not a requirement to submit a bug, but it does help us resolve issues faster as well as ensuring we're solving the same issue you're seeing, so we very much appreciate it.
Xamarin Forms Team
Because we have not received a reply to our request for more information we are closing this issue. If you are still encountering this issue, please reopen the ticket with the requested information. Thanks!