Strange behavior when replying from notification

[SilverPuppy]

Checklist

• I can reproduce the bug with the latest version given here.
• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.
• I have read and understood the contribution guidelines.

Affected app version

1.0.0

Affected Android/Custom ROM version

A12/Moto G stock

Affected device model

Moto G Pure

How did you install the app?

F-Droid / IzzyOnDroid

Steps to reproduce the bug

Receive a message, get notification. Expand notification and select "Reply", compose a response and send.

Expected behavior

Send a message as usual and everything keeps rolling along.

Actual behavior

Sending will take a long time, and subsequently returning to the main app, it will crash to a black screen upon trying to open any thread. Phone reboot is seemingly the only way to restore function; simply closing the app from the not responding popup and restarting it is not sufficient.

Screenshots/Screen recordings

No response

Additional information

No response

[Aga-C]

If anybody else also encounters this bug, please write your device model and OS version. It seems to be device/software specific, so we'd like to have as much info as possible.

[SilverPuppy]

While this has triggered the behavior several times, yesterday it did this crash in spite of my careful avoidance of notification replies. I use it a lot throughout the day, and apparently the crash doesn't have to do specifically with notification replies, although that seems to trigger it.

I understand that this is still a very new program, and expected some bugs. Is there a debug version I could use that would provide a trace log?

[Aga-C]

We don't have any separate version for debugging purposes. If you'd like, you could build yourself a version through Android Studio, there isn't any external configuration that would make it harder than just pressing the Start button.

Also, it's not a new app, just the branding is new. Fossify apps are forks of Simple Mobile Tools after they were sold to a non-FOSS-friendly company. SMS app dates back to 2020.

[doubleddav]

If it helps, I have this exact issue as well, and it's consistent. My device is a Sony Xperia 10 III, running stock official Sony image on Android 13

No root, no MicroG or anything else unusual

[yparitcher]

Can reproduce on:

Pixel 6a, A14, Grapheneos

It happens more often if i reply right after the message is received. I wonder if this has to do with adding reply to the in apps sms db before the original message.

When it happens if i open that conversation no messages load for a few minutes, force stopping the app and re opening it fixes it

[SilverPuppy]

I have noticed this crash happening seemingly at random occasionally even if I don't reply from the notification. Mark Read from the notification seems to trigger it occasionally, and sometimes it happens when I'm just using it normally. In my case, force stop does NOT make it work correctly again. I must reboot the device.

I do have a huge database. I've been rolling my messages forward from past devices for years, and am a heavy user. I'm not sure if that's a common factor with the others experiencing this crash.

[SilverPuppy]

I realized that even "mark as read," though it appears to work, hangs the program, too. Any interaction with the notification seems to go badly on my device for some reason. And force close is not enough; I do have to reboot.

[VA1DER]

This bug occurs on every device I have, and was inherited from Simple Messenger. I'm skeptical it's a device specific bug.

Occurs on:

• Samsung Galaxy S21A with Android 12
• Fairphone FP3+ with either Android 11 or /e/OS (LineageOS/AOSP 11)
• Fairphone FP5 with either Android 13 or /e/OS (LineageOS/AOSP 13)

Notably I can confirm that both replying the through notification or tapping mark as read.

[MorealDeBrevans]

I have this bug too. I'm on app version 1.0.1 installed from F-droid, my device is Huawei AMN-LX9 with Android 9.
The app crash prevents my phone from even receiving messages. I don't mind rebooting my phone every now and then but this specific problem is what's annoying.