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.
The Xamarin.Forms.Platform.UWP.WindowsDeviceInfo class ScalingFactor property implementation is missing several ResolutionScale enums, which results in Xamarin.Forms.Device.Info.ScalingFactor incorrectly returning the default value of '1' for several ResolutionScales.
For our scenario, we are specifically missing Scale125Percent.
**Steps to reproduce:
1. In a Xamarin.Forms app, add an implementation to the portable project to display the value of Xamarin.Forms.Device.Info.ScalingFactor on the app main page
2. Add a UWP-specific implementation to print the value of the DisplayInformation.ResolutionScale to the app main page
3. Deploy the UWP implementation of the app to a Win10 system with a resolution that results in Scale125Percent (in our case Dell Latitude 5175, resolution of 1920 x 1080)
4. Start the app
5. Observe that the displayed ResolutionScale is Scale125Percent, however the ScalingFactor is 1 (expected 1.25)
Would it be possible to just return Windows.Graphics.Display.DisplayInformation.RawPixelsPerViewPixel property instead of relying on the switch statement?
**Switch statement code from Xamarin.Forms.Platform.UWP.WindowsDeviceInfo
Windows.Graphics.Display.DisplayInformation.RawPixelsPerViewPixel is only available on UWP so we would have to check for that as WinRT is not fully removed yet.
Should be fixed on 2.6.0-pre1