mirror of
https://github.com/nextcloud/talk-android
synced 2025-07-10 14:24:05 +01:00
Re-use existing ChatController from notification
NotificationWorker provides the user information under KEY_USER_ENTITY parameter of the notification intent, but does not set the KEY_INTERNAL_USER_ID parameter. With this change existing ChatController instance that has been opened manually from the conversation list is properly reused when a notification is opened. Otherwise two instances of the ChatController were running in parallel for the same room, causing unintended side effects. Signed-off-by: Dariusz Olszewski <starypatyk@users.noreply.github.com>
This commit is contained in:
parent
c95d286de4
commit
93556da33a
@ -48,9 +48,9 @@ import com.nextcloud.talk.controllers.SettingsController
|
||||
import com.nextcloud.talk.controllers.WebViewLoginController
|
||||
import com.nextcloud.talk.controllers.base.providers.ActionBarProvider
|
||||
import com.nextcloud.talk.databinding.ActivityMainBinding
|
||||
import com.nextcloud.talk.models.database.UserEntity
|
||||
import com.nextcloud.talk.models.json.conversations.RoomOverall
|
||||
import com.nextcloud.talk.utils.ApiUtils
|
||||
import com.nextcloud.talk.utils.ConductorRemapping
|
||||
import com.nextcloud.talk.utils.ConductorRemapping.remapChatController
|
||||
import com.nextcloud.talk.utils.SecurityUtils
|
||||
import com.nextcloud.talk.utils.bundle.BundleKeys
|
||||
@ -346,8 +346,8 @@ class MainActivity : BaseActivity(), ActionBarProvider {
|
||||
intent.extras?.let { callNotificationIntent.putExtras(it) }
|
||||
startActivity(callNotificationIntent)
|
||||
} else {
|
||||
ConductorRemapping.remapChatController(
|
||||
router!!, intent.getLongExtra(BundleKeys.KEY_INTERNAL_USER_ID, -1),
|
||||
remapChatController(
|
||||
router!!, intent.getParcelableExtra<UserEntity>(KEY_USER_ENTITY)!!.id,
|
||||
intent.getStringExtra(KEY_ROOM_TOKEN)!!, intent.extras!!, false
|
||||
)
|
||||
}
|
||||
|
Loading…
Reference in New Issue
Block a user