Fat Binaries (arm64-v8a, armeabi-v7a, x86, & x86_64 )

[Darcy Schultz]

With our current android app we ship arm64-v8a, armeabi-v7a, x86, & x86_64 binaries in a Fat APK.  The Flutter build system only seems to include armeabi-v7a flutter binaries by default and doesn’t seem to support x86 at all.  As such, a Flutter app will fail to start on a non-matching device.  Related Github issues are https://github.com/flutter/flutter/issues/9253 and https://github.com/flutter/flutter/issues/18494  I'm looking for some visibility into the schedule for these issues so that we can plan our activities.  Should I expect these to be fixed? when?  Thanks!

[eseidel]

Dan Field mentioned on https://github.com/flutter/flutter/issues/18494 that he would try to look.  Beyond that we have no schedule to share.

Flutter is growing so fast, mostly my teams (and the wider community) are just trying to keep up with the massive, massive user growth and the resulting highest rated bugs:

https://github.com/flutter/flutter/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc

as well as of course the various requests which come in from big customers inside Google or from the public. :)

This feels like something which relates both to the upcoming 64-bit transition for the Play Store:

https://android-developers.googleblog.com/2019/01/get-your-apps-ready-for-64-bit.html

as well as our in-progress "make it easier to add Flutter to your existing application" efforts, as seen on our public roadmap:

https://github.com/flutter/flutter/wiki/Roadmap

I would expect to see progress on these bugs in the coming months, but again I have not guarantees.

Flutter is 100% open source and patches are always welcome! :D

Sorry I don't have more specifics.