[Hold for Payment: 2022-12-09] [$2000] 💥 Crash 💥 com.facebook.react.modules.core.ExceptionsManagerModule.reportException
#9818
Comments
|
Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
|
Huh... This is 4 days overdue. Who can take care of this? |
|
Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it! |
|
Looks related to |
marcaaron
added
the
External
|
Triggered auto assignment to @NicMendonca ( |
|
Triggered auto assignment to Contributor-plus team member for initial proposal review - @Santhosh-Sellavel ( |
melvin-bot
bot
added
the
Help Wanted
|
Triggered auto assignment to @pecanoro ( |
melvin-bot
bot
changed the title
com.facebook.react.modules.core.ExceptionsManagerModule.reportExceptioncom.facebook.react.modules.core.ExceptionsManagerModule.reportException
|
Job posting: https://www.upwork.com/jobs/~017a11ea11ddc116ae |
|
i think it's the same crash here #9624 . |
But the idea is users can navigate to any chat easily when we show along with the sidebar.
I like this one
Definitely, this is one of the considerations while selecting the previous consensus. |
This is what we do if you're trying to access something like a workspace settings page you no longer have access to. Here though, if we don't know the route is a settings page we want to load (similar to not knowing if it's a chat), I'm not sure we should be opening this error in the right-hand modal which implies it is a settings page?
I agree the full page doesn't look great as is, but it's going to get a facelift later as @shawnborton alluded to here. |
|
Sounds good. So @pecanoro @Santhosh-Sellavel I think we can hire @aimane-chnaif to do this one then. @aimane-chnaif let us know if there are questions about where this landed. |
melvin-bot
bot
removed
the
Help Wanted
|
📣 @aimane-chnaif You have been assigned to this job by @marcaaron! |
When is this merged? And can you link to that PR if possible? |
Need to confirm final design of full not found page with @shawnborton |
|
It's happening in the future sometime. As @trjExpensify said
so I think we can go with your original proposal and improve it later. |
Can we just reuse what we currently have? |
|
@marcaaron Thank you for helping us reach a consensus!! |
|
PR in review! |
|
There we go! Lots of action in the PR too, thank you all. |
mountiny
added
the
Awaiting Payment
mountiny
changed the title
com.facebook.react.modules.core.ExceptionsManagerModule.reportExceptioncom.facebook.react.modules.core.ExceptionsManagerModule.reportException
|
@CortneyOfstad This is ready to be paid out, the automation was broken for that deploy |
|
@CortneyOfstad Please let me know if you're not able to get to this today! It's super important we pay our contributors on time. |
|
Question regarding PR timeline bonus/penalty rule: |
|
Looking at the PR it seems the PR started on Wednesday before thanksgiving and was finished the next wednesday so given the holidays I would say the bonus should still apply. cc @CortneyOfstad |
|
@JmillsExpensify Definitely can pay today 👍 So to clarify: @parasharrajat gets the reporting bonus, which is $250 This is my first GH where it was $250 across the board, so I just wanted to confirm this before sending out any contracts in Upwork and making the payments. Thanks |
|
@aimane-chnaif and I should get $2000 for the job + 50% bonus ($1000) i.e $3000 each! |
|
@Santhosh-Sellavel! Thank you!! I'll get those contracts sent out shortly! |
|
Alright, contracts have been sent over @parasharrajat, @aimane-chnaif and @Santhosh-Sellavel! I'll keep an eye on my email and get them paid by EOD. Heading to the airport now but will be working to keep an eye on this. Thanks! |
|
Alright, all three contracts were accepted and paid! Thank you! 👍 |
|
Perfect, thanks everyone closing! |
and others
Fatal Exception: com.facebook.react.common.JavascriptException
Error: Failed to parse the path to a navigation state., js engine: hermes, stack:
linkTo@1:1568442
navigate@1:1567607
onPress@1:3397674
_performTransitionSideEffects@1:319784
_receiveSignal@1:319351
onResponderRelease@1:318549
onResponderRelease@1:307174
invokeGuardedCallbackImpl@1:137261
invokeGuardedCallback@1:137318
invokeGuardedCallbackAndCatchFirstError@1:137350
executeDispatch@1:137482
executeDispatchesAndReleaseTopLevel@1:140878
forEachAccumulated@1:138979
anonymous@1:141235
batchedUpdatesImpl@1:197499
batchedUpdates@1:140795
_receiveRootNodeIDEvent@1:141072
receiveTouches@1:191785
__callFunction@1:124518
anonymous@1:123005
__guard@1:123963
callFunctionReturnFlushedQueue@1:122963
ExceptionsManagerModule.java line 83com.facebook.react.modules.core.ExceptionsManagerModule.reportExceptionNumber of Crashes: 113
Device Information
1.1.78.8,1.1.79.17,1.1.79-17,1.1.82.1,1.1.82.5,1.1.82-5,1.1.84-11,1.1.84.13,1.1.84-13,1.1.85.5,1.1.85-8,1.1.86.5,1.1.86-5,1.1.88-14,1.1.88.14,1.1.89.0,1.1.92.0,1.1.95.4,1.1.96-5,1.1.99.2,1.2.1-0,1.2.5-0,1.2.7.2,1.2.11-4,1.2.21-4,1.2.23.9,1.2.25.0Stacktraces
iOS 1.2.23.9
iOS 1.2.25.0
iOS 1.2.25.0
iOS 1.2.25.0
Android 1.2.21-4
Android 1.2.11-4
iOS 1.2.7.2
Android 1.2.5-0
Android 1.2.1-0
iOS 1.1.99.2
Android 1.1.96-5
iOS 1.1.95.4
iOS 1.1.92.0
iOS 1.1.89.0
iOS 1.1.88.14
Android 1.1.88-14
Android 1.1.86-5
iOS 1.1.86.5
Android 1.1.85-8
iOS 1.1.84.13
iOS 1.1.85.5
Android 1.1.84-13
Android 1.1.84-11
iOS 1.1.78.8
iOS 1.1.82.1
Android 1.1.79-17
iOS 1.1.79.17
iOS 1.1.82.5
Android 1.1.82-5
Android 1.1.82-5
Internal Firebase Info
💥 DO NOT EDIT THIS SECTION 💥
Crash IDs:
42faadc879a4494cb952f0fc44634ad1,fd1cdb4e916b7497e85f0e22ad937c6e,29f5a4afa1f0968901244363906bf119,0c9127e6df526e091a2c1234b473af9b,2b58bfd50d223d37654eb072cb29246c,ef923b3799ff010cbdc5ea71e380a1f8,04e8695e7a6419f0959b5e4107783f2f,1b48dc76294680660c922cd38060fbb0,7aaab775a7cdfbcdd533762bfad8b915,c7030192ceff57dbfe08d05d05eb7fd2,3e22a13cae76308bc81d059fd80893c0,0d67e736a80041771095dbd76dd8b5bb,33adb98aaff855bbb94f92a3cce60fd0,cd29426f21ddd2f64d84388f3436bf27,0f2f03923861eed98c8e2b321fb85037,e018a5bac3eb2b3e68cb20a3db5f537d,3ab6bc1fed57f700ca3d6f4b6930a1d4,b2768cf59642e3ca026bc3cfaca970f2,07a967c45003cb2126335f96423aef85,08a15e7ffa759f74d6b4092a08f6e99c,d7e63917c9532f80ff7fac98d179d56e,b626f66df9f73c9cbd88adb0d352aea1,cce5771a8473530f3055066a928f83cc,fd7bf8cf7da7c84339631b0a8a43ca85,6933177f2b618c717a66b61dbc9cf254,28d21439a942afea21e6aa0790285ea0,1d275a834d1c4edccdd99279ff4d4506,096cacca5f299bff98f13377d44aa414,dbcbeed63118ccee61e53bdea73a84a6,f52ddfb8306449bd3b645e8fe47460aaException:
Error: Failed to parse the path to a navigation state., js engine: hermes, stack: linkTo@1:1568442 navigate@1:1567607 onPress@1:3397674 _performTransitionSideEffects@1:319784 _receiveSignal@1:319351 onResponderRelease@1:318549 onResponderRelease@1:307174 invokeGuardedCallbackImpl@1:137261 invokeGuardedCallback@1:137318 invokeGuardedCallbackAndCatchFirstError@1:137350 executeDispatch@1:137482 executeDispatchesAndReleaseTopLevel@1:140878 forEachAccumulated@1:138979 anonymous@1:141235 batchedUpdatesImpl@1:197499 batchedUpdates@1:140795 _receiveRootNodeIDEvent@1:141072 receiveTouches@1:191785 __callFunction@1:124518 anonymous@1:123005 __guard@1:123963 callFunctionReturnFlushedQueue@1:122963The text was updated successfully, but these errors were encountered: