The plugin provides access to the standard interface that manages the editing and sending an email message. You can use this view controller to display a standard email view inside your application and populate the fields of that view with initial values, such as the subject, email recipients, body text, and attachments. The user can edit the initial contents you specify and choose to send the email or cancel the operation.

Using this interface does not guarantee immediate delivery of the corresponding email message. The user may cancel the creation of the message, and if the user does choose to send the message, the message is only queued in the Mail application outbox. This allows you to generate emails even in situations where the user does not have network access, such as in airplane mode. This interface does not provide a way for you to verify whether emails were actually sent.

The purpose of the plugin is to create an platform independent javascript interface for Cordova based mobile applications to access the specific email composition API on each platform.

• iOS
  See MFMailComposeViewController Class Reference for detailed informations and screenshots.

• Android

• WP8
  See How to use the email compose task for Windows Phone for detailed informations.

• MessageUI.framework

The plugin can either be installed into the local development environment or cloud based through PhoneGap Build.

Through the Command-line Interface:

# ~~ from master ~~
cordova plugin add https://github.com/katzer/cordova-plugin-email-composer.git && cordova prepare

or to use the last stable version:

# ~~ stable version ~~
cordova plugin add de.appplant.cordova.plugin.email-composer && cordova prepare

Through the Command-line Interface:

cordova plugin rm de.appplant.cordova.plugin.email-composer

Add the following xml to your config.xml to always use the latest version of this plugin:

<gap:plugin name="de.appplant.cordova.plugin.email-composer" />

or to use an specific version:

<gap:plugin name="de.appplant.cordova.plugin.email-composer" version="0.8.0" />

More informations can be found here.

• [change:] Renamed absolute: to file:
• [change:] Removed relative: attachment prefix
• [enhancement:] New res: attachment prefix
• [enhancement:] New www: attachment prefix
• [feature:] Bring back simple callback support (Android, iOS)

• See CHANGELOG.md to get the full changelog for the plugin.

The plugin creates the object window.plugin.email with following methods:

The plugin and its methods are not available before the deviceready event has been fired.

document.addEventListener('deviceready', function () {
    // window.plugin.email is now available
}, false);

The ability to send emails can be revised through the email.isServiceAvailable interface.
The method takes a callback function, passed to which is a boolean property. Optionally the callback scope can be assigned as a second parameter.

The Email service is only available on devices capable which are able to send emails. E.g. which have configured an email account and installed an email app.
You can use this function to hide email functionality from users who will be unable to use it.

window.plugin.email.isServiceAvailable(
    function (isAvailable) {
        // alert('Service is not available') unless isAvailable;
    }
);

A pre-filled email draft can be opened through the email.open or email.openDraft interface.
The method takes a hash as an argument to specify the email's properties. All properties are optional. Further more it accepts an callback function to be called after the email view has been dismissed.

After opening the draft the user may have the possibilities to edit, delete or send the email.

• An configured email account is required to send emails.
• Attachments can be either base64 encoded datas, files from the the device storage or assets from within the www folder.
• The default value for isHTML is true.
• See the examples of how to create and show an email draft.

window.plugin.email.open({
    to:          Array, // email addresses for TO field
    cc:          Array, // email addresses for CC field
    bcc:         Array, // email addresses for BCC field
    attachments: Array, // paths to the files you want to attach or base64 encoded data streams
    subject:    String, // subject of the email
    body:       String, // email body (could be HTML code, in this case set isHtml to true)
    isHtml:    Boolean, // indicats if the body is HTML or plain text
}, callback, scope);

The following example shows how to create and show an email draft pre-filled with different kind of properties.

window.plugin.email.open({
    to:      ['[email protected]'],
    cc:      ['[email protected]'],
    bcc:     ['[email protected]', '[email protected]'],
    subject: 'Greetings',
    body:    'How are you? Nice greetings from Leipzig'
});

Of course its also possible to open a blank email draft.

window.plugin.email.open();

Its possible to send the email body either as text or HTML. In the case of HTML the isHTML properties needs to be set.

window.plugin.email.open({
    to:      ['[email protected]'],
    subject: 'Congratulations',
    body:    '<h1>Happy Birthday!!!</h1>',
    isHtml:  true
});

The open method supports additional callback to get informed when the view has been dismissed.

window.plugin.email.open(properties, function () {
    console.log('email view dismissed');
}, this);

Attachments can be either base64 encoded datas, files from the the device storage or assets from within the www folder.

The code below shows how to attach an base64 encoded image which will be added as a image with the name icon.png.

window.plugin.email.open({
    subject:     'Cordova Icon',
    attachments: ['base64:icon.png//iVBORw0KGgoAAAANSUhEUgAAADwAAAA8CAYAAAA6/...']
});

The path to the files must be defined absolute from the root of the file system. The kind of the path may vary between mobile platforms.

window.plugin.email.open({
    attachments: [
        'file:///storage/sdcard/icon.jpg', //=> Android
        'file:///Users/.../Library/Application Support/iPhone Simulator/7.0.3/Applications/E7981856-.../HelloCordova.app/icon.jpg' //=> iOS
    ]
});

On iOS it is also possible to point to the relative app's Documents directory:

window.plugin.email.open({
    attachments: [
        'file://icon.jpg' //=> points to /.../HelloCordova.app/../Documents/icon.jpg (iOS)
    ]
});

Each app has a resource folder, e.g. the res folder for Android apps or the Resource folder for iOS apps.
The following examples shows how to attach files from within the app's resource folder.

window.plugin.email.open({
    attachments: [
        'res://drawable/icon.png', //=> points to res/drawable/icon.png (Android)
        'res://icons/icon.jpg'     //=> points to Resource/icons/icon.png (iOS)
    ]
});

The path to the files must be defined relative from the root of the mobile web app folder, which is located under the www folder.

window.plugin.email.open({
    attachments: [
        'www://img/logo.png' //=> e.g. assets/www/img/logo.png (Android)
    ]
});

An configured email account is required to send emails.

Attachments and HTML formatted body are not supported.

Along with Cordova 3 and Windows Phone 8 the version.bat script has to be renamed to version.

On Mac or Linux

mv platforms/wp8/cordova/version.bat platforms/wp8/cordova/version

On Windows

ren platforms\wp8\cordova\version.bat platforms\wp8\cordova\version

The error indicates, that the MessageUI.framework is not linked to your project. The framework is linked automatically when the plugin was installed, but may removed later.

Undefined symbols for architecture i386:
  "_OBJC_CLASS_$_MFMailComposeViewController", referenced from:
      objc-class-ref in APPEmailComposer.o
ld: symbol(s) not found for architecture i386
clang: error: linker command failed with exit code 1 (use -v to see invocation)

1. Fork it
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create new Pull Request

This software is released under the Apache 2.0 License.

© 2013-2014 appPlant UG, Inc. All rights reserved