Display a warning if device CPU architecture is not active in the export preset.

[Alex2782]

Fixes #86284

Editor crash / freeze (with arm32 devices) are prevented by selecting the correct device CPU architecture. It should also be more user-friendly. #86284 (comment)

[Alex2782]

@m4gr3d

I also tried to intercept the 'freeze' somehow. It gets stuck at fgets(buf, 65535, f) (src), because adb install also gets stuck in the terminal window, does not give any errors. (on my arm32 devices)

logcat

02-23 01:06:37.626  2915  3058 W NativeHelper: Failure copying native libraries [errorCode=-113]
02-23 01:06:37.626  2915  3058 E PackageInstaller: Commit of session 786393543 failed: Failed to extract native libraries, res=-113

[m4gr3d]

This updated approach looks good to me!

I wonder if it's worth adding an additional Fix and run button to the confirm dialog to automatically add the missing architecture as your previous approach was doing, though that may make the UX looks busy.

cc @Calinou Any thoughts on the UX used in this PR?

[Calinou]

I wonder if it's worth adding an additional Fix and run button to the confirm dialog to automatically add the missing architecture as your previous approach was doing, though that may make the UX looks busy.

This should be done if we want to provide a "Run Remote Debug anyway" button, as the button is unlikely to work otherwise. This is even more the case with Android 14 and later which is no longer able to run 32-bit ARM apps on 64-bit ARM devices (to my knowledge).

[Alex2782]

I think adb should somehow be executed in a Thread so that the cancel button works properly. The progress window looks incorrect in the first 2 seconds because rendering is blocked. Which godot function could be used as an example?

[akien-mga]

Thanks!

[Alex2782]

Fix and run button maybe later (new PR).