java.lang.RuntimeException: Error receiving broadcast Intent { act=android.net.conn.CONNECTIVITY_CHANGE flg=0x4000010 (has extras) } in zl$a@5eda151 [133313734]

Fixed

Bug

Status Update

No update yet.

Description

ni...@gmail.com

created issue #1

May 23, 2019 07:24AM

WorkManager 2.1.0-alpha01
I know 2.1.0-alpha02 is out but I cannot test it as I CANNOT reproduce this issue on both alpha01 and 02.

Proguard mappings
------------------
androidx.work.impl.constraints.trackers.NetworkStateTracker -> zl
androidx.work.impl.constraints.trackers.ConstraintTracker -> yl
androidx.work.impl.constraints.controllers.ConstraintController -> pl
androidx.work.impl.constraints.WorkConstraintsTracker -> ml
androidx.work.impl.background.systemalarm.WorkTimer -> gl

Crash report from user
-----------------
APP_VERSION_NAME=228 armeabi-v7a
ANDROID_VERSION=5.0
BRAND=samsung
PHONE_MODEL=SM-N9005
PRODUCT=hltexx
USER_APP_START_DATE=2019-05-22T09:58:13.756+01:00
USER_CRASH_DATE=2019-05-22T19:21:59.888+01:00
STACK_TRACE=java.lang.RuntimeException: Error receiving broadcast Intent { act=android.net.conn.CONNECTIVITY_CHANGE flg=0x4000010 (has extras) } in zl$a@5eda151
at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:933)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:145)
at android.app.ActivityThread.main(ActivityThread.java:5938)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1400)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1195)
Caused by: java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@220005dc rejected from java.util.concurrent.ScheduledThreadPoolExecutor@ffebca8[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0]
at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2011)
at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:793)
at java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:298)
at java.util.concurrent.ScheduledThreadPoolExecutor.schedule(ScheduledThreadPoolExecutor.java:503)
at java.util.concurrent.Executors$DelegatedScheduledExecutorService.schedule(Executors.java:644)
at gl.a(SourceFile:7)
at dl.b(SourceFile:5)
at ml.a(SourceFile:21)
at pl.b(SourceFile:3)
at pl.a(SourceFile:18)
at yl.a(SourceFile:17)
at zl$a.onReceive(SourceFile:4)
at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:923)
... 8 more

LOGCAT=--------- beginning of main
05-22 19:21:59.727 D/AndroidRuntime(11913): Shutting down VM
05-22 19:21:59.757 E/ACRA (11913): ACRA caught a RuntimeException for com.nll.asr
05-22 19:21:59.757 E/ACRA (11913): java.lang.RuntimeException: Error receiving broadcast Intent { act=android.net.conn.CONNECTIVITY_CHANGE flg=0x4000010 (has extras) } in zl$a@5eda151
05-22 19:21:59.757 E/ACRA (11913): at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:933)
05-22 19:21:59.757 E/ACRA (11913): at android.os.Handler.handleCallback(Handler.java:739)
05-22 19:21:59.757 E/ACRA (11913): at android.os.Handler.dispatchMessage(Handler.java:95)
05-22 19:21:59.757 E/ACRA (11913): at android.os.Looper.loop(Looper.java:145)
05-22 19:21:59.757 E/ACRA (11913): at android.app.ActivityThread.main(ActivityThread.java:5938)
05-22 19:21:59.757 E/ACRA (11913): at java.lang.reflect.Method.invoke(Native Method)
05-22 19:21:59.757 E/ACRA (11913): at java.lang.reflect.Method.invoke(Method.java:372)
05-22 19:21:59.757 E/ACRA (11913): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1400)
05-22 19:21:59.757 E/ACRA (11913): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1195)
05-22 19:21:59.757 E/ACRA (11913): Caused by: java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@220005dc rejected from java.util.concurrent.ScheduledThreadPoolExecutor@ffebca8[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0]
05-22 19:21:59.757 E/ACRA (11913): at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2011)
05-22 19:21:59.757 E/ACRA (11913): at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:793)
05-22 19:21:59.757 E/ACRA (11913): at java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:298)
05-22 19:21:59.757 E/ACRA (11913): at java.util.concurrent.ScheduledThreadPoolExecutor.schedule(ScheduledThreadPoolExecutor.java:503)
05-22 19:21:59.757 E/ACRA (11913): at java.util.concurrent.Executors$DelegatedScheduledExecutorService.schedule(Executors.java:644)
05-22 19:21:59.757 E/ACRA (11913): at gl.a(SourceFile:7)
05-22 19:21:59.757 E/ACRA (11913): at dl.b(SourceFile:5)
05-22 19:21:59.757 E/ACRA (11913): at ml.a(SourceFile:21)
05-22 19:21:59.757 E/ACRA (11913): at pl.b(SourceFile:3)
05-22 19:21:59.757 E/ACRA (11913): at pl.a(SourceFile:18)
05-22 19:21:59.757 E/ACRA (11913): at yl.a(SourceFile:17)
05-22 19:21:59.757 E/ACRA (11913): at zl$a.onReceive(SourceFile:4)
05-22 19:21:59.757 E/ACRA (11913): at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:923)
05-22 19:21:59.757 E/ACRA (11913): ... 8 more

