[jira] [Updated] (CB-10463) Windows Appxmanifest caching should use the same mechanism as ConfigChanged uses

["Vladimir Kotikov (JIRA)" <ji...@apache.org>]

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

Vladimir Kotikov updated CB-10463:
----------------------------------
    Component/s: CordovaCommon

> Windows Appxmanifest caching should use the same mechanism as ConfigChanged uses
> --------------------------------------------------------------------------------
>
>                 Key: CB-10463
>                 URL: https://issues.apache.org/jira/browse/CB-10463
>             Project: Apache Cordova
>          Issue Type: Improvement
>          Components: CordovaCommon, Windows
>    Affects Versions: 4.3.0
>            Reporter: Vladimir Kotikov
>             Fix For: 1.1.0, 4.4.0
>
>
> CB-10394 revealed a problem with Appxmanifest class and its file caching. The problem is that at some moment the same file might be cached twice by different facilities and hence changes, made in one of these places might be ignored.
> There is a temporary solution - [cordova-windows PR #143|https://github.com/apache/cordova-windows/pull/143], which fixes the regression, but we need for more general solution.
> A more general way to resolve this is to reuse the same caching mechanism for Appxmanifests as used by {{ConfigChanges}} module. This should resolve the stale cache issue automatically because the one cache will be used for all.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org