-
Notifications
You must be signed in to change notification settings - Fork 1.9k
[Android] Changes in the logic to detect Device.Idiom #11206
Conversation
Retarget to 4.5.0. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Both API 19 tests have the same failures
@PureWeen Yes, are failing the tests Issue2948 and Issue2951 although Device.Idiom is not used in these cases. Will take a look. |
Maybe test didn't succeed, because of you need to accept some new agreements?
|
Going to rebase and run tests again . Tests that were failoing were 2951 and 2948 |
Same tests are failing. @jsuarezruiz Can you investigate, please? Thanks! |
Maybe i could potentially help with fix, but i have problems with identifying failing test, as im not familiar with azure pipeline...
|
a414f31
to
005dd9f
Compare
005dd9f
to
65e2eff
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm testing with the following code
SetMainPage(new ContentPage()
{
Content = new StackLayout()
{
Children =
{
new Label()
{
Text = Device.Idiom.ToString()
}
}
}
});
And it's giving me back Unsupported. I'm testing on an API 23 emulator
if I roll back the changes here for Forms.cs then it gives me "Phone"
@PureWeen Updated fixing that issue. Could you try/review it again please? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok tested with @PureWeen example, can get Phone and Tablet ok , in api 23/ api 29 , api 30
Description of Change
Changed checking the
UiMode
enum using HasFlag to use ==. Based on this changes xamarin/Essentials@b937b12 from Xamarin Essentials.Issues Resolved
API Changes
None
Platforms Affected
Behavioral/Visual Changes
None
Before/After Screenshots
Not applicable
PR Checklist