For my own understanding can you give an example log output that might change what this code does to fix the issue?
Are we hoping that the libraries are there but in an unexpected path? or are we hoping to show that the libraries are not there and that this is a tooling issue in apk delivery or something else?

For my own understanding can you give an example log output that might change what this code does to fix the issue? Are we hoping that the libraries are there but in an unexpected path? or are we hoping to show that the libraries are not there and that this is a tooling issue in apk delivery or something else?

For an app bundle, the output will look something like this

05-12 16:21:04.470 16731 16731 E FlutterLoader: App is using cpu architecture: aarch64, and the native libraries directory (with path /data/app/~~s0585eApe59QLdC1zYUiiw==/com.example.flutter_app_20250425_06-h2hMrlqiR3GGfRT_VRtbWw==/lib/arm64) contains the following files: [], and the split and source libraries directory (with path(s) [/data/app/~~s0585eApe59QLdC1zYUiiw==/com.example.flutter_app_20250425_06-h2hMrlqiR3GGfRT_VRtbWw==/split_config.arm64_v8a.apk!/lib/arm64-v8a, /data/app/~~s0585eApe59QLdC1zYUiiw==/com.example.flutter_app_20250425_06-h2hMrlqiR3GGfRT_VRtbWw==/split_config.en.apk!/lib/arm64-v8a, /data/app/~~s0585eApe59QLdC1zYUiiw==/com.example.flutter_app_20250425_06-h2hMrlqiR3GGfRT_VRtbWw==/split_config.xxhdpi.apk!/lib/arm64-v8a, /data/app/~~s0585eApe59QLdC1zYUiiw==/com.example.flutter_app_20250425_06-h2hMrlqiR3GGfRT_VRtbWw==/base.apk!/lib/arm64-v8a]).

I went back and forth on whether it was worth reading the archived file contents in the apks - at that point, we'd basically be re-writing ReLinker. The first reason to do this is to give a more complete picture of where we are actually looking for the library. As the exception today states that it's only looking in the native library directory - which is not the full picture. I believe the benefit is to look for CPU architecture inconsistencies (for some reason if the phone is reporting the incorrect CPU arch - which seems to be the leading hypothesis as to why sometimes the libflutter.so file cannot be found in bundled installs).

autosubmit label was removed for flutter/flutter/168706, because - The status or check suite Linux linux_web_engine_tests has failed. Please fix the issues identified (or deflake) before re-applying this label.

Looks like engine artifacts are completed (at least for the last sha). I'll look at logs for FRoB

autosubmit label was removed for flutter/flutter/168706, because - The status or check suite Linux linux_fuchsia_tests has failed. Please fix the issues identified (or deflake) before re-applying this label.