-
Notifications
You must be signed in to change notification settings - Fork 29k
Update number of IPHONEOS_DEPLOYMENT_TARGET in plugin_test_ios #91324
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
Conversation
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.
LGTM, but could you update the PR description to explain why the number is changing, so that it's clear to future people why this is correct (and not masking a regression as described in the comment just above this code)?
@@ -179,7 +179,7 @@ class _FlutterProject { | |||
// The plugintest target should not have IPHONEOS_DEPLOYMENT_TARGET set. | |||
// See _reduceDarwinPluginMinimumVersion for details. | |||
final int iosDeploymentTargetCount = 'IPHONEOS_DEPLOYMENT_TARGET'.allMatches(podsProjectContent).length; | |||
if (iosDeploymentTargetCount != 9) { | |||
if (iosDeploymentTargetCount != 12) { |
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.
Should the comment above that says "6 times" be updated too? (It already didn't match, so maybe there's a distinction between the two numbers that I'm missing.)
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.
You're right, this is lame. Let me rework this check.
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 updated the description, test logic, and comment.
This may be a bit brittle
Thanks, past Jenn.
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.
LGTM
Change the integration test #72764 to explicitly check that the too-low plugin version number has been removed, instead of the expected build setting count. Which, as expected, was brittle...
Follow up to #91099
Will allow this test to be turned back on #88794