[ 
https://issues.apache.org/jira/browse/CB-10317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15266252#comment-15266252
 ] 

ASF GitHub Bot commented on CB-10317:
-------------------------------------

Github user dhams commented on the pull request:

    
https://github.com/apache/cordova-plugin-file/pull/172#issuecomment-216162738
  
    @adamscybot Right , iOS version is able to parse this special char. 


> Cannot access entries of folder whose name begins with a hash symbol.
> ---------------------------------------------------------------------
>
>                 Key: CB-10317
>                 URL: https://issues.apache.org/jira/browse/CB-10317
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Plugin File
>    Affects Versions: 3.5.0
>         Environment: cordova-plugin-file
> Android 5
> Sony Xperia z2
>            Reporter: Adam Thomas
>            Priority: Minor
>              Labels: android, triaged
>
> File Plugin [version 3.0.0]
> I am trying to access a folder which happens to begin with a hash/pound 
> symbol, e.g. '#folder'.
> If you try to access this via resolveLocalFileSystemURL(), I am returned a 
> DirectoryEntry which appears to have the correct path. However, calling 
> createReader() and readEntries() on this returns the files/directories for 
> the directory above (including #folder itself) and not those that are 
> actually in #folder. Presumably, something is going on with the fact that in 
> a URL, anything after a hash symbol is a fragment part. But if this is the 
> case, how do I properly access the entries of this folder? I have tried 
> encoding the symbol with '%23' or '\%23' to no positive affect.
> I have tested this on Android. Currently unknown if this happens on iOS or 
> other platforms.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to