-
Notifications
You must be signed in to change notification settings - Fork 24.3k
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
Android HeadlessJS Crash - Tried to finish non-existent task with id #27597
Comments
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions. |
Still happening.
El lun., 23 de marzo de 2020 01:24, stale[bot] <notifications@github.com>
escribió:
… Hey there, it looks like there has been no activity on this issue
recently. Has the issue been fixed, or does it still require the
community's attention? This issue may be closed if no further activity
occurs. You may also label this issue as a "Discussion" or add it to the
"Backlog" and I will leave it open. Thank you for your contributions.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#27597 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALU263BOQMWEMBTXV7VKRCLRI3P67ANCNFSM4J6ZJ5CQ>
.
|
We are also seeing this issue affect our App: 0.61.5 across a range of Android versions. We haven't yet investigated it fully but I wonder if it might be related to the power settings on Android devices and some of the issues which are detailed here: https://dontkillmyapp.com/ Or as you say @cristianoccazinsp a race condition that is very hard to reproduce. |
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions. |
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information. |
Just received a random Android crash from the crash reporting tool. I haven't been able to reproduce it, but the headless task runs every 60 minutes and is intended to finish before the 30s timeout it is given. The crash happened from a headless task that didn't run with the app previously initialized (with an UI / main activity). Crash
After tracing the error, I ended up here: https://github.com/facebook/react-native/blob/0.61-stable/ReactAndroid/src/main/java/com/facebook/react/jstasks/HeadlessJsTaskContext.java#L202 , here https://github.com/facebook/react-native/blob/0.61-stable/ReactAndroid/src/main/java/com/facebook/react/jstasks/HeadlessJsTaskContext.java#L111 and here https://github.com/facebook/react-native/blob/0.61-stable/ReactAndroid/src/main/java/com/facebook/react/jstasks/HeadlessJsTaskContext.java#L165
From the above I can't really tell if the task timed out and it failed to be notified, or if it finished on time, but the timeout also fired (a race condition between the is running check and the actual finish call?) causing the crash. For me this assertion seems a bit to aggressive, and it should be just a warning rather than an app crash.
React Native version:
Steps To Reproduce
The text was updated successfully, but these errors were encountered: