Deprecate support for ia32

@bkonyi

Dart is considering dropping support for ia32, please see dart-lang/sdk#49969 for more context.

This issue is to ensure Flutter goes through a deprecation process before removing support for ia32.

List of items to consider

remove support for jit release mode which is tracked here Remove JIT release x86 mode #151610
make an announcement to external developers about the intent to drop support for ia32, this could be done by having Flutter tools issue a warning whenever the x86 emulator is used (Please see Detect x86 Android device or emulator and log warning. #158953)
switch Flutter tools to use x86_64 by default (switch to use a different ABI, apparently AS: 31 and above ABI uses x86_64)
After one beta cycle of issuing the warning, remove support for ia32 in flutter tools

//cc @bkonyi

Add deprecation notice for Android x86 when building for the target

Add deprecation notice for Android x86 when building for the target (#…

Add deprecation notice for Android x86 when building for the target (f…

[CP-beta]Add deprecation notice for Android x86 when building for the…

Hi, if I may ask, why deprecate x86 tho

Hi, if I may ask, why deprecate x86 tho

x86 has always been a maintenance burden for the Dart VM and is the only architecture that doesn't support our ahead-of-time (AOT) compilation pipeline (partly due to the limited number of CPU registers which would prevent a lot of code being shared between the implementations for other architectures) that Flutter uses for release quality builds. Given that x86 is becoming less and less common, especially for Android devices, the install base is small enough that it's no longer worth maintaining.

fair enough. Thank you flutter and flutter team :)

…

On Mon, Feb 10, 2025 at 5:02 PM Ben Konyi ***@***.***> wrote: Hi, if I may ask, why deprecate x86 tho x86 has always been a maintenance burden for the Dart VM and is the only architecture that doesn't support our ahead-of-time (AOT) compilation pipeline (partly due to the limited number of CPU registers which would prevent a lot of code being shared between the implementations for other architectures) that Flutter uses for release quality builds. Given that x86 is becoming less and less common, especially for Android devices, the install base is small enough that it's no longer worth maintaining. — Reply to this email directly, view it on GitHub <#157543 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A3ZDBO4CLM3KI456JHZGVFL2PDESLAVCNFSM6AAAAABQRWB3O6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBYGUYDEMJUHA> . You are receiving this because you commented.Message ID: ***@***.***>

Support for Android x86 targets will be removed in the next stable release after 3.27. See #157543 for details.
Running Gradle task 'assembleDebug'...

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:mapDebugSourceSetPaths'.

Error while evaluating property 'extraGeneratedResDir' of task ':app:mapDebugSourceSetPaths'.
Failed to calculate the value of task ':app:mapDebugSourceSetPaths' property 'extraGeneratedResDir'.
> Querying the mapped value of provider(java.util.Set) before task ':app:processDebugGoogleServices' has completed is not supported

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
Get more help at https://help.gradle.org.

BUILD FAILED in 16s
Error: Gradle task assembleDebug failed with exit code 1

@YahalomsGuy

What happens to apps working on Smart TVs ?
Most (if not all) embedded operating systems on the televisions are based on x86 architacture (androidOs and other)

@YahalomsGuy (or @trassos or @VEMUC002) can you clarify which TV devices/models/hardware you're talking about? And on which version of Flutter you're using to run on those devices? JIT release x86 was removed in flutter-team-archive/engine#56681. Are you building your own Flutter engine?

Even all the emulators I could find to debug an app are x86.

Can you clarify exactly what x86 emulator you're finding?

Does it mean that from now one should connect a x64 based device to work with a TV ?

Do you mean connect an x64 host device running Flutter, tethered to a TV? Or do you mean you're running on some kind of smart TV stick?

Thanks for any specifics here.

@jmagman

@jmagman @YahalomsGuy
Although I’ve marked those comments favorably, my primary concern differs slightly. I’m more focused on older and widely rebranded/revised white-label POS devices.

Take the RK3288, for example. If we freeze our Flutter project on version 3.27, will it remain functional on this chip?

There are also several x64 CPUs that, while technically compatible, suffer from notable performance issues — including the J3455, J4125, N4020, J6412, and J1900.

In most cases, devices using this hardware come with less than 4 GB of RAM and run some form of customized/stripped Android.

@trassos

RK3288

@trassos That's ARM32, not x86, so wouldn't be impacted by this change. https://dart.dev/get-dart#system-requirements
If you are aware of x86 hardware you think we should support, please let us know the devices/models.

What to do with virtual TV devices? They are all x86.

What to do with virtual TV devices? They are all x86.

In x86 computers , you can only install x86 emulators
But in computers with ARM processors (like Mac Silicon / M series) computers, you can add ARM based emulators.

What to do with virtual TV devices? They are all x86.

In x86 computers , you can only install x86 emulators But in computers with ARM processors (like Mac Silicon / M series) computers, you can add ARM based emulators.

Solution to the problem: a new PC?
Preferred ABI in most mobile virtual devices has arm, but TV only has x86.
Maybe there's something I don't know?

What to do with virtual TV devices? They are all x86.

The support that was dropped was 32 bit x86 devices not all x86 devices.

What to do with virtual TV devices? They are all x86.

The support that was dropped was 32 bit x86 devices not all x86 devices.
But why do I see that?

Support for Android x86 targets will be removed in the next stable release after 3.27. See #157543 for details.

@Farg0k

@Farg0k
Where do you see "Support for Android x86 targets will be removed in the next stable release after 3.27. See #157543 for details."

Hopefully it is someplace I can update. FWIW that bug does say that x86_64 is supported.

@Farg0k Where do you see "Support for Android x86 targets will be removed in the next stable release after 3.27. See #157543 for details."

Hopefully it is someplace I can update. FWIW that bug does say that x86_64 is supported.

Looks like there's just a stray constant that's not actually referenced anywhere:

flutter/packages/flutter_tools/lib/src/android/gradle.dart

Line 136 in 6e9286d

const androidX86DeprecationWarning =

I'll remove it.

@Farg0k

AH, we probably printed that warning, which was poorly worded, on an older version of flutter so there is no documentation to update.

Sorry for any stress we caused you @Farg0k.

[ Tool ] Remove leftover Android x86 deprecation warning constant (#1…

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.

Navigation Menu

Repository navigation

Deprecate support for ia32 #157543

27 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Deprecate support for ia32 #157543

Description

Activity

nathfavour commented on Feb 1, 2025

bkonyi commented on Feb 10, 2025

nathfavour commented on Feb 10, 2025

KannRangsey commented on Feb 14, 2025

27 remaining items

jmagman commented on Jul 8, 2025

trassos commented on Jul 9, 2025

jmagman commented on Jul 11, 2025

Farg0k commented on Sep 2, 2025

YahalomsGuy commented on Sep 2, 2025

Farg0k commented on Sep 2, 2025

reidbaker commented on Sep 2, 2025

Farg0k commented on Sep 3, 2025

reidbaker commented on Sep 4, 2025

bkonyi commented on Sep 4, 2025

reidbaker commented on Sep 4, 2025

github-actions commented on Sep 18, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions