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

[CP-stable] Add empty io.flutter.app.FlutterApplication to give deprecation notice, and un-break projects that have not migrated #164730

Conversation

gmackall
Copy link
Member

@gmackall gmackall commented Mar 6, 2025

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 migration

Impact 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 an android.app.Application. There is no reason to extend a FlutterApplication.

Risk:

What is the risk level of this cherry-pick?

  • Low
  • Medium
  • High

Test Coverage:

Are you confident that your fix is well-tested by automated tests?

  • Yes
  • No (it is on master, but due to a CI bug it can't be on this branch)

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:

# from the .../flutter/dev/devicelab directory
../../bin/cache/dart-sdk/bin/dart bin/test_runner.dart test -t spell_check_test

@github-actions github-actions bot added platform-android Android applications specifically engine flutter/engine repository. See also e: labels. labels Mar 6, 2025
@gmackall gmackall changed the title engine portion of original change [CP-stable] Add empty io.flutter.app.FlutterApplication to give deprecation notice, and un-break projects that have not migrated Mar 6, 2025
@gmackall gmackall marked this pull request as ready for review March 6, 2025 18:35
@gmackall gmackall requested a review from a team March 6, 2025 18:35
@reidbaker reidbaker requested a review from camsim99 March 6, 2025 18:53
Copy link
Contributor

@reidbaker reidbaker left a 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.

@camsim99 camsim99 added cp: review Cherry-picks in the review queue cp: approved Approved cherry-pick request labels Mar 6, 2025
@reidbaker reidbaker added the cp: stable cherry pick this pull request to stable release candidate branch label Mar 10, 2025
@reidbaker reidbaker added the autosubmit Merge PR when tree becomes green via auto submit App label Mar 11, 2025
Copy link
Contributor

auto-submit bot commented Mar 11, 2025

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.

@auto-submit auto-submit bot removed the autosubmit Merge PR when tree becomes green via auto submit App label Mar 11, 2025
@jesswrd jesswrd added the autosubmit Merge PR when tree becomes green via auto submit App label Mar 11, 2025
@auto-submit auto-submit bot removed the autosubmit Merge PR when tree becomes green via auto submit App label Mar 11, 2025
Copy link
Contributor

auto-submit bot commented Mar 11, 2025

autosubmit label was removed for flutter/flutter/164730, because Pull request flutter/flutter/164730 is not in a mergeable state.

@reidbaker reidbaker added the autosubmit Merge PR when tree becomes green via auto submit App label Mar 11, 2025
@auto-submit auto-submit bot merged commit 2cee248 into flutter:flutter-3.29-candidate.0 Mar 11, 2025
150 checks passed
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Mar 14, 2025
…give deprecation notice, and un-break projects that have not migrated (flutter/flutter#164730)
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Mar 14, 2025
…give deprecation notice, and un-break projects that have not migrated (flutter/flutter#164730)
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Mar 15, 2025
…give deprecation notice, and un-break projects that have not migrated (flutter/flutter#164730)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
autosubmit Merge PR when tree becomes green via auto submit App cp: approved Approved cherry-pick request cp: review Cherry-picks in the review queue cp: stable cherry pick this pull request to stable release candidate branch engine flutter/engine repository. See also e: labels. platform-android Android applications specifically
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants