Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Device using Qualcomm Adreno 308 (supports OpenGL ES 3.0) crashes with current OpenGL ES 3.1 #36130

Closed
vortal opened this issue Jul 13, 2019 · 72 comments
Assignees
Labels
c: crash Stack traces logged to the console c: regression It was better in the past than it is now customer: crowd Affects or could affect many people, though not necessarily a specific customer. customer: google Various Google teams dependency: skia Skia team may need to help us platform-android Android applications specifically waiting for PR to land (fixed) A fix is in flight

Comments

@vortal
Copy link

vortal commented Jul 13, 2019

I have my app running on Android 7 to 9, except on a Samsung J6+ which has a Qualcomm Adreno 308, supporting OpenGL 3.0.

AndroidManifest.xml already contains:

<uses-feature android:glEsVersion="0x00030000" android:required="true" />

Gradle:

    dependencies {
        classpath 'com.android.tools.build:gradle:3.4.1'
        classpath 'com.google.gms:google-services:4.2.0'
        classpath 'io.fabric.tools:gradle:1.29.0'
    }

App Gradle:

    defaultConfig {
        applicationId "br.com.xx.xx.xx"
        minSdkVersion 22
        targetSdkVersion 29
        versionCode flutterVersionCode.toInteger()
        versionName flutterVersionName
        testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
        multiDexEnabled true
    }
    . . .

    implementation 'androidx.core:core:1.0.2'
    implementation 'androidx.appcompat:appcompat:1.0.2'
    implementation 'androidx.preference:preference:1.0.0'
    implementation 'androidx.legacy:legacy-support-core-utils:1.0.0'
    implementation 'com.google.android.material:material:1.1.0-alpha07'
    implementation 'androidx.multidex:multidex:2.0.0'

    implementation 'com.google.firebase:firebase-database:17.0.0'
    implementation 'com.google.firebase:firebase-auth:17.0.0'
    implementation 'com.google.firebase:firebase-crash:16.2.1'
    implementation 'com.google.android.gms:play-services-base:17.0.0'
    implementation 'com.google.android.gms:play-services-auth:17.0.0'
    implementation 'com.google.android.gms:play-services-location:17.0.0'
    implementation 'com.crashlytics.sdk.android:crashlytics:2.10.1'

    androidTestImplementation 'androidx.test:runner:1.2.0'
    androidTestImplementation 'androidx.test.espresso:espresso-core:3.2.0'

What am I getting wrong? Is there any way to have the app forcibly compiled with OpenGL ES 3.0 ?

Steps to Reproduce

Run on a real J6+ device.

Logs

