mirror of
https://github.com/nextcloud/talk-android
synced 2025-06-19 19:49:33 +01:00
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>
178 lines
7.0 KiB
Kotlin
178 lines
7.0 KiB
Kotlin
/*
|
|
* Nextcloud Talk - Android Client
|
|
*
|
|
* SPDX-FileCopyrightText: 2022 Dariusz Olszewski <starypatyk@gmail.com>
|
|
* SPDX-License-Identifier: GPL-3.0-or-later
|
|
*/
|
|
package com.nextcloud.talk.receivers
|
|
|
|
import android.app.Notification
|
|
import android.app.NotificationManager
|
|
import android.content.BroadcastReceiver
|
|
import android.content.Context
|
|
import android.content.Intent
|
|
import android.text.SpannableStringBuilder
|
|
import android.text.style.ForegroundColorSpan
|
|
import android.util.Log
|
|
import androidx.core.app.NotificationCompat
|
|
import androidx.core.app.NotificationManagerCompat
|
|
import androidx.core.app.Person
|
|
import androidx.core.app.RemoteInput
|
|
import autodagger.AutoInjector
|
|
import com.nextcloud.talk.R
|
|
import com.nextcloud.talk.api.NcApi
|
|
import com.nextcloud.talk.application.NextcloudTalkApplication
|
|
import com.nextcloud.talk.data.user.model.User
|
|
import com.nextcloud.talk.models.json.chat.ChatOverallSingleMessage
|
|
import com.nextcloud.talk.users.UserManager
|
|
import com.nextcloud.talk.utils.ApiUtils
|
|
import com.nextcloud.talk.utils.NotificationUtils
|
|
import com.nextcloud.talk.utils.bundle.BundleKeys.KEY_INTERNAL_USER_ID
|
|
import com.nextcloud.talk.utils.bundle.BundleKeys.KEY_ROOM_TOKEN
|
|
import com.nextcloud.talk.utils.bundle.BundleKeys.KEY_SYSTEM_NOTIFICATION_ID
|
|
import com.nextcloud.talk.utils.database.user.CurrentUserProviderNew
|
|
import com.nextcloud.talk.utils.message.SendMessageUtils
|
|
import io.reactivex.Observer
|
|
import io.reactivex.Single
|
|
import io.reactivex.android.schedulers.AndroidSchedulers
|
|
import io.reactivex.disposables.Disposable
|
|
import io.reactivex.schedulers.Schedulers
|
|
import javax.inject.Inject
|
|
|
|
@AutoInjector(NextcloudTalkApplication::class)
|
|
class DirectReplyReceiver : BroadcastReceiver() {
|
|
|
|
@Inject
|
|
lateinit var userManager: UserManager
|
|
|
|
@Inject
|
|
lateinit var currentUserProvider: CurrentUserProviderNew
|
|
|
|
@Inject
|
|
lateinit var ncApi: NcApi
|
|
|
|
lateinit var context: Context
|
|
lateinit var currentUser: User
|
|
private var systemNotificationId: Int? = null
|
|
private var roomToken: String? = null
|
|
private var replyMessage: CharSequence? = null
|
|
|
|
init {
|
|
NextcloudTalkApplication.sharedApplication!!.componentApplication.inject(this)
|
|
}
|
|
|
|
override fun onReceive(receiveContext: Context, intent: Intent?) {
|
|
context = receiveContext
|
|
|
|
// NOTE - systemNotificationId is an internal ID used on the device only.
|
|
// It is NOT the same as the notification ID used in communication with the server.
|
|
systemNotificationId = intent!!.getIntExtra(KEY_SYSTEM_NOTIFICATION_ID, 0)
|
|
roomToken = intent.getStringExtra(KEY_ROOM_TOKEN)
|
|
|
|
val id = intent.getLongExtra(KEY_INTERNAL_USER_ID, currentUserProvider.currentUser.blockingGet().id!!)
|
|
currentUser = userManager.getUserWithId(id).blockingGet()
|
|
|
|
replyMessage = getMessageText(intent)
|
|
sendDirectReply()
|
|
}
|
|
|
|
private fun getMessageText(intent: Intent): CharSequence? =
|
|
RemoteInput.getResultsFromIntent(intent)?.getCharSequence(NotificationUtils.KEY_DIRECT_REPLY)
|
|
|
|
private fun sendDirectReply() {
|
|
val credentials = ApiUtils.getCredentials(currentUser.username, currentUser.token)
|
|
val apiVersion = ApiUtils.getChatApiVersion(currentUser.capabilities!!.spreedCapability!!, intArrayOf(1))
|
|
val url = ApiUtils.getUrlForChat(apiVersion, currentUser.baseUrl!!, roomToken!!)
|
|
|
|
ncApi.sendChatMessage(
|
|
credentials,
|
|
url,
|
|
replyMessage,
|
|
currentUser.displayName,
|
|
null,
|
|
false,
|
|
SendMessageUtils().generateReferenceId()
|
|
)
|
|
?.subscribeOn(Schedulers.io())
|
|
?.observeOn(AndroidSchedulers.mainThread())
|
|
?.subscribe(object : Observer<ChatOverallSingleMessage> {
|
|
override fun onSubscribe(d: Disposable) {
|
|
// unused atm
|
|
}
|
|
|
|
override fun onNext(message: ChatOverallSingleMessage) {
|
|
confirmReplySent()
|
|
}
|
|
|
|
override fun onError(e: Throwable) {
|
|
Log.e(TAG, "Failed to send reply", e)
|
|
informReplyFailed()
|
|
}
|
|
|
|
override fun onComplete() {
|
|
// unused atm
|
|
}
|
|
})
|
|
}
|
|
|
|
private fun confirmReplySent() {
|
|
appendMessageToNotification(replyMessage!!)
|
|
}
|
|
|
|
private fun informReplyFailed() {
|
|
val errorColor = ForegroundColorSpan(context.resources.getColor(R.color.medium_emphasis_text, context.theme))
|
|
val errorMessageHeader = context.resources.getString(R.string.nc_message_failed_to_send)
|
|
val errorMessage = SpannableStringBuilder().append("$errorMessageHeader\n$replyMessage", errorColor, 0)
|
|
appendMessageToNotification(errorMessage)
|
|
}
|
|
|
|
private fun findActiveNotification(notificationId: Int): Notification? {
|
|
val notificationManager = context.getSystemService(Context.NOTIFICATION_SERVICE) as NotificationManager
|
|
return notificationManager.activeNotifications.find { it.id == notificationId }?.notification
|
|
}
|
|
|
|
private fun appendMessageToNotification(reply: CharSequence) {
|
|
// Implementation inspired by the SO question and article below:
|
|
// https://stackoverflow.com/questions/51549456/android-o-notification-for-direct-reply-message
|
|
// https://medium.com/@sidorovroman3/android-how-to-use-messagingstyle-for-notifications-without-caching-messages-c414ef2b816c
|
|
//
|
|
// Tries to follow "Best practices for messaging apps" described here:
|
|
// https://developer.android.com/training/notify-user/build-notification#messaging-best-practices
|
|
|
|
// Find the original (active) notification
|
|
val previousNotification = findActiveNotification(systemNotificationId!!) ?: return
|
|
|
|
// Recreate builder based on the active notification
|
|
val previousBuilder = NotificationCompat.Builder(context, previousNotification)
|
|
|
|
// Extract MessagingStyle from the active notification
|
|
val previousStyle = NotificationCompat.MessagingStyle
|
|
.extractMessagingStyleFromNotification(previousNotification)
|
|
|
|
// Add reply
|
|
Single.fromCallable {
|
|
val avatarUrl = ApiUtils.getUrlForAvatar(currentUser.baseUrl!!, currentUser.userId, false)
|
|
val me = Person.Builder()
|
|
.setName(currentUser.displayName)
|
|
.setIcon(NotificationUtils.loadAvatarSync(avatarUrl, context))
|
|
.build()
|
|
val message = NotificationCompat.MessagingStyle.Message(reply, System.currentTimeMillis(), me)
|
|
previousStyle?.addMessage(message)
|
|
|
|
// Set the updated style
|
|
previousBuilder.setStyle(previousStyle)
|
|
|
|
// Check if notification still exists
|
|
if (findActiveNotification(systemNotificationId!!) != null) {
|
|
NotificationManagerCompat.from(context).notify(systemNotificationId!!, previousBuilder.build())
|
|
}
|
|
}
|
|
.subscribeOn(Schedulers.io())
|
|
.subscribe()
|
|
}
|
|
|
|
companion object {
|
|
const val TAG = "DirectReplyReceiver"
|
|
}
|
|
}
|