Launch mailto is converting spaces to + when on iOS

[topherslalom]

When I set a button's OnSelect to Launch("mailto:example@example.com?subject=Here%20is%20my subject&body=here is my body")

And click the button on desktop (launching Outlook) or iPhone, the mail app opens with the subject = Here+is+my+subject

If I change the '?' to a '&', it works on desktop launching Outlook, but iPhone doesn't work at all (button is clicked, mail app isn't opened)

How can I get spaces in my subject and body working on both Desktop and iOS?

[v-micsh-msft]

Hi @topherslalom,

Thanks for the feedback.

Issue could be reproduced from my side.

Generally the Mailto format should be:

mailto:foo@example.com?cc=bar@example.com&subject=Greetings%20from%20Cupertino!&body=Wish%20you%20were%20here!

Changing the ? to & would have the %20 translated to sapce correctly, and the space would also work without %20.

I will collect this as a feedback from my side.

And I will update here once I got any response.

Besides, have you checked the Office 365 outlook (or the outlook conneciton) connection?

Office 365 Outlook

You may take a try with the following function to send the Email:

Office365.SendEmail() 

Regards,

Michael

[topherslalom]

I did find an alternative way using a Flow, but it would be nice to have the Launch("mailto:...") option available as well.

Thanks!

[Anonymous · Accepted solution]

The Launch command takes optional parameters in the following format;

Launch("address", "name", "value", "name", "value"....)  where name/value pairs are queries passed to a web URL.

We tend to put the whole "mailto:blahblah?subject=etc" into the address field, when actually you should use the Launch optional query parameters to pass in what you need, so;

address is the URL containing the mailto command and email address

Each name/value pair is a query parameter with it's value

Example:

Launch("mailto:bobjones@home.com", "subject", "Here's a subject line", "body", "Hello,

How are you?



Line breaks are just carriage returns and spaces remain spaces!")

I've tested this with Chrome and Edge (Edge was giving me headaches originally) and it works fine.  I haven't tested all the RFC stated parameters or attachments yet but this works and no annoying +'s!

Hope this helps someone

Kind regards,

R

[avaldez]

This resolves my issue as well - THANKS!!!!!!

[Anonymous]

Awesome 🙂