-
-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do not crash if mms part data is not exist #42
Comments
Thank you for reporting this. I'm not sure why Android is providing us with the name of a non-existent file, but perhaps we need to add some sort of null check to work around this. Is this a normal Android system, or have you done low-level manipulation of the filesystem, perhaps deleting the JPG file in question? |
I didn't do any low-level manipulations and didn't delete the JPG file. But I can't guarantee that some software didn't. I'm using a custom build of android (crDroid 4.7 on android 8.1.0), but I will assume that it works like a "normal" android. |
Thank you. I should probably add a check for problems, even if I don't understand why they would occur :) |
I've attached a patched version of the app that should catch and log any exceptions thrown when trying to access MMS binary message parts and then continue with the export. Please test it and report back here, if you can. |
catch-mms-part-access-exceptions.zip perfectly works without any errors |
Thank you! Closing. [Edit:] It's this commit (below in the thread) that fixes the problem. |
Catch (and log) exceptions (e.g., FileNotFoundException) thrown when trying to access binary data of MMS parts during export. Closes: #42
When i export messages with "Include (encoded) binary MMS data", i get fatal error:
Tail in messages.json:
Probably it's because the file doesn't exist:
Without "Include (encoded) binary MMS data" all works fine.
The text was updated successfully, but these errors were encountered: