Google Git Google Git
Sign in
android/platform/frameworks/support/886ac5
commit
886ac5a0761e7dfb83b79e3519a6408e11aaa9ca
[log]
author
Daniel Santiago Rivera <danysantiago@google.com>
Fri Aug 07 11:24:10 2026 -0400
committer
Android Build Coastguard Worker <android-build-coastguard-worker@google.com>
Wed Aug 12 13:26:47 2026 -0700
tree
bbd934c474cb153fa4a2da9278e77b367fc085ac
parent
4762f876f4d43c4c8853d8887f9b110fe25777e6 [diff] 
Mark suspend DAO @Transaction delegates as external operations.

A @Transaction delegate in a DAO has user-code that might switch dispatchers and cause databases with a passthrough pool (AndroidSQLiteDriver) to deadlock due to a change of thread. There an optimization to not hop to the transaction thread for 'internal' Room operations but that is only safe knowing no dispatcher change occurs, something that can't be guaranteed with transaction delegates in DAOs.

Bug: 543285472
Test: SuspendingQueryTest
Cherrypick-From: https://android-review.googlesource.com/q/commit:ebd4a3d8e835f6aae6f39d4ee313accbf6031e23
Merged-In: I20a6ac10b9884691490860a02b7c1d2ec732642f
Change-Id: I20a6ac10b9884691490860a02b7c1d2ec732642f
3 files changed
tree: bbd934c474cb153fa4a2da9278e77b367fc085ac
  1. .agents/
  2. .github/
  3. .idea/
  4. a2ui/
  5. activity/
  6. androidx-settings-plugins/
  7. annotation/
  8. appcompat/
  9. appfunctions/
  10. appsearch/
  11. appstate/
  12. arch/
  13. asynclayoutinflater/
  14. autofill/
  15. benchmark/
  16. binarycompatibilityvalidator/
  17. biometric/
  18. browser/
  19. buildSrc/
  20. buildSrc-tests/
  21. busytown/
  22. camera/
  23. car/
  24. cardview/
  25. collection/
  26. compose/
  27. concurrent/
  28. constraintlayout/
  29. coordinatorlayout/
  30. core/
  31. credentials/
  32. cursoradapter/
  33. customview/
  34. datastore/
  35. development/
  36. docs/
  37. docs-public/
  38. docs-tip-of-tree/
  39. documentfile/
  40. draganddrop/
  41. drawerlayout/
  42. dynamicanimation/
  43. emoji/
  44. emoji2/
  45. enterprise/
  46. exifinterface/
  47. external/
  48. fragment/
  49. glance/
  50. gradle/
  51. graphics/
  52. gridlayout/
  53. health/
  54. heifwriter/
  55. hilt/
  56. ink/
  57. input/
  58. inspection/
  59. interpolator/
  60. javascriptengine/
  61. kotlin-js-store/
  62. kruth/
  63. leanback/
  64. lifecycle/
  65. lint/
  66. lint-checks/
  67. loader/
  68. mediarouter/
  69. metrics/
  70. navigation/
  71. navigation3/
  72. navigationevent/
  73. paging/
  74. palette/
  75. pdf/
  76. percentlayout/
  77. photopicker/
  78. placeholder/
  79. placeholder-tests/
  80. playground-common/
  81. playground-projects/
  82. preference/
  83. print/
  84. privacysandbox/
  85. profileinstaller/
  86. recommendation/
  87. recyclerview/
  88. resourceinspection/
  89. room3/
  90. safeparcel/
  91. samples/
  92. savedstate/
  93. security/
  94. sharetarget/
  95. slidingpanelayout/
  96. sqlite/
  97. stableaidl/
  98. startup/
  99. swiperefreshlayout/
  100. test/
  101. testutils/
  102. text/
  103. tracing/
  104. transition/
  105. tv/
  106. tvprovider/
  107. vectordrawable/
  108. versionedparcelable/
  109. viewpager/
  110. viewpager2/
  111. wear/
  112. webgpu/
  113. webkit/
  114. window/
  115. work/
  116. xr/
  117. .gitignore
  118. AGENTS.md
  119. build.gradle
  120. cleanBuild.sh
  121. code-review.md
  122. CONTRIBUTING.md
  123. gradle.properties
  124. gradlew
  125. libraryversions.toml
  126. license-baseline.txt
  127. LICENSE.txt
  128. MOLECULE_UI_OWNERS
  129. OWNERS
  130. PREUPLOAD.cfg
  131. README.md
  132. settings.gradle
  133. studiow
  134. TAG_OWNERS
  135. TEXT_OWNERS
  136. updateAbi.log
README.md

Android Jetpack

Revved up by Develocity

Jetpack is a suite of libraries, tools, and guidance to help developers write high-quality apps easier. These components help you follow best practices, free you from writing boilerplate code, and simplify complex tasks, so you can focus on the code you care about.

Jetpack comprises the androidx.* package libraries, unbundled from the platform APIs. This means that it offers backward compatibility and is updated more frequently than the Android platform, making sure you always have access to the latest and greatest versions of the Jetpack components.

Our official AARs and JARs binaries are distributed through Google Maven.

You can learn more about using it from Android Jetpack landing page.

Contribution Guide

For contributions via GitHub, see the GitHub Contribution Guide.

Note: The contributions workflow via GitHub is currently experimental - only contributions to the following projects are being accepted at this time:

Code Review Etiquette

When contributing to Jetpack, follow the code review etiquette.

Accepted Types of Contributions

  • Bug fixes - needs a corresponding bug report in the Android Issue Tracker
  • Each bug fix is expected to come with tests
  • Fixing spelling errors
  • Updating documentation
  • Adding new tests to the area that is not currently covered by tests
  • New features to existing libraries if the feature request bug has been approved by an AndroidX team member.

We are not currently accepting new modules.

Checking Out the Code

Head over to the onboarding docs to learn more about getting set up and the development workflow!

Continuous integration

Our continuous integration system builds all in progress (and potentially unstable) libraries as new changes are merged. You can manually download these AARs and JARs for your experimentation.

Password and Contributor Agreement before making a change

Before uploading your first contribution, you will need setup a password and agree to the contribution agreement:

Generate a HTTPS password: https://android-review.googlesource.com/new-password

Agree to the Google Contributor Licenses Agreement: https://android-review.googlesource.com/settings/new-agreement

Getting reviewed

  • After you run repo upload, open r.android.com
  • Sign in into your account (or create one if you do not have one yet)
  • Add an appropriate reviewer (use git log to find who did most modifications on the file you are fixing or check the OWNERS file in the project's directory)

Handling binary dependencies

AndroidX uses git to store all the binary Gradle dependencies. They are stored in prebuilts/androidx/internal and prebuilts/androidx/external directories in your checkout. All the dependencies in these directories are also available from google(), or mavenCentral(). We store copies of these dependencies to have hermetic builds. You can pull in a new dependency using our importMaven tool.