Uploaded image for project: 'Apache Cordova'
  1. Apache Cordova
  2. CB-7687

iOS8 : Unable to use iosExtraFileSystems

VotersWatch issueWatchersLinkUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 3.4.0, 3.5.0, 3.6.0
    • None
    • cordova-plugin-file
    • None
    • iOS 8

    Description

      Hello,

      I'm working with the filesystem plugin and i've an issue on iOS.

      I need to open a filesystem on the Library/NoCloud directory, the documentation on github says that we should set these two variable in the config.xml:

      <preference name="iosPersistentFileLocation" value="Library" />
      <preference name="iosExtraFilesystems" value="library-nosync" />

      But when i request the filesystem it gave me this path: Library/files , and i'm unable to move to Library/NoCloud because the root is files.

      window.requestFileSystem(LocalFileSystem.PERSISTENT, 0, function(fs)

      { console.log("init fs sucess"); }

      ,function(error)

      { console.log("Error init fs"+ error.code); }

      );

      I don't know if it's a bug or i've misinterpreted the documentation.

      To reproduce it, you can:
      -> create a test app
      -> install the file system plugin
      -> set these two variable in config.xml:
      <preference name="iosPersistentFileLocation" value="Library" />
      <preference name="iosExtraFilesystems" value="library-nosync" />
      -> request the file system, the path is: Library/files

      Thanks a lot.

      Best regards,

      Thibault

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            tdurand Thibault Durand
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment