-
Notifications
You must be signed in to change notification settings - Fork 28.2k
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
[CP-stable] Add empty io.flutter.app.FlutterApplication to give deprecation notice, and un-break projects that have not migrated #164730
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, We dont want to land this until @camsim99 is done pushing 3.29.1.
autosubmit label was removed for flutter/flutter/164730, because - The status or check suite Linux analyze has failed. Please fix the issues identified (or deflake) before re-applying this label. |
autosubmit label was removed for flutter/flutter/164730, because Pull request flutter/flutter/164730 is not in a mergeable state. |
2cee248
into
flutter:flutter-3.29-candidate.0
…give deprecation notice, and un-break projects that have not migrated (flutter/flutter#164730)
…give deprecation notice, and un-break projects that have not migrated (flutter/flutter#164730)
…give deprecation notice, and un-break projects that have not migrated (flutter/flutter#164730)
This is just the engine portion of #164343. I.e., it does not contain the test change.
Copied from the original cherry pick pr:
This pull request is created by automatic cherry pick workflow
Please fill in the form below, and a flutter domain expert will evaluate this cherry pick request.
Issue Link:
What is the link to the issue this cherry-pick is addressing?
#164024
Changelog Description:
Explain this cherry pick in one line that is accessible to most Flutter developers. See best practices for examples
#164024: Add back an empty
io.flutter.app.FlutterApplication
for Android apps that reference that class post v2 embedder migrationImpact Description:
What is the impact (ex. visual jank on Samsung phones, app crash, cannot ship an iOS app)? Does it impact development (ex. flutter doctor crashes when Android Studio is installed), or the shipping production app (the app crashes on launch)
The class does not provide any additional funcitonality, but it class was removed without sufficient notice in the breaking changes section of the Flutter documentation. As such, consumers of this class were broken without sufficient time to migrate.
Workaround:
Is there a workaround for this issue?
Flutter projects which need a custom
Application
can instead simply extend anandroid.app.Application
. There is no reason to extend aFlutterApplication
.Risk:
What is the risk level of this cherry-pick?
Test Coverage:
Are you confident that your fix is well-tested by automated tests?
Validation Steps:
What are the steps to validate that this fix works?
Either make a flutter app which depends on this class, or run the spell check integration tests: