[ 
https://issues.apache.org/jira/browse/CB-11174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Kotikov updated CB-11174:
----------------------------------
    Description: When project dir is inside of symlinked directory (say 
{{/var}} on OS X), {{getPlatformApi}} method in cordova-lib doesn't resolve 
real path before cache lookup and uses provided path. This causes returning two 
separate instances of {{PlatformApi}} class when {{getPlatformApi}} is first 
called with symlinked path and then with real one, though in fact both paths 
are pointing to the same project  (was: When project dir is inside of symlinked 
directory (say {{/var}} on OS X), {{getPlatformApi}} method in cordova-lib 
doesn't resolve real path before cache lookup and uses provided path. This 
causes returning two separate instances when {{getPlatformApi}} is first called 
with symlinked path and then with real one, though in fact both paths are 
pointing to the same project)

> cordova platformApi cache isn't dealing correctly with symlinked project dirs
> -----------------------------------------------------------------------------
>
>                 Key: CB-11174
>                 URL: https://issues.apache.org/jira/browse/CB-11174
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: CordovaLib
>    Affects Versions: 6.1.1
>            Reporter: Vladimir Kotikov
>            Assignee: Vladimir Kotikov
>
> When project dir is inside of symlinked directory (say {{/var}} on OS X), 
> {{getPlatformApi}} method in cordova-lib doesn't resolve real path before 
> cache lookup and uses provided path. This causes returning two separate 
> instances of {{PlatformApi}} class when {{getPlatformApi}} is first called 
> with symlinked path and then with real one, though in fact both paths are 
> pointing to the same project



--
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