Toast Quota

[hkcowboy]

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

Affected Android/Custom ROM version

crDroid 10.9

Affected device model

Xiaomi 13 Ultra

How did you install the app?

F-Droid / IzzyOnDroid

Steps to reproduce the bug

1. Open App and message shows immediately

Expected behavior

No error

Actual behavior

Toast Message saying Error: org.xmlpull.v1.XmlPullParserException: unexpected type ...

Screenshots/Screen recordings

No response

Additional information

Here is the entry from MatLog:

W/NotificationService(2251): Package org.fossify.messages is above allowed toast quota, the following toast was blocked and discarded: TextToastRecord{b2e0265 31790:org.fossify.messages/u0a532 isSystemToast=false token=android.os.BinderProxy@66ffb3a text=Error: org.xmlpull.v1.XmlPullParserException: unexpected type (position:END_DOCUMENT null@1:1 in java.io.StringReader@9872a6e) duration=1}

[Aga-C]

Have you received any MMS before this error started to show up? If so, what type of attachment does it have?

[hkcowboy]

Hello, this started as soon as I installed the app and it keeps popping up whenever I open the app and anytime i interact with the app (e.g., click back button, click on search bar, open conversation). I am able to send and receive messages: text & image, so I am not sure what is going on.

[hkcowboy]

Hi, what can be done about the error?

[Aga-C]

Until we investigate it further, it's hard to tell what can be done to avoid it. It's probably related to some MMS messages that may be corrupted, but I'm not sure.

[naveensingh]

Yeah, it's definitely an MMS message the app is failing to parse.

This could also happen while trying to import messages but that's probably not the case here.

[hkcowboy]

Yeah, it's definitely an MMS message the app is failing to parse.

This could also happen while trying to import messages but that's probably not the case here.

How would I identify which MMS message is the problem? Maybe I can delete it so the parsing issue stops

[naveensingh]

How would I identify which MMS message is the problem? Maybe I can delete it so the parsing issue stops

Depends. Can you make some code changes and compile an app?

If yes:

• Catch the exception here:

  Messages/app/src/main/kotlin/org/fossify/messages/extensions/Context.kt

  Lines 505 to 506 in 58169df

  	val text = cursor.getStringValue(Mms.Part.TEXT)
  	attachmentNames = parseAttachmentNames(text)

• Log the attachment text or delete the MMS directly
• Build and install the app

If not:

It'll be fixed soon-ish.

[naveensingh]

Duplicate of #70

[hkcowboy]

Hi, just want to say that the issue has been resolved for me with the new update. Thank you very much!