REPORT_ID=a476ba1d-9c82-4b7a-90cd-5d91e77df69d
IS_SILENT=false

Comments

li...@gmail.com <li...@gmail.com> #2May 23, 2019 10:50AM

We are not able to reproduce this issue on Nexus 6P, NPF26F build with plaid app version=0.9.9

Can you provide the below requested information to better understand the issue:

Android build
Which Android build are you using? (e.g. KVT49L)

Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)

Also please mention the Plaid app version.

ra...@google.com <ra...@google.com> #3May 23, 2019 05:06PM

I'm also using Nexus 6P with NPF26F and plaid 0.9.9 installed from the play store.

It happens 100% of the time but the RecyclerView has to be positioned in such a way that the animation would make the bottom comment drop off the bottom of the screen. Then click an item quickly several times without letting the expand animation complete and it will crash after several clicks.

ra...@google.com <ra...@google.com> #4May 23, 2019 05:17PM

Thanks for the detailed inputs.
We have passed this defect on to the development team and will update this issue with more information as it becomes available.

ni...@gmail.com <ni...@gmail.com> #5May 23, 2019 05:17PM

I'm getting the same crash when using TransitionManager to animate the RecyclerView's bounds (changing the constraintSet with ConstraintLayout) if the user is interacting with the list. The problem doesn't occur if the user is not interacting with the list during the transition.

ra...@google.com <ra...@google.com> #6May 23, 2019 05:20PM

[Comment deleted]

ni...@gmail.com <ni...@gmail.com> #7May 23, 2019 05:31PM

[Comment deleted]

su...@google.com <su...@google.com> #8May 23, 2019 05:51PM

[Comment deleted]

ni...@gmail.com <ni...@gmail.com> #9May 23, 2019 05:57PM

[Comment deleted]

su...@google.com <su...@google.com> #10May 23, 2019 07:17PM

I got a similar issue will expanding/collapsing items in a recyclerView. I posted earlier but I removed my post when I thought it was fixed and related to something else than the TransitionManager.
But I got the crash again so I investigated further.
The Issue is happening when you are not specifying a transition to the TransitionManager and that you let Android defining it for you, like :

TransitionManager.beginDelayedTransition(hiddenSection);

If you specify an animation it should solve your issue. Try something like that :

chevron.setOnClickListener(v -> {
ChangeBounds changeBounds = new ChangeBounds();
changeBounds.setDuration(hiddenSection.getMeasuredHeight());
TransitionManager.beginDelayedTransition(hiddenSection, changeBounds);
chevron.setRotation(hiddenSection.getVisibility() == View.GONE ? 0 : 180);
hiddenSection.setVisibility(hiddenSection.getVisibility() == View.GONE ? View.VISIBLE : View.GONE);
});

Hope it help :)

Also don't notify the adapter that the item changed. Otherwise the items might overlaps each others.

ni...@gmail.com <ni...@gmail.com> #11May 23, 2019 08:03PM

Any update on this? I'm having the same problem. It's not happening all the time but I can confirm:

- It's just happening when the transition it's not passed as an argument.
-- TransitionManager.beginDelayedTransition(mRecyclerView); <------ This crashes
-- TransitionManager.beginDelayedTransition(mRecyclerView, new ChangeBounds()); <------ This does not crash

- It's happening when the RecyclerView VH that is gonna perform the animation is taller than the screen itself.

ra...@google.com <ra...@google.com> #12May 23, 2019 08:21PM

At the moment I'm not sure about my last point (...taller than the screen...).

ni...@gmail.com <ni...@gmail.com> #13May 23, 2019 08:33PM

As well:

