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
Building a new_gallery with a local profile or release engine fails #104667
Comments
/cc @GaryQian @christopherfujino @blasten in case one of you knows what's up |
This failure seems to fail at the |
I'm getting errors around it not finding the plugin related classes locally, e.g.
|
Ahh, this may be different then Ill look. |
I'm using local engine and debug as I type, does it work if you use debug? I used profile a week or so ago with plugins. |
Debug works, profile does not - but only if you have deferred app components (i.e. new_gallery) |
To unlock this, is it possible to remove the deferred component ? |
Yeah, you can build with the --no-deferred-components flag, The app will just build it into one single appbundle |
It does mean that contributors can't run the same benchmark as on CI though. |
Where is new_gallery? |
https://github.com/flutter/gallery @rmacnak-google I don't think this is a gen_snapshot issue - I think there's some issue with Flutter's gradle build rules, where we might not be giving some part of the deferred component build the right JARs or something |
Related: #97149 and flutter/gallery#926 |
But it succeeds if you remove the deferred components.
Seems like there's something wrong with deferred component logic when using a local engine.
This makes it harder to test performance experiments in local engine builds on Android.
The text was updated successfully, but these errors were encountered: