Mailing-List: contact issues-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Date: Wed, 2 Jul 2014 18:59:24 +0000 (UTC)
From: "Ian Clelland (JIRA)" <jira@apache.org>
To: issues@cordova.apache.org
Message-ID: <JIRA.12722538.1403197509145.90143.1404327564721@arcas>
In-Reply-To: <JIRA.12722538.1403197509145@arcas>
References: <JIRA.12722538.1403197509145@arcas>
Subject: [jira] [Commented] (CB-6984) requestFileSystem does not always
 return after document reload
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ian Clelland commented on CB-6984:
----------------------------------

This certainly appears to be the same bug as CB-6667. I've seen your test app run as long as 300+ cycles, or fail in as little as 5, using the ONLINE_EVENT bridge mode.

Switching it to LOAD_URL mode, I've had it running now for 20 minutes without a failure, so there's definitely something getting out of sync with our default mode.

> requestFileSystem does not always return after document reload
> --------------------------------------------------------------
>
>                 Key: CB-6984
>                 URL: https://issues.apache.org/jira/browse/CB-6984
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Plugin File
>    Affects Versions: 3.5.0
>         Environment: - Experienced on Nexus 5 smartphone ( Android 4.4.3 )
> - File plugin 1.2.0
>            Reporter: Zarko Hristovski
>         Attachments: fsreload.zip
>
>
> Once in a while we need to reload the application ( document ) because a part of it is dynamic - downloaded from a server and injected into the app.
> The problem is that sometimes and quite often, our app won't be able to compete its initialization since requestFileSystem neither succeeds nor fails, it just hangs there. This happens after location.reload(). It seems like some sort of timing issue and the number of attempts does not actually matter.
> I'll include a slightly modified "hello world" app that should show the problem.
> This doesn't seem to affect iOS.


--
This message was sent by Atlassian JIRA
(v6.2#6252)