Exports fail

[ZethiaZ]

trafficstars

Checklist

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

Affected app version

1.1.3

Affected Android/Custom ROM version

GrapheneOS / Android 15

Affected device model

Pixel 8

How did you install the app?

F-Droid / IzzyOnDroid

Steps to reproduce the bug

Attempt to export SMS & MMS messages. Select any folder. (I tested a few different ones) Fails with an error.

Expected behavior

I expect a JSON containing MMS and SMS messages to be created in the target folder.

Actual behavior

Fails, export messages window closes. Error is given on the bottom of the screen. No JSON or file of any kind is created in target folder.

Screenshots/Screen recordings

Additional information

Is there any way for me to provide a more detailed log? I'm not sure how to access one or where that would be.

[ZethiaZ]

When I disable MMS exports and do only SMS exports, it succeeds. MMS exports seem to be the issue.

[bblhd]

Also experiencing this bug, on my device, also reporting: "Java.Lang.OutOfMemoryError: F...".

[tom93]

This is a known issue, there are notes in #139 on how this could be fixed.

Doing separate SMS-only and MMS-only exports (as you have done) is the only available workaround. The alternative is to use a different app such as "SMS Import / Export". (I suppose another somewhat extreme workaround would be to individually download and delete the largest MMS attachments, in the hope that the remaining MMS will be small enough to export. This is obviously not a great option, and I don't recommend it.)

There is no need for more detailed information in this case, but it would be good to add "OutOfMemoryError" to the issue title. (In general, the way to get more detailed logs is using the Android debug logs aka "logcat", but it's a pain.)