Fixed
Status Update
Comments
se...@google.com <se...@google.com>
wk...@google.com <wk...@google.com>
il...@google.com <il...@google.com> #2
Project: platform/frameworks/support
Branch: androidx-main
commit 23f1ec688f947830ccb1b80ea05bcf918a49259c
Author: Daniel Santiago Rivera <danysantiago@google.com>
Date: Thu Aug 08 11:24:53 2024
Support linuxArm64 JNI in sqlite-bundled
Bug: 358045505
Test: Manual, validated natives/linux_arm64/libsqliteJni.so is in jar file.
Change-Id: I4ad58258e6379b621e25bde24d565db47e7186ea
M sqlite/sqlite-bundled/build.gradle
https://android-review.googlesource.com/3213736
Branch: androidx-main
commit 23f1ec688f947830ccb1b80ea05bcf918a49259c
Author: Daniel Santiago Rivera <danysantiago@google.com>
Date: Thu Aug 08 11:24:53 2024
Support linuxArm64 JNI in sqlite-bundled
Bug: 358045505
Test: Manual, validated natives/linux_arm64/libsqliteJni.so is in jar file.
Change-Id: I4ad58258e6379b621e25bde24d565db47e7186ea
M sqlite/sqlite-bundled/build.gradle
th...@gmail.com <th...@gmail.com> #3
It works perfectly! Thanks for the quick response!
wk...@google.com <wk...@google.com> #4
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.sqlite:sqlite-bundled:2.5.0-alpha07
androidx.sqlite:sqlite-bundled-android:2.5.0-alpha07
androidx.sqlite:sqlite-bundled-iosarm64:2.5.0-alpha07
androidx.sqlite:sqlite-bundled-iossimulatorarm64:2.5.0-alpha07
androidx.sqlite:sqlite-bundled-iosx64:2.5.0-alpha07
androidx.sqlite:sqlite-bundled-jvm:2.5.0-alpha07
androidx.sqlite:sqlite-bundled-linuxarm64:2.5.0-alpha07
androidx.sqlite:sqlite-bundled-linuxx64:2.5.0-alpha07
androidx.sqlite:sqlite-bundled-macosarm64:2.5.0-alpha07
androidx.sqlite:sqlite-bundled-macosx64:2.5.0-alpha07
Description
Version used: 1.0.0-alpha-01
Devices/Android versions reproduced on: -
Safe args are a great enhancement for navigation. A great addition to that would be being able to define nullability for arguments. An example for how this would look like:
<argument android:name="id" app:type="string?"/>
(note the ? for the type) - an alternative would be to have another attribute - e.g. app:required="false" to make it less tied to Kotlin. The generated Args and NavDirections class would have the Nullable/NonNull annotations.
This would make it very obvious which arguments are required and which are optional - especially in Kotlin.