-
Notifications
You must be signed in to change notification settings - Fork 160
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
Fix crash in the room list after a forced log out in background #3180
Conversation
📱 Scan the QR code below to install the build (arm64 only) for this PR. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #3180 +/- ##
========================================
Coverage 76.15% 76.15%
========================================
Files 1645 1645
Lines 38738 38738
Branches 7496 7496
========================================
Hits 29501 29501
Misses 5343 5343
Partials 3894 3894 ☔ View full report in Codecov by Sentry. |
return try { | ||
room(roomId) | ||
} catch (exception: RoomListException) { | ||
Timber.d(exception, "Failed finding room with id=$roomId.") | ||
return null | ||
} catch (exception: IllegalStateException) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we just catch any exception then?
089320d
to
115f51b
Compare
115f51b
to
865de02
Compare
Quality Gate passedIssues Measures |
Content
Take into account
IllegalStateException
too when trying to retrieve a room fromRoomListService
.Motivation and context
Fixes #3173, although it doesn't fix the logout that caused the crash.
Tests
I don't see an easy way to test this.
Tested devices
Checklist