04-25-2013 11:13 AM - edited 04-25-2013 11:14 AM
I integrated my application in the share menu for a specific file type.
I receive an email with an attachment of this file type and select share from the context menu.
For request.uri() i get
I am not allowed to open this file.
My invoke target in the bar-descriptor.xml currently looks like this (redacted with x):
<invoke-target id="x"> <invoke-target-name>x</invoke-target-name> <icon><image>logo.png</image></icon> <invoke-target-type>application</invoke-target-typ
e> <filter> <action>bb.action.SHARE</action> <mime-type>*</mime-type> <property var="exts" value="x"/> </filter> </invoke-target>
Can i specify a FileTransferMode in the definition? Or is there anything else i can do to access the file?
04-25-2013 03:08 PM
I ran into the same problem when trying to integrate into the "Share contact" menu of the Contacts app:
<type>APPLICATION</type> <filter> <action>bb.action.SHARE</action> <mime-type>*</mime-type> <property var="exts" value="vcf" /> </filter>
I also received a file URI in the form "file:///accounts/1000/invoke/appname/xa0000000000
Interestingly when integrating into the share menu of an appointment in the Calendar app (*.vcs file), I received a file URI in the form "file:///accounts/1000/shared/.../appointment.vcs" with the file transfer mode set to PRESERVE.
According to http://developer.blackberry.com/cascades/reference
Further information about PRESERVE can be found at http://developer.blackberry.com/html5/api/blackber
Describes the file transfer mode where the provided URI is preserved as is. No box-2-box logic is applied
So it seems that COPY_RW is supposed to copy the file to the sandbox of the invoked application. But why isn't it possible to access the file then? Maybe the provided file URI cannot be used directly and must be modified in some way? But what exact kind of box-2-box logic has to be applied then?
04-25-2013 03:12 PM
04-26-2013 03:16 AM
My invoke target id is: packagename.config, with package name being the id in the bar-descriptor.
And this target id is used in the url of the invokerequest i get:
05-03-2013 09:29 AM
Need some more info to track this one down. Can you capture logs and submit them to Issue Tracker? Here is how:
05-03-2013 09:49 AM - edited 05-03-2013 10:44 AM
Created a report with a made-up incident number and attached it to a private issue
05-03-2013 01:40 PM
06-05-2013 09:29 PM
Any news on this?
I'm having the same problem. I'm trying to open an e-mail image attachment: The request.uri() is set to the jpg located in file:///accounts/1000/invoke/... and the file transfer mode is CopyReadOnly. If I try to open the file I get permission denied. However, if I set the image uri to a Cascades SystemToast "icon" property the toast is shown with the image rendered.
06-06-2013 04:52 AM