Document provider Move operation problem

Question

vgalli OP

Created Jun ’15

Replies 2

Boosts 0

Participants 3

Hello,

I am having problem with the implementation of a Document Provider, with the “move” operation in particular.

The export/import/open operations are working fine. I did look for information in the Document Provider documentation, the developers forum, stackoverflow and still not able to get it to work.

Here is what is happening, when the operation is initiated from word (word is using a move operation when creating a new file), the URL is handed over to the provider (works fine).

However when I try to copy the file located at this URL to my application the file is empty.

I tested the same workflow with other providers it works.

Any advice, hints will be really appreciated

Best Regards,

Boost

Answer 1

vidya ramesh OP

Jul ’15

Hi,

Did you get a solution/ answer for this?

I am exactly facing the same issue.

So, I do get a url in my extension once i create and try to save the document from Word app to my application. But when i try to get the size of the file from that url, it simply returns zero.

I just tried with a sample app (instead of Word application) from where I am able to move a file to my app, but could not do it from Word application.

The URL path handed over to the provider seems different in both the cases.

While trying from the sample app, my extension provider receives the path like "var/mobile/Containers/Data/Application/37309893-BBC3-4C31-B808-A72F0E519A09/Documents/myFile.docx"

whereas from Word app, it is "/var/mobile/Containers/Data/Application/F8C33B07-DA3E-4FF9-865E-9678BBED3D57/Library/Caches/docmap/e5dd37880705179870c5812d9a96affc5096545b/consumer/myFile.docx"

So, Is there something wrong with the way I get the file path?

Thanks in advance.

0

Answer 2

ilanchezhiank OP

Apr ’17

Hi, anybody found the solution for this? I am also facing the same issue. I have also tried copying the file to a tmp directory and used that, but still it did not work. It is still with 0 bytes. In my sample app, it worked fine. Only issue with "MS Word" app. I believe it is not an "MS Word" issue, as this is the behaviour from 2015 to till date.

Thanks.

0