Syncing files to device SM J610G...
D/ViewRootImpl@adfe2db[MainActivity](28843): MSG_WINDOW_FOCUS_CHANGED 1 1
D/InputMethodManager(28843): prepareNavigationBarInfo() DecorView@6cbb45d[MainActivity]
D/InputMethodManager(28843): getNavigationBarColor() -855310
D/InputMethodManager(28843): prepareNavigationBarInfo() DecorView@6cbb45d[MainActivity]
D/InputMethodManager(28843): getNavigationBarColor() -855310
V/InputMethodManager(28843): Starting input: tba=br.com.xx.xx.xx ic=null mNaviBarColor -855310 mIsGetNaviBarColorSuccess true , NavVisible : true , NavTrans : false
D/InputMethodManager(28843): startInputInner - Id : 0
I/InputMethodManager(28843): startInputInner - mService.startInputOrWindowGainedFocus
D/ViewRootImpl@adfe2db[MainActivity](28843): MSG_RESIZED_REPORT: frame=[0,0][720,1480] ci=[0,42][0,84] vi=[0,42][0,84] or=1
D/InputTransport(28843): Input channel constructed: fd=101
D/InputMethodManager(28843): prepareNavigationBarInfo() DecorView@6cbb45d[MainActivity]
D/InputMethodManager(28843): getNavigationBarColor() -855310
V/InputMethodManager(28843): Starting input: tba=br.com.xx.xx.xx ic=null mNaviBarColor -855310 mIsGetNaviBarColorSuccess true , NavVisible : true , NavTrans : false
D/InputMethodManager(28843): startInputInner - Id : 0
I/flutter (28843): AppScoped.setupModels()
I/flutter (28843): MainApp.build() -> user not authenticated
**I/Adreno  (28843): ERROR: The GPU does not support this version of OpenGL ES, try an older version**
D/skia    (28843): Shader compilation error
D/skia    (28843): ------------------------
D/skia    (28843):    1	#version 310 es
D/skia    (28843):    2	
D/skia    (28843):    3	in highp vec4 sk_FragCoord_Workaround;
D/skia    (28843):    4	precision mediump float;
D/skia    (28843):    5	out mediump vec4 sk_FragColor;
D/skia    (28843):    6	in mediump vec4 vcolor_Stage0;
D/skia    (28843):    7	void main() {
D/skia    (28843):    8	    mediump vec4 outputColor_Stage0;
D/skia    (28843):    9	    {
D/skia    (28843):   10	        outputColor_Stage0 = vcolor_Stage0;
D/skia    (28843):   11	    }
D/skia    (28843):   12	    {
D/skia    (28843):   13	        sk_FragColor = outputColor_Stage0;
D/skia    (28843):   14	    }
D/skia    (28843):   15	}
D/skia    (28843):   16	
D/skia    (28843): Errors:
D/skia    (28843): ERROR: The GPU does not support this version of OpenGL ES, try an older version
D/skia    (28843): 
I/Adreno  (28843): ERROR: The GPU does not support this version of OpenGL ES, try an older version
D/skia    (28843): Shader compilation error
D/skia    (28843): ------------------------
D/skia    (28843):    1	#version 310 es
D/skia    (28843):    2	
D/skia    (28843):    3	in highp vec4 sk_FragCoord_Workaround;
D/skia    (28843):    4	precision mediump float;
D/skia    (28843):    5	out mediump vec4 sk_FragColor;
D/skia    (28843):    6	in highp vec4 vinCircleEdge_Stage0;
D/skia    (28843):    7	in mediump vec4 vinColor_Stage0;
D/skia    (28843):    8	void main() {
D/skia    (28843):    9	    mediump vec4 outputColor_Stage0;
D/skia    (28843):   10	    mediump vec4 outputCoverage_Stage0;
D/skia    (28843):   11	    {
D/skia    (28843):   12	        highp vec4 circleEdge;
D/skia    (28843):   13	        circleEdge = vinCircleEdge_Stage0;
D/skia    (28843):   14	        outputColor_Stage0 = vinColor_Stage0;
D/skia    (28843):   15	        highp float d = length(circleEdge.xy);
D/skia    (28843):   16	        mediump float distanceToOuterEdge = circleEdge.z * (1.0 - d);
D/skia    (28843):   17	        mediump float edgeAlpha = clamp(distanceToOuterEdge, 0.0, 1.0);
D/skia    (28843):   18	        mediump float distanceToInnerEdge = circleEdge.z * (d - circleEdge.w);
D/skia    (28843):   19	        mediump float innerAlpha = clamp(distanceToInnerEdge, 0.0, 1.0);
D/skia    (28843):   20	        edgeAlpha *= innerAlpha;
D/skia    (28843):   21	        outputCoverage_Stage0 = vec4(edgeAlpha);
D/skia    (28843):   22	    }
D/skia    (28843):   23	    {
D/skia    (28843):   24	        sk_FragColor = outputColor_Stage0 * outputCoverage_Stage0;
D/skia    (28843):   25	    }
D/skia    (28843):   26	}
D/skia    (28843):   27	
D/skia    (28843): Errors:
D/skia    (28843): ERROR: The GPU does not support this version of OpenGL ES, try an older version


flutter doctor -v results:

[√] Flutter (Channel dev, v1.8.0, on Microsoft Windows [Version 10.0.15063], locale pt-BR)
    • Flutter version 1.8.0 at C:\Users\fernando\AppData\Local\Flutter
    • Framework revision 2fefa8c731 (12 days ago), 2019-07-01 11:33:22 -0700
    • Engine revision 45b66b722e
    • Dart version 2.4.0

[!] Android toolchain - develop for Android devices (Android SDK version 29.0.0)
    • Android SDK at C:\Users\fernando\AppData\Local\Android\sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.0
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)
    ! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses

[√] Android Studio (version 3.4)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 36.1.1
    • Dart plugin version 183.6270
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)

[√] VS Code (version 1.36.1)
    • VS Code at C:\Users\fernando\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.2.0

[√] Connected device (1 available)
    • SM J610G • 715690a3 • android-arm • Android 9 (API 28)

! Doctor found issues in 1 category.


@vortal
Copy link
Author

vortal commented Jul 14, 2019

Update: rolling back to Flutter stable channel solved the issue, app runs with no issues:

[√] Flutter (Channel stable, v1.7.8+hotfix.3, on Microsoft Windows [Version 10.0.15063], locale pt-BR)
    • Flutter version 1.7.8+hotfix.3 at C:\Users\fernando\AppData\Local\Flutter
    • Framework revision b712a172f9 (5 days ago), 2019-07-09 13:14:38 -0700
    • Engine revision 54ad777fd2
    • Dart version 2.4.0

[!] Android toolchain - develop for Android devices (Android SDK version 29.0.0)
    • Android SDK at C:\Users\fernando\AppData\Local\Android\sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.0
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)
    ! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses

[√] Android Studio (version 3.4)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 36.1.1
    • Dart plugin version 183.6270
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)

[√] VS Code (version 1.36.1)
    • VS Code at C:\Users\fernando\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.2.0

[√] Connected device (1 available)
    • SM J610G • 715690a3 • android-arm • Android 9 (API 28)

@tvolkert tvolkert added c: crash Stack traces logged to the console c: regression It was better in the past than it is now platform-android Android applications specifically labels Jul 18, 2019
@tvolkert
Copy link
Contributor

@liyuqian

@liyuqian
Copy link
Contributor

My understanding is that you can't force OpenGL ES 3.0 from the gradle file (or any file under your control). Skia should be checking your supported OpenGL ES level by communicating with the GPU driver and generate the shader for that version dynamically at runtime.

The crash here could either be a GPU driver bug, or a Skia bug. CC @bsalomon from Skia. Maybe Skia team need a Samsung J6+ and your app to reproduce the issue. Hence for @vortal: can you please attach a minimal Flutter app that reproduces this crash? Alternatively, can you check if flutter_gallery app crashes on J6+?

@liyuqian liyuqian added the dependency: skia Skia team may need to help us label Jul 22, 2019
@vortal
Copy link
Author

vortal commented Jul 25, 2019

My apologies but I have already returned the device to the client, who I borrowed from, hence I won't be able to supply a "crashable" version again nor verify flutter_gallery. Sorry. But the setup at the time was Flutter dev channel v1.8.0 + Gradle 5.1.1/3.4.1 + Dart 2.4.0 with Android Studio 3.4.1 on an i7 Windows box.

Either through debug mode with device attached, or running a release version, the crash has been verified at that very point above.

@markmclaren2
Copy link

markmclaren2 commented Aug 8, 2019

I'm getting the same kind of error when running a Flutter app on my Summit 2 smartwatch. Funny thing is this app was running fine until the underlying Android operating system was updated - now it's giving me a black screen, and the following output:

I/Adreno  ( 2976): ERROR: The GPU does not support this version of OpenGL ES, try an older version
D/skia    ( 2976): Shader compilation error
D/skia    ( 2976): ------------------------
D/skia    ( 2976):    1	#version 310 es
D/skia    ( 2976):    2	
D/skia    ( 2976):    3	in highp vec4 sk_FragCoord_Workaround;
D/skia    ( 2976):    4	precision mediump float;
D/skia    ( 2976):    5	out mediump vec4 sk_FragColor;
D/skia    ( 2976):    6	in mediump vec4 vcolor_Stage0;
D/skia    ( 2976):    7	void main() {
D/skia    ( 2976):    8	    mediump vec4 outputColor_Stage0;
D/skia    ( 2976):    9	    {
D/skia    ( 2976):   10	        outputColor_Stage0 = vcolor_Stage0;
D/skia    ( 2976):   11	    }
D/skia    ( 2976):   12	    {
D/skia    ( 2976):   13	        sk_FragColor = outputColor_Stage0;
D/skia    ( 2976):   14	    }
D/skia    ( 2976):   15	}
D/skia    ( 2976):   16	
D/skia    ( 2976): Errors:
D/skia    ( 2976): ERROR: The GPU does not support this version of OpenGL ES, try an older version
D/skia    ( 2976): 

Here's my flutter doctor output:

[✓] Flutter (Channel dev, v1.8.4, on Mac OS X 10.14.5 18F132, locale en-AU)
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[!] Xcode - develop for iOS and macOS (Xcode 10.2.1)
    ✗ CocoaPods not installed.
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin code that
        responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To install:
        sudo gem install cocoapods
        pod setup
[!] Android Studio (version 3.4)
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
[✓] IntelliJ IDEA Community Edition (version 2019.1.1)
[✓] Connected device (2 available)

! Doctor found issues in 2 categories.

@liyuqian
Copy link
Contributor

liyuqian commented Aug 8, 2019

@vortal @markmclaren2 : can you please try uninstall and reinstall the app to see if the crash goes away? We suspect that the OS upgrade may have downgraded the OpenGL version which causes some trouble in our cache. Deleting the app will evict the cache and fix the problem if that's the case.

@markmclaren2
Copy link

Same problem I'm afraid, even after I removed the app from the device, and performed a flutter clean then flutter run --release

@liyuqian
Copy link
Contributor

liyuqian commented Aug 9, 2019

Ok, I'm going to get a Samsung J6+ to do some local testing (hopefully it suffices without needing a much more expensive Summit 2).

@markmclaren2 : can you please provide a minimal Flutter app (hopefully just one main.dart with fewer than 200 lines of code) that reproduces that crash?

@Jongui
Copy link

Jongui commented Aug 11, 2019

I am facing the same problem. Downgrading to the last stable release solved the problem.

@markmclaren2
Copy link

@liyuqian just the standard app produced by flutter create produces the problem on my device. I have performed a factory reset (from Wear OS 2.8 to Wear OS 2.6) but it still has the problem

@vlkigdm
Copy link

vlkigdm commented Aug 13, 2019

Same problem on J4+

@liyuqian liyuqian added the customer: google Various Google teams label Aug 19, 2019
@ened
Copy link
Contributor

ened commented Aug 21, 2019

@liyuqian Do you have any update? We have multiple customers calling in regarding their unsupported phone.

