-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Investigate ReactNativeManager.getFragmentManager crash #58549
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
Comments
Triggered auto assignment to @mallenexpensify ( |
Hi! This issue occurred only once. Can we assign LOW priority to this issue and keep monitoring it? |
@mallenexpensify, @mateuuszzzzz Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@mallenexpensify, @mateuuszzzzz Still overdue 6 days?! Let's take care of this! |
LOW, will address before too long |
Checked Crashlytics, I wasn't able to find more crashes like that one |
Triggered auto assignment to @trjExpensify ( |
@trjExpensify I'm going to be OOO and offline for two weeks so I'm reassigning, will pick back up upon my return, thx |
@trjExpensify @mallenexpensify @mateuuszzzzz this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
@mateuuszzzzz shall we just close this one then if we had one crash 2 weeks ago? |
@trjExpensify I think we can close it |
Dope! |
Investigate
Attempt to invoke virtual method 'androidx.fragment.app.FragmentManager androidx.fragment.app.FragmentActivity.getSupportFragmentManager()' on a null object reference
crashFirebase here https://console.firebase.google.com/u/0/project/expensify-mobile-app/crashlytics/app/android:org.me.mobiexpensifyg/issues/e3dd311953becad1266a8956631735a1?time=last-seven-days&types=crash&versions=9.1.13.5%20(509011305);9.1.13.4%20(509011304);9.1.13.0%20(509011300)&sessionEventKey=67D6FD1800C90001390C9E09D56F2561_2060893522571821942
The text was updated successfully, but these errors were encountered: