talk-android/app
Marcel Hibbe ca51bf10b7 replace userManager.currentUser usage by currentUserProvider usage
userManager.currentUser was called too often. I was not able to prove that a bug is related to it but i think it may fix some hidden bugs.

CurrentUserProviderImpl is now used throughout the code to access the current user.
userManager.currentUser is only used from CurrentUserProviderImpl whenever the _currentUser was null (should only happen on app startup)

To avoid multiple initialization of CurrentUserProviderImpl it was changed to be a @Singleton

The handling should soon be replaced with coroutine flows. However for the v21.0.0 release it's still done with RxJava to avoid bugs.

Signed-off-by: Marcel Hibbe <dev@mhibbe.de>
2025-02-07 12:26:20 +00:00
..
schemas/com.nextcloud.talk.data.source.local.TalkDatabase save "silent" in chat messages (incl DB) 2025-01-10 12:32:32 +01:00
src replace userManager.currentUser usage by currentUserProvider usage 2025-02-07 12:26:20 +00:00
build.gradle bump version to 21.0.0 RC1 2025-01-23 14:49:31 +01:00
lint.xml Add SPDX header 2024-03-21 18:39:30 +01:00
proguard-rules.pro Add SPDX header 2024-03-17 14:19:56 +01:00