-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
samples:hello-workflow-fragment:connectedDebugAndroidTest
fails consistently on API 21
#582
Comments
So it was broken by #567 |
Step one, blindly updating dependencies and hoping for the best. In particular, we're on |
Nothing is simple. That jump requires targetSdk 31, which requires android:export=true on the activity, which leads to errors on the merge manifest:
which allegedly should have been fixed by LeakCanary 2.7, which we're on, and so maybe come from some other dependency's manifest, but I don't see anything amiss in |
Disabling LeakCanary fixes it. So how did the original PR ever go green? Or any PR since then? Maybe the AVDs have been updated? I dunno. Going to see if I can disable LC just for this particular test, and maybe hit up @pyricau for a debugging session. |
Or more likely, b/c LeakCanary exposes an obscure bug in Jetpack and life is just too short. Fixes #582.
Duplicates #568, or really emphasizes it. We're not just flaky any more. |
It was choking on API 21 w/the old Leakcanary test rules, and we've stopped using those. Fixes #582
It was choking on API 21 w/the old Leakcanary test rules, and we've stopped using those. Fixes #582
I'm seeing
samples:hello-workflow-fragment:connectedDebugAndroidTest
fail consistently on API 21 onmain
as well. Digging into that.In the meantime, we should consider this PR green.
Originally posted by @rjrjr in #577 (comment)
The text was updated successfully, but these errors were encountered: