Fixed
Status Update
Comments
ja...@google.com <ja...@google.com>
je...@google.com <je...@google.com>
sp...@google.com <sp...@google.com> #2
A couple of questions:
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
tn...@google.com <tn...@google.com> #3
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
tn...@google.com <tn...@google.com>
sa...@google.com <sa...@google.com> #4
-
Second crash in the description is from a real device. Experienced it myself on two different Xiaomi phones, plus lots of crashes from users in the Google Play console.
-
Dynamic features are not used in the application.
As a wild guess, I have downgraded build tools from 31.0.0 to 30.0.3, compileSdk from 31 to 30, and moved all work with Language ID to the service in a separate process (just to be sure that crash can kill secondary process instead of main). This combination is in beta for 2 days by now and I don't see any SIGSEGV crashes.
Description
After enabling lint on
test
sources, theNewApi
lint check will be triggered in robolectric tests even if the test is configured with aminSdk
lower than the API being used. To work around this issues, users are required to add a redundant@RequiresApi()
or@TargetApi()
annotation to their test method or test class.STEPS TO REPRODUCE:
test
sources insidebuild.gradle
:src/test/...
@Config(minSdk = <minsdk>)
(orrobolectric.properties
android.defaultConfig.minSdkVersion
is lower thanminsdk
so it doesn't get suppressed that way.sdk
<=minsdk
(I usedandroid.util.Size
which was added in API 21 and setminsdk
to 23, for example). Alternatively, annotate a method or class with@RequiresApi(<sdk>)
and use it in a test../gradlew app:lint
and seeNewApi
failures.Example:
Studio Build:
Version of Gradle Plugin:
7.1.0-alpha03