Sharing image from Messages does not work / Conceptual problem with sharing files in place

REPRODUCIBILITY: 100%
OS VERSION: 4.5.0.18
HARDWARE: Xperia 10 III
UI LANGUAGE: Swedish
REGRESSION: Yes

DESCRIPTION:

Sharing images received over MMS to anything that does not have the CommunicationHistory permission fails.

PRECONDITIONS:

Image received over MMS.

STEPS TO REPRODUCE:

  1. Share an image from the Messages application (to basically anything that is not a Jolla app).
    e.g. via SeaPrint share plugin(version 1.0) to SeaPrint (version 1.3 - soon in store), or to an Android application like LLCrop.

EXPECTED RESULT:

Image can be read by the receiving application.

ACTUAL RESULT:

Image can not be read by the receiving application.

MODIFICATIONS:

None.

ADDITIONAL INFORMATION:

Sharing a resource by sending a path to it seems conceptually broken together with SailJail.
This would assume that the target application must have the same permissions, which generally is not the case.
Sure; it could be argued that image-receiving applications should at least have access to Pictures, but then the sending end must make sure to put it there first, which might be a lot of hassle.

I have previously asked for a neutral ground to share temporary files to/between jailed applications, but perhaps even otherwise “permanent” files needs it too. Or maybe, the whole thing should go over dbus, and the receiving end be responsible to create a file if needed? This is what i do for plaintext in SeaPrint right now, and it’s not very convenient. It is probably not compatible with sharing to Android apps either.

4 Likes

Copied to internal tracker

1 Like

Known shortcoming. We do pass the file descriptor via d-bus and there’s an internal mechanism for writing the content to a temp file, but we haven’t yet opened these for general use because plain file descriptors are quite low level and not nice to play with, and then the temp file way is not nice for huge files.

1 Like