- new TransitionSet().addTransition(new Fade()).addTransition(new ChangeBounds())); <-------- This crashes
- new TransitionSet().addTransition(new ChangeBounds())); <-------- This doesn't crash

ni...@gmail.com <ni...@gmail.com> #14May 23, 2019 08:33PM

Okay, I have something.

Looks like DiffTool is on my way. RecyclerView DiffTool is doing what I was trying to achieve with TransitionManager.beginDelayedTransition(hiddenSection), so when I removed that line the random crash disappeared. I added DiffUtil afterwards so I didn't realize that DiffTool was performing such animations.

ra...@google.com <ra...@google.com> #15May 23, 2019 08:36PM

Hey Googlers, I know how to fix it.

I already found this issue and fixed it in my transitions backport

https://github.com/andkulikov/Transitions-Everywhere
The issue is Visibility transition has to detach an animating view from an overlay in onPause as the transition could be canceled at this moment and the view could be reused somewhere else(recyclerview)

The Commit with the fix:

https://github.com/andkulikov/Transitions-Everywhere/commit/0d977dd7dddee12bdb02f78b1d4c10d649190b26

Also I believe it should be fixed in framework's transitions.

Everyone from this topic who wants to use fixed version of transitions can use

https://github.com/andkulikov/Transitions-Everywhere for now

ra...@google.com <ra...@google.com> #16May 23, 2019 10:40PM

More details about this issue and how to fix it in Transitions framework -

https://issuetracker.google.com/issues/67856407

li...@gmail.com <li...@gmail.com> #17May 24, 2019 06:13AM

Fixed in both androidx transitions and recyclerview and will be released as
androidx.transition:transition:1.1.0-alpha1
androidx.recyclerview:recyclerview:1.1.0-alpha01

ra...@google.com <ra...@google.com> #18May 24, 2019 03:32PM

The fix is not perfect. If I am scrolling, and the transition happens, I loose the touch, need to lift the finger and put again on the screen.

On my apps, I usually do:

TransitionManager.beginDelayedTransition(parentLayout, transition)
filterRecycler.isVisible = !filterRecycler.isVisible
filterItem.isEnabled = false

defaultRecycler.setOnTouchListener { _, _ -> true }

launch(Dispatchers.Main) {
delay(transitionDelay + 50)
filterItem.isEnabled = true
defaultRecycler.setOnTouchListener { _, _ -> false }
}

Video sample of the bug:

https://photos.app.goo.gl/WCSCangdyVeHbVoe9

li...@gmail.com <li...@gmail.com> #19May 25, 2019 12:20AM

#16: Yes, we are using WorkManager 2.1.0-alpha01

ra...@google.com <ra...@google.com> #20May 29, 2019 04:49AM

Marked as fixed, reassigned to ra...@google.com.

Fixed by

https://android-review.googlesource.com/c/platform/frameworks/support/+/971650

Issue 133313734

Description

Issue summary

Comments

li...@gmail.com <li...@gmail.com> #2May 23, 2019 10:50AM

ra...@google.com <ra...@google.com> #3May 23, 2019 05:06PM

ra...@google.com <ra...@google.com> #4May 23, 2019 05:17PM

ni...@gmail.com <ni...@gmail.com> #5May 23, 2019 05:17PM

ra...@google.com <ra...@google.com> #6May 23, 2019 05:20PM

ni...@gmail.com <ni...@gmail.com> #7May 23, 2019 05:31PM

su...@google.com <su...@google.com> #8May 23, 2019 05:51PM

ni...@gmail.com <ni...@gmail.com> #9May 23, 2019 05:57PM

su...@google.com <su...@google.com> #10May 23, 2019 07:17PM

ni...@gmail.com <ni...@gmail.com> #11May 23, 2019 08:03PM

ra...@google.com <ra...@google.com> #12May 23, 2019 08:21PM

ni...@gmail.com <ni...@gmail.com> #13May 23, 2019 08:33PM

ni...@gmail.com <ni...@gmail.com> #14May 23, 2019 08:33PM

ra...@google.com <ra...@google.com> #15May 23, 2019 08:36PM

ra...@google.com <ra...@google.com> #16May 23, 2019 10:40PM

li...@gmail.com <li...@gmail.com> #17May 24, 2019 06:13AM

ra...@google.com <ra...@google.com> #18May 24, 2019 03:32PM

li...@gmail.com <li...@gmail.com> #19May 25, 2019 12:20AM

ra...@google.com <ra...@google.com> #20May 29, 2019 04:49AM

Add comment

Issue metadata