Skip to content

New Android embedding is only enabled on master #45453

Closed

Description

@tvolkert

hostonly_devicelab_tests are failing only in non-master branches on Cirrus with the following error.

[module_test] [STDOUT] stderr: /private/var/folders/sy/2x5qvs0n4lg18fry9jz4y21m0000gn/T/flutter_module_test.vOxl3v/hello_host_app/app/src/main/java/io/flutter/add2app/MainActivity.java:11: error: incompatible types: FlutterEngine cannot be converted to PluginRegistry
[module_test] [STDOUT] stderr:     GeneratedPluginRegistrant.registerWith(flutterEngine);
[module_test] [STDOUT] stderr:    

For example: https://cirrus-ci.com/task/4684340952301568

Activity

  1. xster commented on Nov 23, 2019

    @xster
    Member

    cc @blasten, not sure if there's anything to do there since the state of the code at tip of tree is very different now, but it looks like this registration is using a new embedding with old plugins directly without shim

  2. tvolkert commented on Dec 3, 2019

    @tvolkert
    ContributorAuthor

    This is failing on beta channel with v1.12.13+hotfix.1, which is very new.

    https://cirrus-ci.com/task/6300811973361664

    @blasten @matthew-carroll thoughts?

  3. matthew-carroll commented on Dec 3, 2019

    @matthew-carroll
    Contributor

    The following leads me to believe that the flutter tool is generating the wrong version of the plugin registrant:

    [module_test] [STDOUT] stderr: C:\Users\ContainerAdministrator\AppData\Local\Temp\flutter_module_test.884c5db6-1601-11ea-aad5-8bd5e2fead93\hello\.android\Flutter\src\main\java\io\flutter\facade\Flutter.java:98: error: incompatible types: FlutterPluginRegistry cannot be converted to FlutterEngine
    [module_test] [STDOUT] stderr:         GeneratedPluginRegistrant.registerWith(flutterView.getPluginRegistry());
    [module_test] [STDOUT] stderr:                                                                             ^
    

    Given that the project is referencing a flutterView, I think it should be using the old registrant version, but it appears to be using the new registrant version.

    @blasten

  4. blasten commented on Dec 3, 2019

    @blasten
  5. matthew-carroll commented on Dec 4, 2019

    @matthew-carroll
    Contributor

    @blasten can you patch that to allow us to roll to other channels?

  6. tvolkert commented on Dec 4, 2019

    @tvolkert
    ContributorAuthor

    That would explain it!

    That's definitely something we should fix ASAP since we want the new embedding enabled in our next stable release. Marking as a release blocker, which means I'll gladly accept cherry-pick of tested PRs 🙂

  7. added
    a: existing-appsIntegration with existing apps via the add-to-app flow
    platform-androidAndroid applications specifically
    and removed
    c: contributor-productivityTeam-specific productivity, code health, technical debt.
    on Dec 4, 2019
  8. changed the title [-]hostonly_devicelab_tests failing on dev and beta branches[/-] [+]New Android embedding is only enabled on master[/+] on Dec 4, 2019
  9. tvolkert commented on Dec 4, 2019

    @tvolkert
    ContributorAuthor

    This has been cherry-picked in v1.12.13+hotfix.2, so removing the release blocker label.

  10. github-actions commented on Aug 25, 2021

    @github-actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  11. locked as resolved and limited conversation to collaborators on Aug 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

a: existing-appsIntegration with existing apps via the add-to-app flowplatform-androidAndroid applications specifically

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions