Fixed
Status Update
Comments
ku...@google.com <ku...@google.com>
ku...@google.com <ku...@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
nk...@google.com <nk...@google.com>
ma...@gmail.com <ma...@gmail.com> #3
It works perfectly! Thanks for the quick response!
nk...@google.com <nk...@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
nk...@google.com <nk...@google.com> #5
The release is not out yet but marking this as fixed for now.
Description
Version used: "1.0.1"
What steps will reproduce the problem?
Test an `Activity`'s `setResult()` using `ActivityTestRule.getActivityResult()` and Espresso.
If the activity undergoes a configuration change (such as display rotation) during the test, `ActivityTestRule.getActivity()` will still return the previous instance of the activity (the one existing before the configuration change). This will make any subsequent calls to `ActivityTestRule.getActivityResult()` throw `IllegalStateException` with error message: "Activity is not finishing!".
Example code snippet:
@Rule
public ActivityTestRule<MyActivity> rule = new ActivityTestRule<>(MyActivity.class);
@Test
public void myTest() throws Exception {
rule.getActivity().setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_LANDSCAPE);
Espresso.onView(ViewMatchers.withId(R.id.button)).perform(click()); // In MyActivity this button click will trigger setResult() and finish().
Instrumentation.ActivityResult result = activityTestRule.getActivityResult(); // Test will crash here.
}