Status Update
Comments
he...@gmail.com <he...@gmail.com> #2
Room uses
I don't have a M1 machine to try this out but my guess is they simply don't have yet a compiled SQLite native lib for the aarch64.
ve...@google.com <ve...@google.com> #3
By the way, I imagine you can workaround this using a JDK x86/x64 version + Rosetta that would make the JNI layer load the right native library.
he...@gmail.com <he...@gmail.com> #4
Yes, Apple Silicon is supported by this pull request
Hope to be supported in the next version of Room. Thanks!
he...@gmail.com <he...@gmail.com> #5
workaround for now
def room_version = "2.3.0-alpha03"
implementation("androidx.room:room-runtime:$room_version") {
exclude(group:'org.xerial')
}
kapt("androidx.room:room-compiler:$room_version"){
exclude(group:'org.xerial')
}
implementation("androidx.room:room-ktx:$room_version"){
exclude(group:'org.xerial')
}
implementation 'org.xerial:sqlite-jdbc:3.34.0'
he...@gmail.com <he...@gmail.com> #6
Branch: androidx-main
commit abddddd5b5040e47ae1c28153343fef168036341
Author: Daniel Santiago Rivera <danysantiago@google.com>
Date: Tue Dec 15 09:16:21 2020
Update xerial sqlite-jdbc library.
Updating to 3.34.0 that support Apple's M1 chip arch 'aarch64'.
Bug: 174695268
Test: n/a - I don't have an M1 Mac...
Relnote: Update Room dependencies to support Apple's M1 CPUs.
Change-Id: Ieb6dd72b5443d7ec555a0720bff84bc413fc144c
M buildSrc/src/main/kotlin/androidx/build/dependencies/Dependencies.kt
he...@gmail.com <he...@gmail.com> #7
he...@gmail.com <he...@gmail.com> #8
Not yet sorry, we ran into an issue with the JDBC library (
he...@gmail.com <he...@gmail.com> #9
For those who are facing this problem, you can simply add this line before the room-compiler
as a workaround now:
+kapt("org.xerial:sqlite-jdbc:3.34.0")
kapt("androidx.room:room-compiler:2.3.0-beta01")
he...@gmail.com <he...@gmail.com> #10
If the mentioned workarounds are not working, I recommend using this workaround instead, adding it to the root build.gradle. This will force using the given dependency in the whole project:
allprojects {
configurations.all {
resolutionStrategy {
force 'org.xerial:sqlite-jdbc:3.34.0'
}
}
}
vi...@google.com <vi...@google.com> #11
You should use configureEach instead of all, FYI!
vi...@google.com <vi...@google.com> #12
he...@gmail.com <he...@gmail.com> #13
Just a note for others - fixed *in room 2.4.0-alpha03
ve...@google.com <ve...@google.com>
he...@gmail.com <he...@gmail.com> #14
we need a patch version for 2.3.x
Description
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
What type of Android issue is this? User Interface, Display, or Rendering issue
When did this happen?
Dec 11, 2021 04:00 GMT+01:00
What steps would let us observe this issue?
1. Have a few notifications as bundles. (Pretty sure normal notifications won't trigger this bug)
2. Receive a few live new notifications and reply to 1 of them.
3. Expand one of the other notifications (not the one where you replied to).
4. Pull down from the top.
5. Basically do what I did in the sample video.
What did you expect to happen?
I expected a smooth pull down animation.
What actually happened?
The area from where I pulled down became blank and the notification that I pulled down was underneath that blank area.
How often has this happened?
Frequently
What was the effect of this issue on your device usage, such as lost time or work?
Slight
Debugging information
Google Play services
com.google.android.gms
Version 214218053 (21.42.18 (190400-410302452))
System App (Updated)
Android System WebView
com.google.android.webview
Version 466409233 (96.0.4664.92)
System App (Updated)
Network operator:
SIM operator: Vodafone
Filed by Android Beta Feedback. Version (Updated): 2.22-betterbug.external_20211027_RC01
To learn more about our feedback process, please visit