Fossify crashes at startup

[Massedil]

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.7.0

Affected Android/Custom ROM version

Android 15 / LineageOS 22.1

Affected device model

Samsung Galaxy A52s 5G

How did you install the app?

F-Droid / IzzyOnDroid

Steps to reproduce the bug

Describe the bug

When I open the app, it freezes and then crashes after some time.

Normal SMS app from LineageOS works fine.

To Reproduce

I don't know. I suspect I received a MMS (or SMS) that Fossify Messages can't handle correctly.

Expected behavior

No crash, I can send and receive SMS and MMS.

Actual behavior

App crashes, I can't do anything with it.

Screenshots/Screen recordings

No response

Additional information

ANR in org.fossify.messages (org.fossify.messages/.activities.MainActivity)
PID: 19214
Reason: Input dispatching timed out (1c6fcc org.fossify.messages/org.fossify.messages.activities.MainActivity is not responding. Waited 5001ms for MotionEvent(deviceId=5, eventTime=267642030062000, source=TOUCHSCREEN, displayId=0, action=DOWN, actionButton=0x00000000, flags=0x00000000, metaState=0x00000000, buttonState=0x00000000, classification=NONE, edgeFlags=0x00000000, xPrecision=3.8, yPrecision=1.7, xCursorPosition=nan, yCursorPosition=nan, pointers=[0: (964.0, 189.3)]), policyFlags=0x62000000).
Parent: org.fossify.messages/.activities.MainActivity
ErrorId: 93d8a700-3a0a-48db-bd88-fa07c679a9b1
Frozen: false
Load: 0.0 / 0.0 / 0.0

[Massedil]

Same problem with Quik, I reported the bug here:
octoshrimpy/quik#678

[Massedil]

I wonder if it is a variant of https://github.com/FossifyOrg/Messages/security/advisories/GHSA-xpgw-rx45-4vmx

[Massedil]

[naveensingh]

Did you manage to isolate the message or conversation that triggered the crash?

[Massedil]

Did you manage to isolate the message or conversation that triggered the crash?

Yes. I have a backup of my sms database sqlite file.

Without replies from you and Quik, I had to delete the problematic message from my phone with the LineageOS app.

It is again a MMS with a lot of text. I don't know what is special with it and why the last fix you developed didn't handle this one.

What I had observed is that even deleting it did not solve the problem in both Fossify and Quik. I had the clear the app data of both apps for them to resync and work again.

So I suspect there is a copy of this MMS in the Fossify database, and when Fossify try to read that copy, it crashes.

What do you need to reproduce the problem ? I can send you an SQL extract of lines corresponding to the MMS. Which tables are involved ?

[naveensingh]

Which tables are involved ?

In the app, messages are stored in the messages table.

I don't know what is special with it and why the last fix you developed didn't handle this one.

Not yet sure how it managed to get in. Since the fix, the app always truncates text parts to 5000 chars.

[Massedil]

I have checked my mmssms.db database, the problematic MMS is in the table part :

I imagine to reproduce, it would be necessary to insert a message this big (433264 chars) in the Fossify messages table.