Crash Release Android x86

[rod-moraes]

This bug is reproducible when you generate the app using in release mode and you open it in an x86 or arm32 emulator

If you are having issues opening an app on your x86 or arm32 emulator, you may be seeing the following error message: "{AppName} consistently crashes". This may be caused by the fact that Flutter does not support x86 files, as mentioned in this link: https://docs.flutter.dev/deployment/android#what-are-the-supported-target-architectures. According to the documentation, Flutter currently does not offer support for generating x86 files for Android (see Issue 9253).

This can be a particularly problematic when you are trying to use packages that depend on resources such as the camera or MLKit. To resolve this issue, you can edit the 'build.grandle' file in the 'app' folder and add the following lines to prevent the generation of x86 files:

   defaultConfig {
        ndk {
            abiFilters 'armeabi-v7a','arm64-v8a','x86_64'
        }
    }

This should help resolve the issue and allow you to open the app on the emulator without errors. It is important to remember that Flutter currently only supports the armeabi-v7a (ARM 32-bit), arm64-v8a (ARM 64-bit), and x86-64 (x86 64-bit) target architectures. Therefore, when editing the 'build.grandle' file, it is important to ensure that you are only including these architectures.

[exaby73]

Hello @rod-moraes. Are you raising an issue here or providing information to other developers facing an issue? If the latter, I do not think Guthub issues are the best place for this. Github issues are meant for raising bugs or requesting features. If this "bug" you're mentioning already has a fix, then it cannot be considered a bug and would make this issue invalid. Please clarify on this

[rod-moraes]

Well, I don't know about you, but I investigate certain problems in Github issues, since they are very specific things, even if there is a stackoverflow, I still think that the github of the language is a good place to keep a history of problems x solutions. See the issue where it talks about x86 architecture support

[exaby73]

There are communities you can find on https://flutter.Dev/community where this might be more valid to post on

[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.