Bug 49068 - Manual rotation in xamarin.forms.maps for UWP raises a "Value out of range" exception.
Summary: Manual rotation in xamarin.forms.maps for UWP raises a "Value out of range" e...
Status: RESOLVED DUPLICATE of bug 41900
Alias: None
Product: Forms
Classification: Xamarin
Component: Windows ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2016-12-06 09:59 UTC by Swati Das
Modified: 2017-02-01 01:02 UTC (History)
3 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
RESOLVED DUPLICATE of bug 41900

Description Swati Das 2016-12-06 09:59:25 UTC
We are using Xamarin.forms.maps for UWP platform. However, on rotating the map through gestures, the app crashes. We also deployed the sample code provided by Xamarin "WorkingWithMaps" on a Windows mobile. Even that app crashes. The exception stack trace pointed to some geolocation binding and Visible region population in the native code. So I guess that is a bug with Xamarin.forms.maps for UWP. Could you please look into this ?
Comment 1 Samantha Houts [MSFT] 2017-02-01 01:02:20 UTC

*** This bug has been marked as a duplicate of bug 41900 ***