Status Update
No update yet.
Comments
rk...@google.com
jo...@google.com
We're seeing a similar error in our code. Appears to be a combination of AGP 8.6.0 and Kotlin 2 needed to hit it.
private fun Intent.stripUnwantedFlags() {
// Explicitly remove the new task and clear task flags (Our browser activity is a single
// task activity and we never want to start a second task here).
flags = flags and Intent.FLAG_ACTIVITY_NEW_TASK.inv()
flags = flags and Intent.FLAG_ACTIVITY_CLEAR_TASK.inv()
// IntentReceiverActivity is started with the "excludeFromRecents" flag (set in manifest). We
// do not want to propagate this flag from the intent receiver activity to the browser.
flags = flags and Intent.FLAG_ACTIVITY_EXCLUDE_FROM_RECENTS.inv()
}
All 3 lines then hit:
Must be one or more of: Intent.FLAG_GRANT_READ_URI_PERMISSION, Intent.FLAG_GRANT_WRITE_URI_PERMISSION, Intent.FLAG_FROM_BACKGROUND, Intent.FLAG_DEBUG_LOG_RESOLUTION, Intent.FLAG_EXCLUDE_STOPPED_PACKAGES, Intent.FLAG_INCLUDE_STOPPED_PACKAGES, Intent.FLAG_GRANT_PERSISTABLE_URI_PERMISSION, Intent.FLAG_GRANT_PREFIX_URI_PERMISSION, Intent.FLAG_ACTIVITY_MATCH_EXTERNAL, Intent.FLAG_ACTIVITY_NO_HISTORY, Intent.FLAG_ACTIVITY_SINGLE_TOP, Intent.FLAG_ACTIVITY_NEW_TASK, Intent.FLAG_ACTIVITY_MULTIPLE_TASK, Intent.FLAG_ACTIVITY_CLEAR_TOP, Intent.FLAG_ACTIVITY_FORWARD_RESULT, Intent.FLAG_ACTIVITY_PREVIOUS_IS_TOP, Intent.FLAG_ACTIVITY_EXCLUDE_FROM_RECENTS, Intent.FLAG_ACTIVITY_BROUGHT_TO_FRONT, Intent.FLAG_ACTIVITY_RESET_TASK_IF_NEEDED, Intent.FLAG_ACTIVITY_LAUNCHED_FROM_HISTORY, Intent.FLAG_ACTIVITY_CLEAR_WHEN_TASK_RESET, Intent.FLAG_ACTIVITY_NEW_DOCUMENT, Intent.FLAG_ACTIVITY_CLEAR_WHEN_TASK_RESET, Intent.FLAG_ACTIVITY_NO_USER_ACTION, Intent.FLAG_ACTIVITY_REORDER_TO_FRONT, Intent.FLAG_ACTIVITY_NO_ANIMATION, Intent.FLAG_ACTIVITY_CLEAR_TASK, Intent.FLAG_ACTIVITY_TASK_ON_HOME, Intent.FLAG_ACTIVITY_RETAIN_IN_RECENTS, Intent.FLAG_ACTIVITY_LAUNCH_ADJACENT, Intent.FLAG_ACTIVITY_REQUIRE_NON_BROWSER, Intent.FLAG_ACTIVITY_REQUIRE_DEFAULT, Intent.FLAG_RECEIVER_REGISTERED_ONLY, Intent.FLAG_RECEIVER_REPLACE_PENDING, Intent.FLAG_RECEIVER_FOREGROUND, Intent.FLAG_RECEIVER_NO_ABORT, Intent.FLAG_RECEIVER_VISIBLE_TO_INSTANT_APPS
ru...@gmail.com
The initial report (
However,
ru...@gmail.com
Thanks for fixing! What release should we be able to verify the fix in? And is there any chance of a backport for 8.6.1?
ru...@gmail.com
Thanks for the update!
jo...@google.com
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Studio Ladybug Feature Drop | 2024.2.2 Canary 2
- Android Gradle Plugin 8.8.0-alpha02
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
ru...@gmail.com
The fixes for this issue are now also available in:
- Android Studio Ladybug | 2024.2.1 RC 1
- Android Gradle Plugin 8.7.0-rc01
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
ru...@gmail.com
Hi, any news on qt 6.5.3 aarch64 update?
jo...@google.com
Hi, I have a local emulator build with updated Qt6 prebuilts. Could you please try and let me know if it works? Thanks!
ru...@gmail.com
I immediately get /lib/aarch64-linux-gnu/libc.so.6: version GLIBC_2.36' not found (required by /home/appetizer/emulator/lib64/libstdc++.so.6)` - most likely this was compiled on a newer system? I am on ubuntu 22.04 which has glibc 2.35 but i can try upgrading to 22.10
jo...@google.com
Hmm, I used a docker image based on ubuntu focal. The GLIBC version on it is 2.31. Maybe we are distributing a different libstdc++.so.6.
Could you try replacing the libstdc++.so.6 in /home/appetizer/emulator/lib64/ with the one in your sysroot (located probably in /lib/aarch64-linux-gnu).
In the meantime, I'll update the emulator prebuilt.
ru...@gmail.com
I was trying to validate what is going on in the background and yeah glibc 2.36 is pulled in by libstdc++:
./emulator: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.36' not found (required by /home/appetizer/emulator/./lib64/libstdc++.so.6)
libc.so.6 (GLIBC_2.36) => not found
The version from your build seemes to have GLIBCXX_3.4.42 macro, where as the last one I had laying around from ci.google.com had GLIBCXX_3.4.28. Ok, ill try to replace it with the sysrooted one.
ru...@gmail.com
Replacing libstdc++ with the sysrooted one did work, emulator seems to be working, thank you very much - this is much snappier than the arhaic arm version I was using.
Btw when trying to shut it down via the power button on the side bar i got:
INFO | Warning: QMetaObject::connectSlotsByName: No matching signal for on_rgbcSensorValueWidget_valueChanged() ((null):0, (null))
INFO | Warning: QMetaObject::connectSlotsByName: No matching signal for on_posture_valueChanged(int) ((null):0, (null))
WARNING | UpdateCheck: Failure: Error
ERROR | Error reading vhal json
but well that is most likely a separate issue.
I'll be eagerly awaiting an official build, but the main problem seems to be solved - the window comes up and seems to work so seem that the qt prebuilts are ok:) Does this also then mean that all emulator 35.x releases (x86_64 as well) will have the libstdc++ version bump?
jo...@google.com
Does this also then mean that all emulator 35.x releases (x86_64 as well) will have the libstdc++ version bump?
Only the linux-aarch64 target uses libstdc++ (all other targets ship with libc++). Also, the libstdc++ version we ship will not change from the current 34.x and 35.x releases; my local build had a newer version of libstdc++, but the buildbot used to build the release builds did not change.
ru...@gmail.com
Thanks for the clarification - I double checked that myself today and yeah the latest aarch64 build from ci.android.com had older libstdc++ than your build. So everything seems great, thanks for the help here. Are the qt prebuilts merged in already?
jo...@google.com
ru...@gmail.com
Ok,thanks a lot:)
Description
DESCRIBE THE ISSUE IN DETAIL:
The latest linux-aarch64 emulators fromhttps://ci.android.com/ crash for me with the following output
and following stack trace:
while my own debug build from emu-master-dev seems to behave similarly, it actually gives some errors about missing xcb plugin:
and then also fails with SIGABRT:
Looking at this changeset (https://android-review.googlesource.com/c/platform/prebuilts/android-emulator-build/qt/+/2976235 ) does show that all those plugins were removed during the qt 6.5.3 prebuilts update so the crash seems logical. Thus i have the following questions:
STEPS TO REPRODUCE:
ATTACH SCREENSHOTS/RECORDINGS OF THE ISSUE
ATTACH LOG FILES (Select Help > Show Log in Files, or Show Log in Finder on a Mac)
IMPORTANT: Please readhttps://developer.android.com/studio/report-bugs.html carefully and supply
all required information.
Studio Build: Version of Gradle Plugin: Version of Gradle: Version of Java: OS: