This article describes how you can use Wisej.NET Hybrid to open the default email app. When the email app is loaded, it can be set to create a new email with the specified recipients, subject, and body.
Get started
To access the email functionality, the following platform specific setup is required.
Android
If your project's Target Android version is set to Android 11 (R API 30) or higher, you must update your Android Manifest with queries that use Android's package visibility requirements.
In the Platforms/Android/AndroidManifest.xml file, add the following queries/intent nodes in the manifest node:
<queries>
<intent>
<action android:name="android.intent.action.SENDTO" />
<data android:scheme="mailto" />
</intent>
</queries>
iOS / Mac Catalyst
Apple requires that you define the schemes you want to use. Add the LSApplicationQueriesSchemes key and schemes to the Platforms/iOS/Info.plist and Platforms/MacCatalyst/Info.plist files:
<key>LSApplicationQueriesSchemes</key>
<array>
<string>mailto</string>
</array>
Using Email
The Email functionality works by providing the email information as an argument to the Compose method. In this example, the EmailMessage type is used to represent the email information:
if (Device.Email.IsComposeSupported)
{
string subject = "Hello friends!";
string body = "It was great to see you last weekend.";
string[] recipients = new[] { "john@contoso.com", "jane@contoso.com" };
var message = new EmailMessage
{
Subject = subject,
Body = body,
BodyFormat = EmailBodyFormat.PlainText,
To = new List<string>(recipients)
};
Device.Email.Compose(message);
}
File attachments
When creating the email provided to the email client, you can add file attachments. The file type (MIME) is automatically detected, so you don't need to specify it. Some mail clients may restrict the types of files you send, or possibly prevent attachments altogether.
Pass attachments through Device.Email.Compose(message, attachments), where attachments maps file names to readable streams. The Hybrid API sends those streams to the native client; it does not use MAUI's EmailAttachment collection.
The following example belongs inside an async Wisej event handler. It reads a file from the native client through the Hybrid file-system module, then passes the resulting stream as an attachment. Include System.IO, System.Collections.Generic and Wisej.Hybrid using directives.
if (Device.Email.IsComposeSupported)
{
string subject = "Hello friends!";
string body = "It was great to see you last weekend. I've attached a photo of our adventures together.";
string[] recipients = new[] { "john@contoso.com", "jane@contoso.com" };
var message = new EmailMessage
{
Subject = subject,
Body = body,
BodyFormat = EmailBodyFormat.PlainText,
To = new List<string>(recipients)
};
string picturePath = Path.Combine(Device.FileSystem.CacheDirectory, "memories.jpg");
byte[] bytes = await Device.FileSystem.ReadBytesAsync(picturePath);
using var picture = new MemoryStream(bytes);
var attachments = new Dictionary<string, Stream> { ["memories.jpg"] = picture };
Device.Email.Compose(message, attachments);
}
See DeviceEmail for the attachment parameter and DeviceFileSystem for native file access.
Platform Differences
Android
Not all email clients for Android support EmailBodyFormat.Html, since there is no way to detect this, we recommend using EmailBodyFormat.PlainText when sending emails.
iOS
Both EmailBodyFormat.Html and EmailBodyFormat.PlainText are supported.
To use the email API on iOS, you must run it on a physical device. Otherwise, an exception is thrown.
Windows
Only supports EmailBodyFormat.PlainText as the EmailMessage.BodyFormat. Attempting to send an Html email throws the exception: FeatureNotSupportedException.
Not all email clients support sending attachments.