This repository has been archived by the owner on Jun 20, 2023. It is now read-only.
Prevent IllegalStateException when orphaned Fragments try to popBackStack() (EXPOSUREAPP-4430) #1987
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prevent IllegalStateException if a fragment that's not added to an Activity tries to popBackStack().
We've got a few stacktraces where the app crashes with this stacktrace (see below).
It looks like the Fragment is not added to an Activity and then we call
popBackStack
which throws due not not being able to find a fragment manager.While I can't reproduce it, I think what happens is:
popBackStack
on that leading to the crash.As this may be a more common error to encounter, I've added the fix (guard clause) to the extension function. "If a fragment is not added to an activity, don't
popBackStack()
.Originates from here:
cwa-app-android/Corona-Warn-App/src/main/java/de/rki/coronawarnapp/ui/submission/testresult/pending/SubmissionTestResultPendingFragment.kt
Line 136 in 8178542