jesswrd
jesswrd
Removed `platform/example/android` and `dynamic_layouts/example/android` as they have been moved to a new location or deleted. Added a few outstanding example plugin apps to migration checklist, including `rfw` and `third_party` .
It looks like a `camera` integration test is also failing on image resolution: https://ci.chromium.org/ui/p/flutter/builders/try/Linux_android%20android_device_tests_shard_1%20master/12254/overview
Evaluating some cases such as a Cupertino app on Android and Material on iOS to see if the bug shows up by default. And if not, why?
The bug appears in the Cupertino app on Android when there is no CupertinoNavigationBar. @LouiseHsu confirmed the bug does not show up by default in Material and Cupertino on iOS.
Made a doc investigating existing behavior of adopting/using a dark theme on Material [here](https://docs.google.com/document/d/17x8ClG6BcdsXypbJQBVLjTn_vswh4qPxJmLxhhSF_-M/edit?usp=sharing). It explains how Material currently handles using a dark theme. It also outlines the differences in...
from android triage: @zilvis97 What version of google_maps_flutter_android are you using and if this is a regression, what was the last known good version?
From Android Triage: It looks like there are still instances of `onSurfaceDestroyed`. It looks like the issue @matanlurey linked has replaced all instances of `onSurfaceCreated`. https://github.com/search?q=repo%3Aflutter%2Fpackages+onsurfacedestroyed&type=code
> Looks like this change triggers a new check on the existing `targetSdkVersion` value? Yeah, I think the current `targetSdkVersion` is outdated. I'm just going to update it to 35...
We don't plan on supporting CameraAndroid plugin in the long-term. If we choose to continue supporting it, then we can revisit the priority.