-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Crash in DetoxSync #2641
Comments
I don't think the number of workers matters here. |
Might be similar to #2627 (which was closed in error as duplicate of another issue). |
Maybe it doesn't but when I run the tests without |
Detox 18 has a new synchronization mechanism, built in-house. |
Yes, but it is quite nice. Thats why I want to upgrade, so now I am also digging around trying to find the cause. |
@denissb Please comment if you find the same crash when upgrading to the latest v18. When I last tried it happened on 18.3 |
@alon-ha any leads to help out? |
@sam-barker I still have the same issue on 18.6.0 |
Any movement on this at all? |
Hi, Environment:
Logs:
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions! For more information on bots in this reporsitory, read this discussion. |
All, we are currently on a break and a bit short-staffed at the moment, in general. We hope to get on top of this within 1-2 weeks. Here are similar discussions that could be relevant, in the meantime: |
Hello, any updates on this? We are sorely in need of a Firebase upgrade (the old version of Firebase is actually causing bugs in our app) but we can't bump Firebase until this gets resolved. |
Hi, any advice on this, the app is having this issue when trying to add firebase and segment to the project |
@alon-ha, pinging you just for visibility. Personally, I think this is an important issue since many RN users are using Firebase including our teams as well if I am not mistaken. Let's check if we already have clear instructions on how to reproduce the crash. @wdospinal, @shamilovtim could you help to locate any demo project crashing with that error or create one? I think Alon will get back to his job duties starting from the next week, and I hope he'll find time during April-May to check out a demo project if it will be already prepared. |
From what I could tell based on shallow research the issue might be caused by monkey patching in HTTP libraries. That's supposedly how it appeared in KTOR: firebase/firebase-ios-sdk#7277 I've seen other tickets in the ecosystem also blaming the same thing in various ways |
Also related: JetBrains/kotlin-native#4569 (blame was again monkey patching) |
@shamilovtim, what but isn't that Android-related there? At the moment, we are discussing iOS. |
This workaround solves the issue described here: firebase/firebase-ios-sdk#9083 And some of the crashes that was mentioned here: - wix#3000 - wix#3123 - wix#2641 - wix#2802
This workaround solves the issue described here: firebase/firebase-ios-sdk#9083 And some of the crashes that was mentioned here: - #3000 - #3123 - #2641 - #2802
#3135 was merged, it should solve the issue of DetoxSync crashes when Firebase/Performance is integrated, it was tested on the example apps that reproduced this issue. Once you have updated a version (to the latest/next version), if any of you are still having Signal 11 crashes on DetoxSync when Firebase/Performance is integrated, please open a new bug report with the required details. As for the parallel @param-finder I will investigate soon the crashes with Expo. |
Sorry to be the bearer of bad news, but we're still seeing Signal 11's with Detox 19.4.1:
It looks similar to the original trace on this issue, but happy to open a new one if you'd prefer @asafkorem ? |
Hi @ball-hayden, thanks for the report. Are you running parallel tests? |
We're running with |
we also still have the |
I've also got interesting behaviour (no parallel workers used):
There is Signal 11 error. But all my tests are running successfully after it. RN: 0.66.2 Firebase packages: @react-native-firebase/analytics: 12.0.0 |
After updating all the above |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions! For more information on bots in this reporsitory, read this discussion. |
We're still seeing Signal 11s intermittently. (I appreciate this isn't massively helpful - I'll keep trying to narrow it down) |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions! For more information on bots in this reporsitory, read this discussion. |
Still seeing this. |
@ball-hayden would appreciate more info indeed. Thank you. |
Can we move to this thread? #3207 |
Yeah - @d4vidi there's some more information in #3207. Both myself and @shamilovtim are struggling to isolate what causes this, so I appreciate there isn't a huge amount that can be done at the moment. It is still an issue, however, so IMHO shouldn't be marked as stale. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions! For more information on bots in this reporsitory, read this discussion. |
Closing in favor of #3207 |
I have an issue when running tests in parallel with
--workers 2
usingjest-circus
after upgrading to detox 18The form tests that use the keyboard actions like
typeText
andclearText
fail when they are running in parallel with another test.Reproduction
--workers 2
usingjest-circus
as a runnerI also get this error thrown in one of the tests when running in parallel
Expected behaviour
The tests should pass just like when you run them with
--maxWorkers 1
Environment (please complete the following information):
Detox: 18.3.1
React Native: 0.63.4
Node: 14.15.4
Device: iPhone 8
Xcode: 12.3
iOS: 14.4
macOS: 10.15.7
I have followed the instructions under Identifying which synchronization mechanism causes us to wait too much, I have read synchronization debug documentation and am providing the relevant synchronization debug output below:
The text was updated successfully, but these errors were encountered: