xamarin/Xamarin.Forms

Gradient view issue on Mac OS Android emulator API level 28 (Pie)

Open

#3,912 opened on Sep 27, 2018

View on GitHubContributor guide
 (6 comments) (1 reaction) (0 assignees)C# (1,926 forks)batch import
a/layoute/7 :clock7:excellent-reporthelp wantedinactivep/iOS 🍎t/bug :bug:up-for-grabs

Repository metrics

Stars
 (5,644 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Description

Gradient view doesn't rendered properly on Mac OS Android 9 emulator (Older version of emulators work fine). But same project works as expected on Android 9 emulator on Windows.

Steps to Reproduce

I have attached a demo project.

Expected Behavior

Gradient view should be rendered only within the specified area of the view.

Actual Behavior

Gradient view rendered in entire screen as an input transparent view. User can interact with elements out side the Gradient view which are invisible. Only elements inside Gradient view are visible.

Basic Information

  • Version with issue: 3.1.0.697729 / 2.5.0.91635
  • Last known good version: Didn't try with working older versions
  • IDE: VS Community 2017 for Mac
  • Platform Target Frameworks:
    • iOS: N/A
    • Android: 9.0 Pie
    • UWP: N/A
  • Android Support Library Version: API 28
  • Nuget Packages:
  • Affected Devices: Mac OS Android 9 (Pie) emulator

Screenshots

image Expected output (Windows emulator)

image Unexpected output (Mac OS emulator)

Reproduction Link

GradientViewDemo.zip

Contributor guide

Research direction
Investigate the rendering differences between Mac and Windows Android emulators for API level 28, focusing on the gradient view implementation and identifying why it renders full screen on Mac.
Tech stack
csharp
Domain
mobile
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitXamarin.FormsAndroid emulator
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60