We also can not downgrade to stable currently due to other important bug fixes in dev. :-(

Anything you need from the community to get it one?
A sample project is here: https://github.com/ened/flt_perf_04_samsung_j6_plus - it's just the basic flutter app template. You can run it with flutter run --release lib/main.dart, or flutter run --debug lib/main.dart.

@liyuqian
Copy link
Contributor

I can reproduce the issue. But I haven't figured out why the issue happened. Will keep debugging further tomorrow.

@liyuqian
Copy link
Contributor

On Samsung J6+, I've identified that

  • GR_GL_CALL_RET(gl, v, GetString(GR_GL_SHADING_LANGUAGE_VERSION)) returns OpenGL ES GLSL ES 3.10
  • GR_GL_CALL_RET(interface.get(), verUByte, GetString(GR_GL_VERSION)) returns OpenGL ES 3.0 V@331.0 (GIT@077c1bb, I67e1628f4e) (Date:04/09/19)

Hence this seems to be a driver bug that claims that it supports GLSL ES 3.10 but actually it doesn't. Will discuss with Skia team to see how to work around this bug.

CC @egdaniel

@CPDdev
Copy link

CPDdev commented Aug 28, 2019

@liyuqian Did you get any response from the Skia team? We are daily receiving calls regarding this issue.

@liyuqian
Copy link
Contributor

The fix is coming: https://skia-review.googlesource.com/c/skia/+/237898

@liyuqian
Copy link
Contributor

The fix relanded in https://skia-review.googlesource.com/c/skia/+/238057

luigi-rosso pushed a commit to luigi-rosso/skia that referenced this issue Aug 29, 2019
Some Adreno 308 devices have a driver bug where the GLSL version is
higher than the GL version, and attempting to use shaders with that
version triggers an error.

Change-Id: I5c8996e9771983e547ec75e57b04e2584507727f
Bug: flutter/flutter#36130
Reviewed-on: https://skia-review.googlesource.com/c/skia/+/237898
Reviewed-by: Brian Salomon <bsalomon@google.com>
Commit-Queue: Brian Osman <brianosman@google.com>
luigi-rosso pushed a commit to luigi-rosso/skia that referenced this issue Aug 29, 2019
This reverts commit 63655b5.

Reason for revert: Seems to be happening on more devices than is expected.

Original change's description:
> Pin the GLSL version to be no larger than the GL version
> 
> Some Adreno 308 devices have a driver bug where the GLSL version is
> higher than the GL version, and attempting to use shaders with that
> version triggers an error.
> 
> Change-Id: I5c8996e9771983e547ec75e57b04e2584507727f
> Bug: flutter/flutter#36130
> Reviewed-on: https://skia-review.googlesource.com/c/skia/+/237898
> Reviewed-by: Brian Salomon <bsalomon@google.com>
> Commit-Queue: Brian Osman <brianosman@google.com>

TBR=bsalomon@google.com,brianosman@google.com

Change-Id: I4df2a01ae5228aa4edb56b35aa7f28807886282a
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: flutter/flutter#36130
Reviewed-on: https://skia-review.googlesource.com/c/skia/+/237903
Reviewed-by: Brian Osman <brianosman@google.com>
Commit-Queue: Brian Osman <brianosman@google.com>
@CPDdev
Copy link

CPDdev commented Sep 4, 2019

Hi when will this be available in the dev channel please? This issue is impacting ~2% of our android users so including ASAP would be much appreciated.

@liyuqian
Copy link
Contributor

liyuqian commented Sep 4, 2019

This fix will be included in the dev channel as soon as 471c805 is included in the dev channel. Our current dev channel v1.9.7 includes commits up to 08/28 while that commit is on 08/30.

We're rolling commits into dev channel as fast as we can. Usually a commit will be in the dev channel within a week or so. Hence I'd expect that fix to be in the dev channel either this week or the next week.

@liyuqian liyuqian self-assigned this Sep 4, 2019
@liyuqian liyuqian added the waiting for PR to land (fixed) A fix is in flight label Sep 4, 2019
@huergomartin
Copy link

This fix should be in beta now (v1.10.7).

Hi, yesterday I added internal testers with J6+ and J4+ in beta channel 1.10.7 and the black screen still appears. The bad comments on the store keep growing.

@liyuqian
Copy link
Contributor

@huergomartin : #37155 seems to be a different issue. let's try to move the discussion there and find a solution.

@MuhammamdArslanKhan
Copy link

I have samsung J6+ still having black screen . flutter 1.9.1+hotfix4

@campioncino
Copy link

I have the same problem with Samsung J6+ and flutter 1.9.1+hotfix6

@andersonmendesdev
Copy link

Hello same problem with j6 and j4, Channel stable, v1.9.1 + hotfix.6.
We're getting negative comments in store, we need a solution.

@campioncino
Copy link

Hello same problem with j6 and j4, Channel stable, v1.9.1 + hotfix.6.
We're getting negative comments in store, we need a solution.

Maybe is not the best solution, but you can solve temporarily switching to 1.7.8 hotfix 4

@MuhammamdArslanKhan
Copy link

If the Flutter team still didn't solve this issue then It seems they are working on react native rather than flutter, It is really disappointing waiting since 9/10/2019.

@MuhammamdArslanKhan
Copy link

Hello same problem with j6 and j4, Channel stable, v1.9.1 + hotfix.6.
We're getting negative comments in store, we need a solution.

Bro come on 1.7.8+hotfix.4

@sergicastellsague
Copy link

@andersonmendesdev I'm using the latest in Beta branch and this issue is not happening anymore.

@andersonmendesdev
Copy link

So unfortunately I can not downgrade there are several corrections that in this version do not exist, such as overflow in dropdownbutton with large text and overflow in row text and among other various corrections. I believe it is best to go to the beta channel less risk I believe.

@sergicastellsague
Copy link

@andersonmendesdev we're currently using Channel beta, v1.10.7 and we did not experience more issues than with previous versions on the stable channel. I would really give it a try.

@andersonmendesdev
Copy link

@sergicastellsague Great we are already preparing a test version using the beta channel.

@guitcastro
Copy link

@andersonmendesdev @sergicastellsague We had some issues with iOS using v1.10.7, v 1.10.15 seems ok for both iOS and Android.

@edinaldofox
Copy link

edinaldofox commented Nov 26, 2019

Topic in stackoverflow
"To switch version you can do flutter version 1.7.8+hotfix.4 and then flutter run"

Success on my J4+ device!

@ryannh
Copy link

ryannh commented Dec 5, 2019

Topic in stackoverflow
"To switch version you can do flutter version 1.7.8+hotfix.4 and then flutter run"

Success on my J4+ device!

There is still an error if your application uses the firebase_messaging library

@santiagorr207
Copy link

Buenos Días, tengo el mismo problema con mi dispositivo j4+ ¿ya encontraron una solución?

@edinaldofox
Copy link

edinaldofox commented Dec 5, 2019

@santiagorr207 no seu projeto execute "flutter version 1.7.8+hotfix.4" com essa verção do flutter vai funcionar, deu certo no meu J4+

@santiagorr207
Copy link

saben si en la versión 1.12.13+hotfix.2, este error esta solucionado ?

@edinaldofox
Copy link

não sei qual outro hotfix esta funcionando, a cima do 1.7.8+hotfix.4

@sergicastellsague
Copy link

@santiagorr207 It was fixed quite a while ago, indeed 1.12 also has the fix.

@santiagorr207
Copy link

@ santiagorr207 Se solucionó hace bastante tiempo, de hecho 1.12 también tiene la solución.

Muchas gracias ¿me puedes pasar el codigo para actualizar?

@sergicastellsague
Copy link

To update @santiagorr207 it's quite simple. First of all you've to switch flutter to use the beta instead of stable:
flutter channel beta
and then:
flutter upgrade
That should be enough. Confirm with:
flutter --version

@santiagorr207
Copy link

me sale lo siguiente "bash: /d/Programas/src/flutter/bin/flutter: No such file or directory
"

@sergicastellsague
Copy link

@santiagorr207 this is because you did not set up the environment variables properly. You either do it now:
https://flutter.dev/docs/get-started/install/macos#update-your-path

Or just replace "flutter" by the absolute path of the flutter binary file.

@github-actions
Copy link

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 25, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
c: crash Stack traces logged to the console c: regression It was better in the past than it is now customer: crowd Affects or could affect many people, though not necessarily a specific customer. customer: google Various Google teams dependency: skia Skia team may need to help us platform-android Android applications specifically waiting for PR to land (fixed) A fix is in flight
Projects
None yet
Development

No branches or pull requests