Repository navigation
Android min sdk 24 part 1 - #170882
Android min sdk 24 part 1#170882
Conversation
…expand it to cover multiple min api level definitions
…hed on versions older than 24
|
This pull request has been changed to a draft. The currently pending flutter-gold status will not be able to resolve until a new commit is pushed or the change is marked ready for review again. For more guidance, visit Writing a golden file test for Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. |
Also migrate FlutterViewTest to use API_LEVELS for roboletric config
…g line about deprecrated mocked calls
|
Desugar is the last test that is still failing. I tweaked the error version in the extension so I could pick lower min apk versions and the test passes on when the min sdk is 21, 22 or 23 and fails at 24. Additionally I ruled out that this might be a change from the google maps side by running the test locally and checking the lock file. Which are recet published versions. Additionally this test is passing on master on the dashboard without flakes. #72185 is the original bug this test was meant to protect against regression. This makes me think the way we validate is at issue but we have not regressed. |
|
GoogleMapController API 24 methods Api 23 methods |
|
The only difference in the above are the following lines are missing from min api 24. |
|
Current theory is that onFlutterViewAttached and onFlutterViewDetached are not actually used in the google maps plugin code (or any plugins that we currently have) and what I am seeing is some form of code stripping change. If that is the case than any method that is used from the framework in the plugin can verify the change in behavior without necessarily relating to desugaring (aka using higher java apis than what they are compiled with). Further evidence in support i that this test ran successfully as we bumped java from 8 to 11 then 17 and now 21 without issue. |
- **bump template version, update migration code to handle api 21-23 and expand it to cover multiple min api level definitions** - **bump add to app project to minimum api level 24** - **PathUtilsTest converted to using config, removed test code that branched on versions older than 24** - **Update additional build.gradle files to have minsdk 24 and documenation** Related to flutter#170807 G3 cls - espresso https://critique.corp.google.com/cl/776592881 - integration tests cl/778034198 - removal of pre api 23 samples tests cl/777652802 ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [x] I listed at least one issue that this PR fixes in the description above. - [x] I updated/added relevant documentation (doc comments with `///`). - [x] I added new tests to check the change I am making, or this PR is [test-exempt]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing. --------- Co-authored-by: Gray Mackall <[email protected]>
- **bump template version, update migration code to handle api 21-23 and expand it to cover multiple min api level definitions** - **bump add to app project to minimum api level 24** - **PathUtilsTest converted to using config, removed test code that branched on versions older than 24** - **Update additional build.gradle files to have minsdk 24 and documenation** Related to flutter#170807 G3 cls - espresso https://critique.corp.google.com/cl/776592881 - integration tests cl/778034198 - removal of pre api 23 samples tests cl/777652802 ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [x] I listed at least one issue that this PR fixes in the description above. - [x] I updated/added relevant documentation (doc comments with `///`). - [x] I added new tests to check the change I am making, or this PR is [test-exempt]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing. --------- Co-authored-by: Gray Mackall <[email protected]>
Related to #170807
G3 cls
Pre-launch Checklist
///).