Skip to content
This repository has been archived by the owner on Sep 4, 2019. It is now read-only.

EmailSender plugin should support non-file attachments #293

Open
rtholmes opened this issue Apr 25, 2014 · 5 comments
Open

EmailSender plugin should support non-file attachments #293

rtholmes opened this issue Apr 25, 2014 · 5 comments
Assignees

Comments

@rtholmes
Copy link
Contributor

MessageBuilder can also take Attachment(s) that can be constructed from strings (or byte arrays):

https://developer.blackberry.com/native/reference/cascades/bb__pim__message__attachment.html#function-attachment-mimetype-name-textdata

Supporting attachments in this way would be beneficial because it would allow webworks apps to append attachments to emails without requiring 'Shared File' permissions (currently the invoke card for email requires a path to the shared directory for attachments; private app storage cannot be used).

@timwindsor
Copy link
Collaborator

Added by #340

@rtholmes
Copy link
Contributor Author

Just checking: in the end this just added the ability to specify attachments by path right? I think this was previously supported by blackberry.invoke.card.invokeEmailComposer without the plugin. This original bug was about being able to supply an attachment as a stream of data instead of a path to a file. This would permit attachments to be generated by apps and attached without requiring the access_shared permission to be set.

@timwindsor
Copy link
Collaborator

Weird, for some reason I thought that had been included already. This does allow files to be included from the App's private filesystem, so it does bypass the need to use the shared folder. I'll reopen it though so that we can add the byte array feature.

@timwindsor timwindsor reopened this Jan 16, 2015
@rtholmes
Copy link
Contributor Author

Thanks Tim. Since it is already using MessageBuilder under the covers, I think it would just be a 30 minute fix to allow a var to be passed containing what would be the contents of a text file or the base64 of an image.

@timwindsor
Copy link
Collaborator

All right, please check out the latest push and see how it works for you.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants