chrome.fileSystem.chooseEntry fail on android about mobile-chrome-apps

[kzahel]

Some more information
in fileSystem.js, getFileAndroid, in onFileReceived, nativeUri is "content://com.android.providers.media.documents/document/image%3A446"

It seems like a reasonable/good thing. I'm thinking perhaps fixing this warning may be helpful?

resolveLocalFileSystemURI is deprecated. Please call resolveLocalFileSystemURL instead. resolveLocalFileSystemURI.js:67

Hmm, looking at https://stackoverflow.com/questions/19834842/android-gallery-on-kitkat-returns-different-uri-for-intent-action-get-content, it looks like perhaps this is related to the fact that the file chooser can select entries that don't actually resolve to local files (content://), since they may be e.g. multi gigabyte files stored in google drive.

[mmocny]

Thanks for reporting this. Will take a look (Mind also peaking, @mwoghiren and @clelland?)

[clelland]

There is an issue handling the URLs that KitKat returns (I think that KitKat can't even use them internally, but I haven't finished investigating that)

This looks like an error in the File plugin, though -- I'll take a look into that.

[yingkailiang]

I also facing the same problem. Any solution now?

[clelland]

The warning about resolveLocalFileSystemURI is a red herring: that method just immediately calls through to resolveLocalFileSystemURL. It looks like the error reporting is broken -- that's the reason for Cannot read property 'error' of undefined. The underlying error from the File plugin is being masked by all of that.

[clelland]

@kzahel -- can you try again with the lastest commit? This is working for me now -- I don't actually see any errors coming back from the file system. There have been significant changes to the File plugin in the last two months, so the underlying issue may have been fixed in the meantime.

[mmocny]

@kzahel Seems you are roaming our issue tracker today -- did you get a chance to try this?

[kzahel]

Nope, sorry. I haven't. But I trust @clelland if he says it works. I'm not working on any apps with MobileChromeApps at the moment and don't have a development environment setup. Perhaps just close and let it be re-opened if it persists.

[mmocny]

@kzahel Ah thats too bad. I was hoping to try JsTorrent on Android.

Thanks for all the feedback, though.

[kzahel]

Well, alright, I'll try and get it running again tomorrow. Hold off then...

On Tue, Apr 1, 2014 at 7:08 PM, Michal Mocny [email protected]:

@kzahel https://github.com/kzahel Ah thats too bad. I was hoping to try
JsTorrent on Android.

Thanks for all the feedback, though.

Reply to this email directly or view it on GitHubhttps://github.com//issues/62#issuecomment-39282166
.