feat: reaction instead of "message sent"

[jficz]

The bot replies to a message with "message sent successfully" to the sent messages.

This clutters the conversation. It would be nicer if the bot instead just reacted to the sent message with ✔ or something similar.

[MangoCubes]

The latest build has an option to set that, do try that out. You can set it for both success and failure independently.

[jficz]

Thanks, but the new version crashes when I try to open the app. It also has just a generic icon. How can I help with debugging?

[MangoCubes]

Damn, it worked on my machine ^TM. I updated every single dependencies, so it may not be as compatible with the previous state. Can you confirm that it doesn't work even if you uninstall the app completely before reinstalling it?

If you know how to use logcat, it would be really great. You can do it with Android Debugging Bridge tool from here: https://developer.android.com/tools/releases/platform-tools.

Once you enable Android debugging, and type adb logcat, then you should see some logs. Don't worry if this seems a bit too tricky; I'll see what I can do.

About the Android icon, I forgot to copy over the logo after the project migration.

[jficz]

there you go, data migration failure:

04-15 22:04:45.770 32099 32676 E AndroidRuntime: FATAL EXCEPTION: DefaultDispatcher-worker-7
04-15 22:04:45.770 32099 32676 E AndroidRuntime: Process: ch.skew.remotrix, PID: 32099
04-15 22:04:45.770 32099 32676 E AndroidRuntime: java.lang.IllegalStateException: [RLM_ERR_MIGRATION_FAILED]: Primary key property 'RealmGlobalAccountData.id' has duplicate values after migration.

There's a stack trace there, too. If you want it, I'll send it as well.

I guess I could just wipe the config and try again then but I would very much prefer not to do that :)

Unless this is expected of course.

I can try and help you with the state migration, as far as I'm able - that is, mostly testing, my android coding skill are pretty much nonexistent atm. If you even want to fix this. I guess the config isn't that complex for an occasional reset.

[devnoname120]

I confirm that I have the same error when I upgrade from version v06alpha to the latest commit (c355ce5):

FATAL EXCEPTION: DefaultDispatcher-worker-15
Process: ch.skew.remotrix, PID: 6751
java.lang.IllegalStateException: [RLM_ERR_MIGRATION_FAILED]: Primary key property 'RealmGlobalAccountData.id' has duplicate values after migration.
	at io.realm.kotlin.internal.interop.CoreErrorConverter.asThrowable(CoreErrorConverter.kt:45)
	at io.realm.kotlin.internal.interop.realmcJNI.realm_open(Native Method)
	at io.realm.kotlin.internal.interop.realmc.realm_open(realmc.java:389)
	at io.realm.kotlin.internal.interop.RealmInterop.realm_open(RealmInterop.kt:222)
	at io.realm.kotlin.internal.ConfigurationImpl.openRealm$lambda$0(ConfigurationImpl.kt:107)
	at io.realm.kotlin.internal.ConfigurationImpl.$r8$lambda$UmB1YFg6VH-CAVlAwp6Vm17ZYlQ(Unknown Source:0)
	at io.realm.kotlin.internal.ConfigurationImpl$$ExternalSyntheticLambda1.invoke(D8$$SyntheticClass:0)
	at io.realm.kotlin.internal.interop.NativePointerKt.use(NativePointer.kt:53)
	at io.realm.kotlin.internal.ConfigurationImpl.openRealm$suspendImpl(ConfigurationImpl.kt:106)
	at io.realm.kotlin.internal.ConfigurationImpl.openRealm(Unknown Source:0)
	at io.realm.kotlin.internal.RealmImpl$1.invokeSuspend(RealmImpl.kt:133)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:100)
	at kotlinx.coroutines.EventLoopImplBase.processNextEvent(EventLoop.common.kt:263)
	at kotlinx.coroutines.BlockingCoroutine.joinBlocking(Builders.kt:95)
	at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking(Builders.kt:69)
	at kotlinx.coroutines.BuildersKt.runBlocking(Unknown Source:1)
	at io.realm.kotlin.internal.platform.CoroutineUtilsSharedJvmKt.runBlocking(CoroutineUtilsSharedJvm.kt:25)
	at io.realm.kotlin.internal.platform.CoroutineUtilsSharedJvmKt.runBlocking$default(CoroutineUtilsSharedJvm.kt:24)
	at io.realm.kotlin.internal.RealmImpl.<init>(RealmImpl.kt:115)
	at io.realm.kotlin.internal.RealmImpl.<init>(Unknown Source:0)
	at io.realm.kotlin.internal.RealmImpl$Companion.create$io_realm_kotlin_library(RealmImpl.kt:318)
	at io.realm.kotlin.Realm$Companion.open(Realm.kt:83)
	at net.folivo.trixnity.client.store.repository.realm.CreateRealmRepositoriesModuleKt.createRealmRepositoriesModule(createRealmRepositoriesModule.kt:54)
	at ch.skew.remotrix.background.CommandService.load(CommandService.kt:451)
	at ch.skew.remotrix.background.CommandService.access$load(CommandService.kt:83)
	at ch.skew.remotrix.background.CommandService$load$1.invokeSuspend(Unknown Source:14)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:98)
	at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:113)
	at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:89)
	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:586)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:820)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:717)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:704)
	Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@da54e49, Dispatchers.IO]