Thank you for visiting the BlackBerry Support Community Forums.
BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)
BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.
"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."
- Kevin Michaluk, Founder, CrackBerry.com
Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.
06-14-2012 04:04 PM
Hello BB NDK Devs,
We are trying to invoke navigator_invoke() to generate an email with a user App file attached. Unfortunately, this doesn't seem to be described in the messages:// protocol in the navigator_invoke() documentation. Is there an additional parameters to do this such as messages://attachments=<comma separated paths>.
Solved! Go to Solution.
06-14-2012 04:12 PM
06-14-2012 06:55 PM - edited 06-14-2012 06:55 PM
You can do this using mailto instead of messages. Check the syntax here:
06-18-2012 01:55 PM
That worked nicely! There are however a few gotchas:
- The file:// protocol needs to be omitted.
- It only seems to work with files located in /accounts/1000/shared. We were hope to attach some app generated data from $APPROOT/data. We were abot to work around this by copying the file to shared then attaching it. This does however mean that our app needs an additional Shared access permission just for this purpose.
Thanks again for your answer!