[jira] [Created] (CB-5662) Arguments for hooks
Вячеслав Шабельник created CB-5662: -- Summary: Arguments for hooks Key: CB-5662 URL: https://issues.apache.org/jira/browse/CB-5662 Project: Apache Cordova Issue Type: New Feature Components: CLI Reporter: Вячеслав Шабельник Hooker doesn't pass arguments from cordova call to hooks. So hook cant get info about in what mode (release/debug) it runs or for what platform. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Created] (CB-5663) Geolocation minTime on Android is 60s, preventing realtime updates
Clayton Grassick created CB-5663: Summary: Geolocation minTime on Android is 60s, preventing realtime updates Key: CB-5663 URL: https://issues.apache.org/jira/browse/CB-5663 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 3.3.0 Environment: Android 4.2, Intel Yolo phone Reporter: Clayton Grassick cordova-plugin-geolocation / src / android / GPSListener.java has the minTime parameter on the locationManager.requestLocationUpdates(LocationManager.GPS_PROVIDER, 6, 0, this) set to 60 seconds. On Android platforms that respect that parameter, it means that the GPS location will only update every 60 seconds, making it less useful. I suggest changing it to 1000ms instead. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Created] (CB-5664) AppCache's checking event fired more than once per App startup.
Godric Kwok created CB-5664:
---
Summary: AppCache's checking event fired more than once per App
startup.
Key: CB-5664
URL: https://issues.apache.org/jira/browse/CB-5664
Project: Apache Cordova
Issue Type: Bug
Components: Android
Affects Versions: 3.3.0
Environment: Android 4.1.2 (SDK 16)
Reporter: Godric Kwok
Expected Behavior:
1) AppCache is only check ONCE per App startup.
Observed Behavior:
1) AppCache is check *multiple times* on random per App Startup.
Steps to repeat:
1) console.log() AppCache's checking event.
2) Start App, see checking once.
3) navigator.app.exitApp(), then re-launches App.
4) First relaunch leads to a single checking still.
5) Repeat the relaunch a few times.
6) Then you'll see sometimes it's a double, triple, or quadruple (but never 5x).
7) Only a KILL from task switcher will reset these accumulations.
Code Snippet:
document.addEventListener('deviceready', function(){
function logEvent(event) {
console.log('appcache: '+event.type);
}
window.applicationCache.addEventListener('checking', logEvent, false);
window.applicationCache.addEventListener('noupdate', logEvent, false);
window.applicationCache.addEventListener('downloading', logEvent, false);
window.applicationCache.addEventListener('progress', logEvent, false);
window.applicationCache.addEventListener('cached', logEvent, false);
window.applicationCache.addEventListener('updateready', logEvent, false);
window.applicationCache.addEventListener('obsolete', logEvent, false);
window.applicationCache.addEventListener('error', logEvent, false);
document.addEventListener('backbutton', function(){
navigator.app.exitApp();
}, false);
}, false);
LogCat pattern:
(1x)
12-17 21:11:13.470: I/Web Console(2142): appcache: checking:23
12-17 21:11:13.478: I/Web Console(2142): appcache: noupdate:23
(1x updateready)
12-17 21:11:47.775: I/Web Console(2142): appcache: checking:23
12-17 21:11:50.072: I/Web Console(2142): appcache: downloading:23
12-17 21:11:50.072: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.166: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.197: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.697: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.697: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.697: I/Web Console(2142): appcache: updateready:23
12-17 21:11:50.697: I/Web Console(2142): appcache: updateready:23
(2x)
12-17 21:12:27.283: I/Web Console(2142): appcache: checking:23
12-17 21:12:27.283: I/Web Console(2142): appcache: checking:23
12-17 21:12:29.759: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:29.759: I/Web Console(2142): appcache: noupdate:23
(2x)
12-17 21:12:35.447: I/Web Console(2142): appcache: checking:23
12-17 21:12:35.447: I/Web Console(2142): appcache: checking:23
12-17 21:12:38.025: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:38.025: I/Web Console(2142): appcache: noupdate:23
(3x)
12-17 21:12:45.322: I/Web Console(2142): appcache: checking:23
12-17 21:12:45.322: I/Web Console(2142): appcache: checking:23
12-17 21:12:45.322: I/Web Console(2142): appcache: checking:23
12-17 21:12:47.345: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:47.345: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:47.345: I/Web Console(2142): appcache: noupdate:23
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Updated] (CB-5664) AppCache's checking event fired more than once per App startup.
[
https://issues.apache.org/jira/browse/CB-5664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Godric Kwok updated CB-5664:
Description:
Expected Behavior:
1) AppCache is only checked *once* per App startup.
Observed Behavior:
1) AppCache is checked *multiple times* on random per App Startup.
Steps to repeat:
1) console.log() AppCache's checking event.
2) Start App, see checking once.
3) navigator.app.exitApp(), then re-launches App.
4) First relaunch leads to a single checking still.
5) Repeat the relaunch a few times.
6) Then you'll see sometimes it's a double, triple, or quadruple (but never 5x).
7) Only a KILL from task switcher will reset these accumulations.
Code Snippet:
document.addEventListener('deviceready', function(){
function logEvent(event) {
console.log('appcache: '+event.type);
}
window.applicationCache.addEventListener('checking', logEvent, false);
window.applicationCache.addEventListener('noupdate', logEvent, false);
window.applicationCache.addEventListener('downloading', logEvent, false);
window.applicationCache.addEventListener('progress', logEvent, false);
window.applicationCache.addEventListener('cached', logEvent, false);
window.applicationCache.addEventListener('updateready', logEvent, false);
window.applicationCache.addEventListener('obsolete', logEvent, false);
window.applicationCache.addEventListener('error', logEvent, false);
document.addEventListener('backbutton', function(){
navigator.app.exitApp();
}, false);
}, false);
LogCat pattern:
(1x)
12-17 21:11:13.470: I/Web Console(2142): appcache: checking:23
12-17 21:11:13.478: I/Web Console(2142): appcache: noupdate:23
(1x updateready)
12-17 21:11:47.775: I/Web Console(2142): appcache: checking:23
12-17 21:11:50.072: I/Web Console(2142): appcache: downloading:23
12-17 21:11:50.072: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.166: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.197: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.697: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.697: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.697: I/Web Console(2142): appcache: updateready:23
12-17 21:11:50.697: I/Web Console(2142): appcache: updateready:23
(2x)
12-17 21:12:27.283: I/Web Console(2142): appcache: checking:23
12-17 21:12:27.283: I/Web Console(2142): appcache: checking:23
12-17 21:12:29.759: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:29.759: I/Web Console(2142): appcache: noupdate:23
(2x)
12-17 21:12:35.447: I/Web Console(2142): appcache: checking:23
12-17 21:12:35.447: I/Web Console(2142): appcache: checking:23
12-17 21:12:38.025: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:38.025: I/Web Console(2142): appcache: noupdate:23
(3x)
12-17 21:12:45.322: I/Web Console(2142): appcache: checking:23
12-17 21:12:45.322: I/Web Console(2142): appcache: checking:23
12-17 21:12:45.322: I/Web Console(2142): appcache: checking:23
12-17 21:12:47.345: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:47.345: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:47.345: I/Web Console(2142): appcache: noupdate:23
was:
Expected Behavior:
1) AppCache is only checked ONCE per App startup.
Observed Behavior:
1) AppCache is checked *multiple times* on random per App Startup.
Steps to repeat:
1) console.log() AppCache's checking event.
2) Start App, see checking once.
3) navigator.app.exitApp(), then re-launches App.
4) First relaunch leads to a single checking still.
5) Repeat the relaunch a few times.
6) Then you'll see sometimes it's a double, triple, or quadruple (but never 5x).
7) Only a KILL from task switcher will reset these accumulations.
Code Snippet:
document.addEventListener('deviceready', function(){
function logEvent(event) {
console.log('appcache: '+event.type);
}
window.applicationCache.addEventListener('checking', logEvent, false);
window.applicationCache.addEventListener('noupdate', logEvent, false);
window.applicationCache.addEventListener('downloading', logEvent, false);
window.applicationCache.addEventListener('progress', logEvent, false);
window.applicationCache.addEventListener('cached', logEvent, false);
window.applicationCache.addEventListener('updateready', logEvent, false);
window.applicationCache.addEventListener('obsolete', logEvent, false);
window.applicationCache.addEventListener('error', logEvent, false);
document.addEventListener('backbutton', function(){
navigator.app.exitApp();
}, false);
}, false);
LogCat pattern:
(1x)
12-17 21:11:13.470: I/Web Console(2142): appcache: checking:23
12-17 21:11:13.478: I/Web Console(2142): appcache: noupdate:23
(1x updateready)
12-17 21:11:47.775: I/Web Console(2142): appcache: checking:23
12-17 21:11:50.072: I/Web Console(2142): appcache: downloading:23
12-17 21:11:50.072: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.166: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.197:
[jira] [Updated] (CB-5664) AppCache's checking event fired more than once per App startup.
[
https://issues.apache.org/jira/browse/CB-5664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Godric Kwok updated CB-5664:
Description:
Expected Behavior:
1) AppCache is checked only *once* per App startup.
Observed Behavior:
1) AppCache is checked *multiple times* on random per App Startup.
Steps to repeat:
1) console.log() AppCache's checking event.
2) Start App, see checking once.
3) navigator.app.exitApp(), then re-launches App.
4) First relaunch leads to a single checking still.
5) Repeat the relaunch a few times.
6) Then you'll see sometimes it's a double, triple, or quadruple (but never 5x).
7) Only a KILL from task switcher will reset these accumulations.
Code Snippet:
document.addEventListener('deviceready', function(){
function logEvent(event) {
console.log('appcache: '+event.type);
}
window.applicationCache.addEventListener('checking', logEvent, false);
window.applicationCache.addEventListener('noupdate', logEvent, false);
window.applicationCache.addEventListener('downloading', logEvent, false);
window.applicationCache.addEventListener('progress', logEvent, false);
window.applicationCache.addEventListener('cached', logEvent, false);
window.applicationCache.addEventListener('updateready', logEvent, false);
window.applicationCache.addEventListener('obsolete', logEvent, false);
window.applicationCache.addEventListener('error', logEvent, false);
document.addEventListener('backbutton', function(){
navigator.app.exitApp();
}, false);
}, false);
LogCat pattern:
(1x)
12-17 21:11:13.470: I/Web Console(2142): appcache: checking:23
12-17 21:11:13.478: I/Web Console(2142): appcache: noupdate:23
(1x updateready)
12-17 21:11:47.775: I/Web Console(2142): appcache: checking:23
12-17 21:11:50.072: I/Web Console(2142): appcache: downloading:23
12-17 21:11:50.072: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.166: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.197: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.697: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.697: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.697: I/Web Console(2142): appcache: updateready:23
12-17 21:11:50.697: I/Web Console(2142): appcache: updateready:23
(2x)
12-17 21:12:27.283: I/Web Console(2142): appcache: checking:23
12-17 21:12:27.283: I/Web Console(2142): appcache: checking:23
12-17 21:12:29.759: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:29.759: I/Web Console(2142): appcache: noupdate:23
(2x)
12-17 21:12:35.447: I/Web Console(2142): appcache: checking:23
12-17 21:12:35.447: I/Web Console(2142): appcache: checking:23
12-17 21:12:38.025: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:38.025: I/Web Console(2142): appcache: noupdate:23
(3x)
12-17 21:12:45.322: I/Web Console(2142): appcache: checking:23
12-17 21:12:45.322: I/Web Console(2142): appcache: checking:23
12-17 21:12:45.322: I/Web Console(2142): appcache: checking:23
12-17 21:12:47.345: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:47.345: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:47.345: I/Web Console(2142): appcache: noupdate:23
was:
Expected Behavior:
1) AppCache is only checked *once* per App startup.
Observed Behavior:
1) AppCache is checked *multiple times* on random per App Startup.
Steps to repeat:
1) console.log() AppCache's checking event.
2) Start App, see checking once.
3) navigator.app.exitApp(), then re-launches App.
4) First relaunch leads to a single checking still.
5) Repeat the relaunch a few times.
6) Then you'll see sometimes it's a double, triple, or quadruple (but never 5x).
7) Only a KILL from task switcher will reset these accumulations.
Code Snippet:
document.addEventListener('deviceready', function(){
function logEvent(event) {
console.log('appcache: '+event.type);
}
window.applicationCache.addEventListener('checking', logEvent, false);
window.applicationCache.addEventListener('noupdate', logEvent, false);
window.applicationCache.addEventListener('downloading', logEvent, false);
window.applicationCache.addEventListener('progress', logEvent, false);
window.applicationCache.addEventListener('cached', logEvent, false);
window.applicationCache.addEventListener('updateready', logEvent, false);
window.applicationCache.addEventListener('obsolete', logEvent, false);
window.applicationCache.addEventListener('error', logEvent, false);
document.addEventListener('backbutton', function(){
navigator.app.exitApp();
}, false);
}, false);
LogCat pattern:
(1x)
12-17 21:11:13.470: I/Web Console(2142): appcache: checking:23
12-17 21:11:13.478: I/Web Console(2142): appcache: noupdate:23
(1x updateready)
12-17 21:11:47.775: I/Web Console(2142): appcache: checking:23
12-17 21:11:50.072: I/Web Console(2142): appcache: downloading:23
12-17 21:11:50.072: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.166: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.197:
[jira] [Updated] (CB-5664) AppCache's checking event fired more than once per App startup.
[
https://issues.apache.org/jira/browse/CB-5664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Godric Kwok updated CB-5664:
Description:
Expected Behavior:
1) AppCache is checked only *once* per App startup.
Observed Behavior:
1) AppCache is checked *multiple times* randomly per App startup.
Steps to repeat:
1) console.log() AppCache's checking event.
2) Start App, see checking once.
3) navigator.app.exitApp(), then re-launches App.
4) First relaunch leads to a single checking still.
5) Repeat the relaunch a few times.
6) Then you'll see sometimes it's a double, a triple, or a quadruple (but never
5x).
7) Only a KILL from task switcher will reset these accumulations.
Code Snippet:
document.addEventListener('deviceready', function(){
function logEvent(event) {
console.log('appcache: '+event.type);
}
window.applicationCache.addEventListener('checking', logEvent, false);
window.applicationCache.addEventListener('noupdate', logEvent, false);
window.applicationCache.addEventListener('downloading', logEvent, false);
window.applicationCache.addEventListener('progress', logEvent, false);
window.applicationCache.addEventListener('cached', logEvent, false);
window.applicationCache.addEventListener('updateready', logEvent, false);
window.applicationCache.addEventListener('obsolete', logEvent, false);
window.applicationCache.addEventListener('error', logEvent, false);
document.addEventListener('backbutton', function(){
navigator.app.exitApp();
}, false);
}, false);
LogCat pattern:
(1x)
12-17 21:11:13.470: I/Web Console(2142): appcache: checking:23
12-17 21:11:13.478: I/Web Console(2142): appcache: noupdate:23
(1x updateready)
12-17 21:11:47.775: I/Web Console(2142): appcache: checking:23
12-17 21:11:50.072: I/Web Console(2142): appcache: downloading:23
12-17 21:11:50.072: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.166: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.197: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.697: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.697: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.697: I/Web Console(2142): appcache: updateready:23
12-17 21:11:50.697: I/Web Console(2142): appcache: updateready:23
(2x)
12-17 21:12:27.283: I/Web Console(2142): appcache: checking:23
12-17 21:12:27.283: I/Web Console(2142): appcache: checking:23
12-17 21:12:29.759: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:29.759: I/Web Console(2142): appcache: noupdate:23
(2x)
12-17 21:12:35.447: I/Web Console(2142): appcache: checking:23
12-17 21:12:35.447: I/Web Console(2142): appcache: checking:23
12-17 21:12:38.025: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:38.025: I/Web Console(2142): appcache: noupdate:23
(3x)
12-17 21:12:45.322: I/Web Console(2142): appcache: checking:23
12-17 21:12:45.322: I/Web Console(2142): appcache: checking:23
12-17 21:12:45.322: I/Web Console(2142): appcache: checking:23
12-17 21:12:47.345: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:47.345: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:47.345: I/Web Console(2142): appcache: noupdate:23
was:
Expected Behavior:
1) AppCache is checked only *once* per App startup.
Observed Behavior:
1) AppCache is checked *multiple times* randomly per App startup.
Steps to repeat:
1) console.log() AppCache's checking event.
2) Start App, see checking once.
3) navigator.app.exitApp(), then re-launches App.
4) First relaunch leads to a single checking still.
5) Repeat the relaunch a few times.
6) Then you'll see sometimes it's a double, triple, or quadruple (but never 5x).
7) Only a KILL from task switcher will reset these accumulations.
Code Snippet:
document.addEventListener('deviceready', function(){
function logEvent(event) {
console.log('appcache: '+event.type);
}
window.applicationCache.addEventListener('checking', logEvent, false);
window.applicationCache.addEventListener('noupdate', logEvent, false);
window.applicationCache.addEventListener('downloading', logEvent, false);
window.applicationCache.addEventListener('progress', logEvent, false);
window.applicationCache.addEventListener('cached', logEvent, false);
window.applicationCache.addEventListener('updateready', logEvent, false);
window.applicationCache.addEventListener('obsolete', logEvent, false);
window.applicationCache.addEventListener('error', logEvent, false);
document.addEventListener('backbutton', function(){
navigator.app.exitApp();
}, false);
}, false);
LogCat pattern:
(1x)
12-17 21:11:13.470: I/Web Console(2142): appcache: checking:23
12-17 21:11:13.478: I/Web Console(2142): appcache: noupdate:23
(1x updateready)
12-17 21:11:47.775: I/Web Console(2142): appcache: checking:23
12-17 21:11:50.072: I/Web Console(2142): appcache: downloading:23
12-17 21:11:50.072: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.166: I/Web Console(2142): appcache: progress:23
12-17
[jira] [Updated] (CB-5664) AppCache's checking event fired more than once per App startup.
[
https://issues.apache.org/jira/browse/CB-5664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Godric Kwok updated CB-5664:
Description:
Expected Behavior:
1) AppCache is checked only *once* per App startup.
Observed Behavior:
1) AppCache is checked *multiple times* randomly per App startup.
Steps to repeat:
1) console.log() AppCache's checking event.
2) Start App, see checking once.
3) navigator.app.exitApp(), then re-launches App.
4) First relaunch leads to a single checking still.
5) Repeat the relaunch a few times.
6) Then you'll see sometimes it's a double, triple, or quadruple (but never 5x).
7) Only a KILL from task switcher will reset these accumulations.
Code Snippet:
document.addEventListener('deviceready', function(){
function logEvent(event) {
console.log('appcache: '+event.type);
}
window.applicationCache.addEventListener('checking', logEvent, false);
window.applicationCache.addEventListener('noupdate', logEvent, false);
window.applicationCache.addEventListener('downloading', logEvent, false);
window.applicationCache.addEventListener('progress', logEvent, false);
window.applicationCache.addEventListener('cached', logEvent, false);
window.applicationCache.addEventListener('updateready', logEvent, false);
window.applicationCache.addEventListener('obsolete', logEvent, false);
window.applicationCache.addEventListener('error', logEvent, false);
document.addEventListener('backbutton', function(){
navigator.app.exitApp();
}, false);
}, false);
LogCat pattern:
(1x)
12-17 21:11:13.470: I/Web Console(2142): appcache: checking:23
12-17 21:11:13.478: I/Web Console(2142): appcache: noupdate:23
(1x updateready)
12-17 21:11:47.775: I/Web Console(2142): appcache: checking:23
12-17 21:11:50.072: I/Web Console(2142): appcache: downloading:23
12-17 21:11:50.072: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.166: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.197: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.697: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.697: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.697: I/Web Console(2142): appcache: updateready:23
12-17 21:11:50.697: I/Web Console(2142): appcache: updateready:23
(2x)
12-17 21:12:27.283: I/Web Console(2142): appcache: checking:23
12-17 21:12:27.283: I/Web Console(2142): appcache: checking:23
12-17 21:12:29.759: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:29.759: I/Web Console(2142): appcache: noupdate:23
(2x)
12-17 21:12:35.447: I/Web Console(2142): appcache: checking:23
12-17 21:12:35.447: I/Web Console(2142): appcache: checking:23
12-17 21:12:38.025: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:38.025: I/Web Console(2142): appcache: noupdate:23
(3x)
12-17 21:12:45.322: I/Web Console(2142): appcache: checking:23
12-17 21:12:45.322: I/Web Console(2142): appcache: checking:23
12-17 21:12:45.322: I/Web Console(2142): appcache: checking:23
12-17 21:12:47.345: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:47.345: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:47.345: I/Web Console(2142): appcache: noupdate:23
was:
Expected Behavior:
1) AppCache is checked only *once* per App startup.
Observed Behavior:
1) AppCache is checked *multiple times* on random per App Startup.
Steps to repeat:
1) console.log() AppCache's checking event.
2) Start App, see checking once.
3) navigator.app.exitApp(), then re-launches App.
4) First relaunch leads to a single checking still.
5) Repeat the relaunch a few times.
6) Then you'll see sometimes it's a double, triple, or quadruple (but never 5x).
7) Only a KILL from task switcher will reset these accumulations.
Code Snippet:
document.addEventListener('deviceready', function(){
function logEvent(event) {
console.log('appcache: '+event.type);
}
window.applicationCache.addEventListener('checking', logEvent, false);
window.applicationCache.addEventListener('noupdate', logEvent, false);
window.applicationCache.addEventListener('downloading', logEvent, false);
window.applicationCache.addEventListener('progress', logEvent, false);
window.applicationCache.addEventListener('cached', logEvent, false);
window.applicationCache.addEventListener('updateready', logEvent, false);
window.applicationCache.addEventListener('obsolete', logEvent, false);
window.applicationCache.addEventListener('error', logEvent, false);
document.addEventListener('backbutton', function(){
navigator.app.exitApp();
}, false);
}, false);
LogCat pattern:
(1x)
12-17 21:11:13.470: I/Web Console(2142): appcache: checking:23
12-17 21:11:13.478: I/Web Console(2142): appcache: noupdate:23
(1x updateready)
12-17 21:11:47.775: I/Web Console(2142): appcache: checking:23
12-17 21:11:50.072: I/Web Console(2142): appcache: downloading:23
12-17 21:11:50.072: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.166: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.197:
[jira] [Updated] (CB-5664) AppCache's checking event fired more than once per App startup.
[
https://issues.apache.org/jira/browse/CB-5664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Godric Kwok updated CB-5664:
Description:
Expected Behavior:
1) AppCache is checked only *once* per App startup.
Observed Behavior:
1) AppCache is checked *multiple times* randomly per App startup.
Steps to repeat:
1) console.log() AppCache's checking event.
2) Start App, see checking once.
3) *navigator.app.exitApp()*, then re-launches App.
4) First relaunch leads to a single checking still.
5) Repeat the relaunch *a few times*.
6) Then you'll see sometimes it's a double, a triple, or a quadruple (but never
5x).
7) Only a *KILL* from task switcher will reset these accumulations.
Unwanted Results:
1) Multiple checking triggers multiple subsequent events (download,
updateready, etc...) that renders the App slow.
2) Multiple updateready triggers multiple swapCache()/reload() that renders
the App appeared broken.
Code Snippet:
document.addEventListener('deviceready', function(){
function logEvent(event) {
console.log('appcache: '+event.type);
}
window.applicationCache.addEventListener('checking', logEvent, false);
window.applicationCache.addEventListener('noupdate', logEvent, false);
window.applicationCache.addEventListener('downloading', logEvent, false);
window.applicationCache.addEventListener('progress', logEvent, false);
window.applicationCache.addEventListener('cached', logEvent, false);
window.applicationCache.addEventListener('updateready', logEvent, false);
window.applicationCache.addEventListener('obsolete', logEvent, false);
window.applicationCache.addEventListener('error', logEvent, false);
document.addEventListener('backbutton', function(){
navigator.app.exitApp();
}, false);
}, false);
LogCat pattern:
*(1x)*
12-17 21:11:13.470: I/Web Console(2142): appcache: checking:23
12-17 21:11:13.478: I/Web Console(2142): appcache: noupdate:23
*(1x updateready)*
12-17 21:11:47.775: I/Web Console(2142): appcache: checking:23
12-17 21:11:50.072: I/Web Console(2142): appcache: downloading:23
12-17 21:11:50.072: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.166: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.197: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.697: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.697: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.697: I/Web Console(2142): appcache: updateready:23
12-17 21:11:50.697: I/Web Console(2142): appcache: updateready:23
*(2x)*
12-17 21:12:27.283: I/Web Console(2142): appcache: checking:23
12-17 21:12:27.283: I/Web Console(2142): appcache: checking:23
12-17 21:12:29.759: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:29.759: I/Web Console(2142): appcache: noupdate:23
*(2x)*
12-17 21:12:35.447: I/Web Console(2142): appcache: checking:23
12-17 21:12:35.447: I/Web Console(2142): appcache: checking:23
12-17 21:12:38.025: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:38.025: I/Web Console(2142): appcache: noupdate:23
*(3x)*
12-17 21:12:45.322: I/Web Console(2142): appcache: checking:23
12-17 21:12:45.322: I/Web Console(2142): appcache: checking:23
12-17 21:12:45.322: I/Web Console(2142): appcache: checking:23
12-17 21:12:47.345: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:47.345: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:47.345: I/Web Console(2142): appcache: noupdate:23
was:
Expected Behavior:
1) AppCache is checked only *once* per App startup.
Observed Behavior:
1) AppCache is checked *multiple times* randomly per App startup.
Steps to repeat:
1) console.log() AppCache's checking event.
2) Start App, see checking once.
3) navigator.app.exitApp(), then re-launches App.
4) First relaunch leads to a single checking still.
5) Repeat the relaunch a few times.
6) Then you'll see sometimes it's a double, a triple, or a quadruple (but never
5x).
7) Only a KILL from task switcher will reset these accumulations.
Unwanted Results:
1) Multiple checking triggers multiple subsequent events (download,
updateready, etc...) that renders the App slow.
2) Multiple updateready triggers multiple swapCache()/reload() that renders
the App appeared broken.
Code Snippet:
document.addEventListener('deviceready', function(){
function logEvent(event) {
console.log('appcache: '+event.type);
}
window.applicationCache.addEventListener('checking', logEvent, false);
window.applicationCache.addEventListener('noupdate', logEvent, false);
window.applicationCache.addEventListener('downloading', logEvent, false);
window.applicationCache.addEventListener('progress', logEvent, false);
window.applicationCache.addEventListener('cached', logEvent, false);
window.applicationCache.addEventListener('updateready', logEvent, false);
window.applicationCache.addEventListener('obsolete', logEvent, false);
window.applicationCache.addEventListener('error', logEvent, false);
[jira] [Updated] (CB-5664) AppCache's checking event fired more than once per App startup.
[
https://issues.apache.org/jira/browse/CB-5664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Godric Kwok updated CB-5664:
Description:
_Expected Behavior:_
1) AppCache is checked only *once* per App startup.
Observed Behavior:
1) AppCache is checked *multiple times* randomly per App startup.
Steps to repeat:
1) console.log() AppCache's checking event.
2) Start App, see checking once.
3) *navigator.app.exitApp()*, then re-launches App.
4) First relaunch leads to a single checking still.
5) Repeat the relaunch *a few times*.
6) Then you'll see sometimes it's a double, a triple, or a quadruple (but never
5x).
7) Only a *KILL* from task switcher will reset these accumulations.
Unwanted Results:
1) Multiple checking triggers multiple subsequent events (download,
updateready, etc...) that renders the App slow.
2) Multiple updateready triggers multiple swapCache()/reload() that renders
the App appeared broken.
Code Snippet:
document.addEventListener('deviceready', function(){
function logEvent(event) {
console.log('appcache: '+event.type);
}
window.applicationCache.addEventListener('checking', logEvent, false);
window.applicationCache.addEventListener('noupdate', logEvent, false);
window.applicationCache.addEventListener('downloading', logEvent, false);
window.applicationCache.addEventListener('progress', logEvent, false);
window.applicationCache.addEventListener('cached', logEvent, false);
window.applicationCache.addEventListener('updateready', logEvent, false);
window.applicationCache.addEventListener('obsolete', logEvent, false);
window.applicationCache.addEventListener('error', logEvent, false);
document.addEventListener('backbutton', function(){
navigator.app.exitApp();
}, false);
}, false);
LogCat pattern:
*(1x)*
12-17 21:11:13.470: I/Web Console(2142): appcache: checking:23
12-17 21:11:13.478: I/Web Console(2142): appcache: noupdate:23
*(1x updateready)*
12-17 21:11:47.775: I/Web Console(2142): appcache: checking:23
12-17 21:11:50.072: I/Web Console(2142): appcache: downloading:23
12-17 21:11:50.072: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.166: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.197: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.697: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.697: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.697: I/Web Console(2142): appcache: updateready:23
12-17 21:11:50.697: I/Web Console(2142): appcache: updateready:23
*(2x)*
12-17 21:12:27.283: I/Web Console(2142): appcache: checking:23
12-17 21:12:27.283: I/Web Console(2142): appcache: checking:23
12-17 21:12:29.759: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:29.759: I/Web Console(2142): appcache: noupdate:23
*(2x)*
12-17 21:12:35.447: I/Web Console(2142): appcache: checking:23
12-17 21:12:35.447: I/Web Console(2142): appcache: checking:23
12-17 21:12:38.025: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:38.025: I/Web Console(2142): appcache: noupdate:23
*(3x)*
12-17 21:12:45.322: I/Web Console(2142): appcache: checking:23
12-17 21:12:45.322: I/Web Console(2142): appcache: checking:23
12-17 21:12:45.322: I/Web Console(2142): appcache: checking:23
12-17 21:12:47.345: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:47.345: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:47.345: I/Web Console(2142): appcache: noupdate:23
was:
Expected Behavior:
1) AppCache is checked only *once* per App startup.
Observed Behavior:
1) AppCache is checked *multiple times* randomly per App startup.
Steps to repeat:
1) console.log() AppCache's checking event.
2) Start App, see checking once.
3) *navigator.app.exitApp()*, then re-launches App.
4) First relaunch leads to a single checking still.
5) Repeat the relaunch *a few times*.
6) Then you'll see sometimes it's a double, a triple, or a quadruple (but never
5x).
7) Only a *KILL* from task switcher will reset these accumulations.
Unwanted Results:
1) Multiple checking triggers multiple subsequent events (download,
updateready, etc...) that renders the App slow.
2) Multiple updateready triggers multiple swapCache()/reload() that renders
the App appeared broken.
Code Snippet:
document.addEventListener('deviceready', function(){
function logEvent(event) {
console.log('appcache: '+event.type);
}
window.applicationCache.addEventListener('checking', logEvent, false);
window.applicationCache.addEventListener('noupdate', logEvent, false);
window.applicationCache.addEventListener('downloading', logEvent, false);
window.applicationCache.addEventListener('progress', logEvent, false);
window.applicationCache.addEventListener('cached', logEvent, false);
window.applicationCache.addEventListener('updateready', logEvent, false);
window.applicationCache.addEventListener('obsolete', logEvent, false);
window.applicationCache.addEventListener('error', logEvent, false);
[jira] [Updated] (CB-5664) AppCache's checking event fired more than once per App startup.
[
https://issues.apache.org/jira/browse/CB-5664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Godric Kwok updated CB-5664:
Description:
+Expected Behavior:+
1) AppCache is checked only *once* per App startup.
Observed Behavior:
1) AppCache is checked *multiple times* randomly per App startup.
Steps to repeat:
1) console.log() AppCache's checking event.
2) Start App, see checking once.
3) *navigator.app.exitApp()*, then re-launches App.
4) First relaunch leads to a single checking still.
5) Repeat the relaunch *a few times*.
6) Then you'll see sometimes it's a double, a triple, or a quadruple (but never
5x).
7) Only a *KILL* from task switcher will reset these accumulations.
Unwanted Results:
1) Multiple checking triggers multiple subsequent events (download,
updateready, etc...) that renders the App slow.
2) Multiple updateready triggers multiple swapCache()/reload() that renders
the App appeared broken.
Code Snippet:
document.addEventListener('deviceready', function(){
function logEvent(event) {
console.log('appcache: '+event.type);
}
window.applicationCache.addEventListener('checking', logEvent, false);
window.applicationCache.addEventListener('noupdate', logEvent, false);
window.applicationCache.addEventListener('downloading', logEvent, false);
window.applicationCache.addEventListener('progress', logEvent, false);
window.applicationCache.addEventListener('cached', logEvent, false);
window.applicationCache.addEventListener('updateready', logEvent, false);
window.applicationCache.addEventListener('obsolete', logEvent, false);
window.applicationCache.addEventListener('error', logEvent, false);
document.addEventListener('backbutton', function(){
navigator.app.exitApp();
}, false);
}, false);
LogCat pattern:
*(1x)*
12-17 21:11:13.470: I/Web Console(2142): appcache: checking:23
12-17 21:11:13.478: I/Web Console(2142): appcache: noupdate:23
*(1x updateready)*
12-17 21:11:47.775: I/Web Console(2142): appcache: checking:23
12-17 21:11:50.072: I/Web Console(2142): appcache: downloading:23
12-17 21:11:50.072: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.166: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.197: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.697: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.697: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.697: I/Web Console(2142): appcache: updateready:23
12-17 21:11:50.697: I/Web Console(2142): appcache: updateready:23
*(2x)*
12-17 21:12:27.283: I/Web Console(2142): appcache: checking:23
12-17 21:12:27.283: I/Web Console(2142): appcache: checking:23
12-17 21:12:29.759: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:29.759: I/Web Console(2142): appcache: noupdate:23
*(2x)*
12-17 21:12:35.447: I/Web Console(2142): appcache: checking:23
12-17 21:12:35.447: I/Web Console(2142): appcache: checking:23
12-17 21:12:38.025: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:38.025: I/Web Console(2142): appcache: noupdate:23
*(3x)*
12-17 21:12:45.322: I/Web Console(2142): appcache: checking:23
12-17 21:12:45.322: I/Web Console(2142): appcache: checking:23
12-17 21:12:45.322: I/Web Console(2142): appcache: checking:23
12-17 21:12:47.345: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:47.345: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:47.345: I/Web Console(2142): appcache: noupdate:23
was:
_Expected Behavior:_
1) AppCache is checked only *once* per App startup.
Observed Behavior:
1) AppCache is checked *multiple times* randomly per App startup.
Steps to repeat:
1) console.log() AppCache's checking event.
2) Start App, see checking once.
3) *navigator.app.exitApp()*, then re-launches App.
4) First relaunch leads to a single checking still.
5) Repeat the relaunch *a few times*.
6) Then you'll see sometimes it's a double, a triple, or a quadruple (but never
5x).
7) Only a *KILL* from task switcher will reset these accumulations.
Unwanted Results:
1) Multiple checking triggers multiple subsequent events (download,
updateready, etc...) that renders the App slow.
2) Multiple updateready triggers multiple swapCache()/reload() that renders
the App appeared broken.
Code Snippet:
document.addEventListener('deviceready', function(){
function logEvent(event) {
console.log('appcache: '+event.type);
}
window.applicationCache.addEventListener('checking', logEvent, false);
window.applicationCache.addEventListener('noupdate', logEvent, false);
window.applicationCache.addEventListener('downloading', logEvent, false);
window.applicationCache.addEventListener('progress', logEvent, false);
window.applicationCache.addEventListener('cached', logEvent, false);
window.applicationCache.addEventListener('updateready', logEvent, false);
window.applicationCache.addEventListener('obsolete', logEvent, false);
window.applicationCache.addEventListener('error', logEvent, false);
[jira] [Updated] (CB-5664) AppCache's checking event fired more than once per App startup.
[
https://issues.apache.org/jira/browse/CB-5664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Godric Kwok updated CB-5664:
Description:
+Expected Behavior:+
1) AppCache is checked only *once* per App startup.
+Observed Behavior:+
1) AppCache is checked *multiple times* randomly per App startup.
+Steps to repeat:+
1) console.log() AppCache's checking event.
2) Start App, see checking once.
3) *navigator.app.exitApp()*, then re-launches App.
4) First relaunch leads to a single checking still.
5) Repeat the relaunch *a few times*.
6) Then you'll see sometimes it's a double, a triple, or a quadruple (but never
5x).
7) Only a *KILL* from task switcher will reset these accumulations.
+Unwanted Results:+
1) Multiple checking triggers multiple subsequent events (download,
updateready, etc...) that renders the App slow.
2) Multiple updateready triggers multiple swapCache()/reload() that renders
the App appeared broken.
+Code Snippet:+
document.addEventListener('deviceready', function(){
function logEvent(event) {
console.log('appcache: '+event.type);
}
window.applicationCache.addEventListener('checking', logEvent, false);
window.applicationCache.addEventListener('noupdate', logEvent, false);
window.applicationCache.addEventListener('downloading', logEvent, false);
window.applicationCache.addEventListener('progress', logEvent, false);
window.applicationCache.addEventListener('cached', logEvent, false);
window.applicationCache.addEventListener('updateready', logEvent, false);
window.applicationCache.addEventListener('obsolete', logEvent, false);
window.applicationCache.addEventListener('error', logEvent, false);
document.addEventListener('backbutton', function(){
navigator.app.exitApp();
}, false);
}, false);
+LogCat pattern:+
*(1x)*
12-17 21:11:13.470: I/Web Console(2142): appcache: checking:23
12-17 21:11:13.478: I/Web Console(2142): appcache: noupdate:23
*(1x updateready)*
12-17 21:11:47.775: I/Web Console(2142): appcache: checking:23
12-17 21:11:50.072: I/Web Console(2142): appcache: downloading:23
12-17 21:11:50.072: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.166: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.197: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.697: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.697: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.697: I/Web Console(2142): appcache: updateready:23
12-17 21:11:50.697: I/Web Console(2142): appcache: updateready:23
*(2x)*
12-17 21:12:27.283: I/Web Console(2142): appcache: checking:23
12-17 21:12:27.283: I/Web Console(2142): appcache: checking:23
12-17 21:12:29.759: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:29.759: I/Web Console(2142): appcache: noupdate:23
*(2x)*
12-17 21:12:35.447: I/Web Console(2142): appcache: checking:23
12-17 21:12:35.447: I/Web Console(2142): appcache: checking:23
12-17 21:12:38.025: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:38.025: I/Web Console(2142): appcache: noupdate:23
*(3x)*
12-17 21:12:45.322: I/Web Console(2142): appcache: checking:23
12-17 21:12:45.322: I/Web Console(2142): appcache: checking:23
12-17 21:12:45.322: I/Web Console(2142): appcache: checking:23
12-17 21:12:47.345: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:47.345: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:47.345: I/Web Console(2142): appcache: noupdate:23
was:
+Expected Behavior:+
1) AppCache is checked only *once* per App startup.
Observed Behavior:
1) AppCache is checked *multiple times* randomly per App startup.
Steps to repeat:
1) console.log() AppCache's checking event.
2) Start App, see checking once.
3) *navigator.app.exitApp()*, then re-launches App.
4) First relaunch leads to a single checking still.
5) Repeat the relaunch *a few times*.
6) Then you'll see sometimes it's a double, a triple, or a quadruple (but never
5x).
7) Only a *KILL* from task switcher will reset these accumulations.
Unwanted Results:
1) Multiple checking triggers multiple subsequent events (download,
updateready, etc...) that renders the App slow.
2) Multiple updateready triggers multiple swapCache()/reload() that renders
the App appeared broken.
Code Snippet:
document.addEventListener('deviceready', function(){
function logEvent(event) {
console.log('appcache: '+event.type);
}
window.applicationCache.addEventListener('checking', logEvent, false);
window.applicationCache.addEventListener('noupdate', logEvent, false);
window.applicationCache.addEventListener('downloading', logEvent, false);
window.applicationCache.addEventListener('progress', logEvent, false);
window.applicationCache.addEventListener('cached', logEvent, false);
window.applicationCache.addEventListener('updateready', logEvent, false);
window.applicationCache.addEventListener('obsolete', logEvent, false);
window.applicationCache.addEventListener('error', logEvent, false);
[jira] [Updated] (CB-5664) AppCache's checking event fired more than once per App startup.
[
https://issues.apache.org/jira/browse/CB-5664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Godric Kwok updated CB-5664:
Description:
+Expected Behavior:+
1) AppCache is checked only *once* per App startup.
+Observed Behavior:+
1) AppCache is checked *multiple times* randomly per App startup.
+Steps to repeat:+
1) console.log() AppCache's checking event.
2) Start App, see checking once.
3) *navigator.app.exitApp()*, then re-launches App.
4) First relaunch leads to a single checking still.
5) Repeat the relaunch *a few times*.
6) Then you'll see sometimes it's a double, a triple, or a quadruple (but never
5x).
7) Only a *KILL* from task switcher will reset these accumulations.
+Unwanted Results:+
1) Multiple checking triggers multiple subsequent events (download,
updateready, etc...) that renders the App slow.
2) Multiple updateready triggers multiple swapCache()/reload() that renders
the App appeared broken.
+Code Snippet:+
document.addEventListener('deviceready', function(){
function logEvent(event) {
console.log('appcache: '+event.type);
}
window.applicationCache.addEventListener('checking', logEvent, false);
window.applicationCache.addEventListener('noupdate', logEvent, false);
window.applicationCache.addEventListener('downloading', logEvent, false);
window.applicationCache.addEventListener('progress', logEvent, false);
window.applicationCache.addEventListener('cached', logEvent, false);
window.applicationCache.addEventListener('updateready', logEvent, false);
window.applicationCache.addEventListener('obsolete', logEvent, false);
window.applicationCache.addEventListener('error', logEvent, false);
document.addEventListener('backbutton', function(){
navigator.app.exitApp();
}, false);
}, false);
+LogCat pattern:+
*(1x)*
12-17 21:11:13.470: I/Web Console(2142): appcache: checking:23
12-17 21:11:13.478: I/Web Console(2142): appcache: noupdate:23
*(1x, but _double_ updateready)*
12-17 21:11:47.775: I/Web Console(2142): appcache: checking:23
12-17 21:11:50.072: I/Web Console(2142): appcache: downloading:23
12-17 21:11:50.072: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.166: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.197: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.697: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.697: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.697: I/Web Console(2142): appcache: updateready:23
12-17 21:11:50.697: I/Web Console(2142): appcache: updateready:23
*(2x)*
12-17 21:12:27.283: I/Web Console(2142): appcache: checking:23
12-17 21:12:27.283: I/Web Console(2142): appcache: checking:23
12-17 21:12:29.759: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:29.759: I/Web Console(2142): appcache: noupdate:23
*(2x)*
12-17 21:12:35.447: I/Web Console(2142): appcache: checking:23
12-17 21:12:35.447: I/Web Console(2142): appcache: checking:23
12-17 21:12:38.025: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:38.025: I/Web Console(2142): appcache: noupdate:23
*(3x)*
12-17 21:12:45.322: I/Web Console(2142): appcache: checking:23
12-17 21:12:45.322: I/Web Console(2142): appcache: checking:23
12-17 21:12:45.322: I/Web Console(2142): appcache: checking:23
12-17 21:12:47.345: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:47.345: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:47.345: I/Web Console(2142): appcache: noupdate:23
was:
+Expected Behavior:+
1) AppCache is checked only *once* per App startup.
+Observed Behavior:+
1) AppCache is checked *multiple times* randomly per App startup.
+Steps to repeat:+
1) console.log() AppCache's checking event.
2) Start App, see checking once.
3) *navigator.app.exitApp()*, then re-launches App.
4) First relaunch leads to a single checking still.
5) Repeat the relaunch *a few times*.
6) Then you'll see sometimes it's a double, a triple, or a quadruple (but never
5x).
7) Only a *KILL* from task switcher will reset these accumulations.
+Unwanted Results:+
1) Multiple checking triggers multiple subsequent events (download,
updateready, etc...) that renders the App slow.
2) Multiple updateready triggers multiple swapCache()/reload() that renders
the App appeared broken.
+Code Snippet:+
document.addEventListener('deviceready', function(){
function logEvent(event) {
console.log('appcache: '+event.type);
}
window.applicationCache.addEventListener('checking', logEvent, false);
window.applicationCache.addEventListener('noupdate', logEvent, false);
window.applicationCache.addEventListener('downloading', logEvent, false);
window.applicationCache.addEventListener('progress', logEvent, false);
window.applicationCache.addEventListener('cached', logEvent, false);
window.applicationCache.addEventListener('updateready', logEvent, false);
window.applicationCache.addEventListener('obsolete', logEvent, false);
window.applicationCache.addEventListener('error', logEvent,
[jira] [Issue Comment Deleted] (CB-5660) [BlackBerry10] init.bat fails when parentheses exist within PATH
[ https://issues.apache.org/jira/browse/CB-5660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Soref updated CB-5660: --- Comment: was deleted (was: https://issues.apache.org/jira/browse/CB-5660) [BlackBerry10] init.bat fails when parentheses exist within PATH Key: CB-5660 URL: https://issues.apache.org/jira/browse/CB-5660 Project: Apache Cordova Issue Type: Bug Components: BlackBerry Affects Versions: 3.3.0 Reporter: Bryan Higgins Assignee: Josh Soref Priority: Blocker CB-5443 introduced a change to init.bat which breaks the platform for some Windows users. Specifically, if they have (x86) somewhere in their path it will fail to parse the file. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CB-5604) [BlackBerry10] Improve performance of exec bridge
[ https://issues.apache.org/jira/browse/CB-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13850616#comment-13850616 ] ASF subversion and git services commented on CB-5604: - Commit a320b79325e376c38bfbee0cf80aec2668d2 in branch refs/heads/master from Genevieve Mak [ https://git-wip-us.apache.org/repos/asf?p=cordova-js.git;h=a320b79 ] CB-5604 [BlackBerry10] Switch to async XHR for exec bridge [BlackBerry10] Improve performance of exec bridge - Key: CB-5604 URL: https://issues.apache.org/jira/browse/CB-5604 Project: Apache Cordova Issue Type: Improvement Components: BlackBerry Affects Versions: 3.3.0 Reporter: Bryan Higgins Assignee: Bryan Higgins Fix For: 3.4.0 The sync XHR call blocks the client web view, resulting in poor performance. On devices prior to 10.1, the combination of async XHR and networkResourceHandler proved too unreliable and ended up blocking anyway. Since this has been fixed for the last two major OTA updates, I would like to switch back to async. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Resolved] (CB-5604) [BlackBerry10] Improve performance of exec bridge
[ https://issues.apache.org/jira/browse/CB-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Higgins resolved CB-5604. --- Resolution: Fixed [BlackBerry10] Improve performance of exec bridge - Key: CB-5604 URL: https://issues.apache.org/jira/browse/CB-5604 Project: Apache Cordova Issue Type: Improvement Components: BlackBerry Affects Versions: 3.3.0 Reporter: Bryan Higgins Assignee: Bryan Higgins Fix For: 3.4.0 The sync XHR call blocks the client web view, resulting in poor performance. On devices prior to 10.1, the combination of async XHR and networkResourceHandler proved too unreliable and ended up blocking anyway. Since this has been fixed for the last two major OTA updates, I would like to switch back to async. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (CB-5648) cordova platform add android fails with Package name must look like: com.company.Name
[ https://issues.apache.org/jira/browse/CB-5648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Grieve updated CB-5648: -- Component/s: CLI cordova platform add android fails with Package name must look like: com.company.Name - Key: CB-5648 URL: https://issues.apache.org/jira/browse/CB-5648 Project: Apache Cordova Issue Type: Bug Components: Android, CLI Affects Versions: 3.1.0, 3.3.0 Environment: OS X 18.3 Reporter: Evan Rowley Priority: Blocker Labels: newbie Fix For: 3.3.0 I was making my way through the PhoneGap 3 Beginner’s Guide by Giorigo Natili when I ran into the following error. Chapter 03 is on creating the HelloWorld app. The steps that got me to the error are: Step 1 cordova create ~/the/path/to/src/ch03 HelloWorld Step 2 cd ~/the/path/to/src/ch03 Step 3 cordova platform add android ^ This command doesn’t seem to work. What I get from running this is: Creating android project... /usr/local/lib/node_modules/cordova/node_modules/q/q.js:126 throw e; ^ Error: An error occured during creation of android sub-project. /Users/evanrowley/.cordova/lib/android/cordova/3.3.0/bin/node_modules/q/q.js:126 throw e; ^ Package name must look like: com.company.Name at /usr/local/lib/node_modules/cordova/src/platform.js:244:30 at ChildProcess.exithandler (child_process.js:641:7) at ChildProcess.EventEmitter.emit (events.js:98:17) at maybeClose (child_process.js:735:16) at Process.ChildProcess._handle.onexit (child_process.js:802:5) I would really like to debug this but I don’t have the slightest clue as to how my environment could be verified and/or how a node application can be debugged. I took a look at q.js:126 and platform.js:244 and both basically tie into some kind of exception thingy. It would be really neat if I could run this in a ‘debug mode’ and see what all the variables are at certain breakpoints. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (CB-5648) cordova platform add android fails with Package name must look like: com.company.Name
[ https://issues.apache.org/jira/browse/CB-5648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Grieve updated CB-5648: -- Priority: Minor (was: Blocker) cordova platform add android fails with Package name must look like: com.company.Name - Key: CB-5648 URL: https://issues.apache.org/jira/browse/CB-5648 Project: Apache Cordova Issue Type: Bug Components: Android, CLI Affects Versions: 3.1.0, 3.3.0 Environment: OS X 18.3 Reporter: Evan Rowley Priority: Minor Labels: newbie Fix For: 3.3.0 I was making my way through the PhoneGap 3 Beginner’s Guide by Giorigo Natili when I ran into the following error. Chapter 03 is on creating the HelloWorld app. The steps that got me to the error are: Step 1 cordova create ~/the/path/to/src/ch03 HelloWorld Step 2 cd ~/the/path/to/src/ch03 Step 3 cordova platform add android ^ This command doesn’t seem to work. What I get from running this is: Creating android project... /usr/local/lib/node_modules/cordova/node_modules/q/q.js:126 throw e; ^ Error: An error occured during creation of android sub-project. /Users/evanrowley/.cordova/lib/android/cordova/3.3.0/bin/node_modules/q/q.js:126 throw e; ^ Package name must look like: com.company.Name at /usr/local/lib/node_modules/cordova/src/platform.js:244:30 at ChildProcess.exithandler (child_process.js:641:7) at ChildProcess.EventEmitter.emit (events.js:98:17) at maybeClose (child_process.js:735:16) at Process.ChildProcess._handle.onexit (child_process.js:802:5) I would really like to debug this but I don’t have the slightest clue as to how my environment could be verified and/or how a node application can be debugged. I took a look at q.js:126 and platform.js:244 and both basically tie into some kind of exception thingy. It would be really neat if I could run this in a ‘debug mode’ and see what all the variables are at certain breakpoints. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Reopened] (CB-5648) cordova platform add android fails with Package name must look like: com.company.Name
[ https://issues.apache.org/jira/browse/CB-5648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Grieve reopened CB-5648: --- I think there actually is supposed to be a default ID. Likely this is a valid bug cordova platform add android fails with Package name must look like: com.company.Name - Key: CB-5648 URL: https://issues.apache.org/jira/browse/CB-5648 Project: Apache Cordova Issue Type: Bug Components: Android, CLI Affects Versions: 3.1.0, 3.3.0 Environment: OS X 18.3 Reporter: Evan Rowley Priority: Blocker Labels: newbie Fix For: 3.3.0 I was making my way through the PhoneGap 3 Beginner’s Guide by Giorigo Natili when I ran into the following error. Chapter 03 is on creating the HelloWorld app. The steps that got me to the error are: Step 1 cordova create ~/the/path/to/src/ch03 HelloWorld Step 2 cd ~/the/path/to/src/ch03 Step 3 cordova platform add android ^ This command doesn’t seem to work. What I get from running this is: Creating android project... /usr/local/lib/node_modules/cordova/node_modules/q/q.js:126 throw e; ^ Error: An error occured during creation of android sub-project. /Users/evanrowley/.cordova/lib/android/cordova/3.3.0/bin/node_modules/q/q.js:126 throw e; ^ Package name must look like: com.company.Name at /usr/local/lib/node_modules/cordova/src/platform.js:244:30 at ChildProcess.exithandler (child_process.js:641:7) at ChildProcess.EventEmitter.emit (events.js:98:17) at maybeClose (child_process.js:735:16) at Process.ChildProcess._handle.onexit (child_process.js:802:5) I would really like to debug this but I don’t have the slightest clue as to how my environment could be verified and/or how a node application can be debugged. I took a look at q.js:126 and platform.js:244 and both basically tie into some kind of exception thingy. It would be really neat if I could run this in a ‘debug mode’ and see what all the variables are at certain breakpoints. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CB-5134) Add location.hash / anchor click bridge mode
[ https://issues.apache.org/jira/browse/CB-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13850683#comment-13850683 ] ASF subversion and git services commented on CB-5134: - Commit 0f28be660c19f0860d1a37ee985e1fd934cae836 in branch refs/heads/master from [~agrieve] [ https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;h=0f28be6 ] CB-5134 Add location.hash based exec() bridge. Add location.hash / anchor click bridge mode Key: CB-5134 URL: https://issues.apache.org/jira/browse/CB-5134 Project: Apache Cordova Issue Type: Bug Components: iOS Reporter: Andrew Grieve Priority: Minor Blog post shows that these methods are faster than what we're doing. http://blog.persistent.info/2013/10/a-faster-uiwebview-communication.html -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CB-5134) Add location.hash / anchor click bridge mode
[ https://issues.apache.org/jira/browse/CB-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13850682#comment-13850682 ] ASF subversion and git services commented on CB-5134: - Commit 2c93179f5d7c72883bda37f559cb6ee701b5763f in branch refs/heads/master from [~agrieve] [ https://git-wip-us.apache.org/repos/asf?p=cordova-js.git;h=2c93179 ] CB-5134 iOS - Add location.hash-based exec bridge. Off by default for now until I can benchmark it. Add location.hash / anchor click bridge mode Key: CB-5134 URL: https://issues.apache.org/jira/browse/CB-5134 Project: Apache Cordova Issue Type: Bug Components: iOS Reporter: Andrew Grieve Priority: Minor Blog post shows that these methods are faster than what we're doing. http://blog.persistent.info/2013/10/a-faster-uiwebview-communication.html -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Created] (CB-5665) Document the need for xcopy on path
Mike Billau created CB-5665: --- Summary: Document the need for xcopy on path Key: CB-5665 URL: https://issues.apache.org/jira/browse/CB-5665 Project: Apache Cordova Issue Type: Bug Components: Android, Docs Environment: Windows Reporter: Mike Billau Priority: Minor Fix For: 3.4.0 On Windows, you need to have xcopy on the path when trying to build Android, otherwise it will fail. I think this maybe started when we switched to q.js See: https://issues.apache.org/jira/browse/CB-4074 and http://stackoverflow.com/questions/20616893/an-error-occured-during-creation-of-android-sub-project/20640450 If it is necessary only when you use the CLI, we can just add a note in the CLI documentation. If it is necessary regardless of which workflow you use, then I think it should be in check_reqs with a log message on the terminal to Make sure xcopy is on your path. It's probably a Windows-specific thing, no? -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CB-5648) cordova platform add android fails with Package name must look like: com.company.Name
[ https://issues.apache.org/jira/browse/CB-5648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13850728#comment-13850728 ] Marcel Kinard commented on CB-5648: --- Aha, you are right, Andrew. In cordova-android/lib/create.js, createProject() has defaults for the dir, package name, and class/activityName. However, bin/create invokes that as: create.createProject(args._[0], args._[1], args._[2], args._[3], args['--shared']).done(); which being positional doesn't account for unspecified args in the middle. So Evan's classname was being interpreted as the package name, and that was failing the pattern-match check. With this code, unspecified args only work when they are at the end of the list, not the middle. But I'm wondering on the appropriateness of default values for the classname, packagename, and dir. Those would only make sense for an internal prototype that never goes to an app store (I'm thinking collisions). And there isn't an easy CLI way to modify them after they've been created. Do we really want to support default values here? Are there use cases I'm missing? cordova platform add android fails with Package name must look like: com.company.Name - Key: CB-5648 URL: https://issues.apache.org/jira/browse/CB-5648 Project: Apache Cordova Issue Type: Bug Components: Android, CLI Affects Versions: 3.1.0, 3.3.0 Environment: OS X 18.3 Reporter: Evan Rowley Priority: Minor Labels: newbie Fix For: 3.3.0 I was making my way through the PhoneGap 3 Beginner’s Guide by Giorigo Natili when I ran into the following error. Chapter 03 is on creating the HelloWorld app. The steps that got me to the error are: Step 1 cordova create ~/the/path/to/src/ch03 HelloWorld Step 2 cd ~/the/path/to/src/ch03 Step 3 cordova platform add android ^ This command doesn’t seem to work. What I get from running this is: Creating android project... /usr/local/lib/node_modules/cordova/node_modules/q/q.js:126 throw e; ^ Error: An error occured during creation of android sub-project. /Users/evanrowley/.cordova/lib/android/cordova/3.3.0/bin/node_modules/q/q.js:126 throw e; ^ Package name must look like: com.company.Name at /usr/local/lib/node_modules/cordova/src/platform.js:244:30 at ChildProcess.exithandler (child_process.js:641:7) at ChildProcess.EventEmitter.emit (events.js:98:17) at maybeClose (child_process.js:735:16) at Process.ChildProcess._handle.onexit (child_process.js:802:5) I would really like to debug this but I don’t have the slightest clue as to how my environment could be verified and/or how a node application can be debugged. I took a look at q.js:126 and platform.js:244 and both basically tie into some kind of exception thingy. It would be really neat if I could run this in a ‘debug mode’ and see what all the variables are at certain breakpoints. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Resolved] (CB-5666) Add Ubuntu Platform Guide Documentation
[ https://issues.apache.org/jira/browse/CB-5666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brooks resolved CB-5666. Resolution: Fixed Fix Version/s: 3.3.0 Add Ubuntu Platform Guide Documentation --- Key: CB-5666 URL: https://issues.apache.org/jira/browse/CB-5666 Project: Apache Cordova Issue Type: Improvement Components: Docs, Ubuntu Affects Versions: 3.3.0 Reporter: Michael Brooks Assignee: Michael Brooks Fix For: 3.3.0 Add the initial documentation for Cordova-Ubuntu. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CB-5648) cordova platform add android fails with Package name must look like: com.company.Name
[ https://issues.apache.org/jira/browse/CB-5648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13850827#comment-13850827 ] Andrew Grieve commented on CB-5648: --- You can change it by updating the ID value in your config.xml, and then CLI will reflect that value in the platform Info.plist / AndroidManifest files. That said, it doesn't rename Java namespace. I'd be in support of making the parameters non-optional, but wanted to point out that currently they were meant to be. cordova platform add android fails with Package name must look like: com.company.Name - Key: CB-5648 URL: https://issues.apache.org/jira/browse/CB-5648 Project: Apache Cordova Issue Type: Bug Components: Android, CLI Affects Versions: 3.1.0, 3.3.0 Environment: OS X 18.3 Reporter: Evan Rowley Priority: Minor Labels: newbie Fix For: 3.3.0 I was making my way through the PhoneGap 3 Beginner’s Guide by Giorigo Natili when I ran into the following error. Chapter 03 is on creating the HelloWorld app. The steps that got me to the error are: Step 1 cordova create ~/the/path/to/src/ch03 HelloWorld Step 2 cd ~/the/path/to/src/ch03 Step 3 cordova platform add android ^ This command doesn’t seem to work. What I get from running this is: Creating android project... /usr/local/lib/node_modules/cordova/node_modules/q/q.js:126 throw e; ^ Error: An error occured during creation of android sub-project. /Users/evanrowley/.cordova/lib/android/cordova/3.3.0/bin/node_modules/q/q.js:126 throw e; ^ Package name must look like: com.company.Name at /usr/local/lib/node_modules/cordova/src/platform.js:244:30 at ChildProcess.exithandler (child_process.js:641:7) at ChildProcess.EventEmitter.emit (events.js:98:17) at maybeClose (child_process.js:735:16) at Process.ChildProcess._handle.onexit (child_process.js:802:5) I would really like to debug this but I don’t have the slightest clue as to how my environment could be verified and/or how a node application can be debugged. I took a look at q.js:126 and platform.js:244 and both basically tie into some kind of exception thingy. It would be really neat if I could run this in a ‘debug mode’ and see what all the variables are at certain breakpoints. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CB-5667) Unix platforms should skip over non-executable files within .cordova/hooks
[ https://issues.apache.org/jira/browse/CB-5667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13850834#comment-13850834 ] ASF subversion and git services commented on CB-5667: - Commit 4a5dc404075b63d377d9f6014029fdf7093e90f5 in branch refs/heads/master from [~agrieve] [ https://git-wip-us.apache.org/repos/asf?p=cordova-cli.git;h=4a5dc40 ] CB-5667 Skip over non-executable hooks in non-windows environments. Unix platforms should skip over non-executable files within .cordova/hooks -- Key: CB-5667 URL: https://issues.apache.org/jira/browse/CB-5667 Project: Apache Cordova Issue Type: Bug Components: CLI Reporter: Andrew Grieve Assignee: Andrew Grieve Priority: Minor Right now, if you have two files: winhook.cmd osxhook.sh (+x) You'll get a fatal error instead of skipping the windows hook. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Created] (CB-5667) Unix platforms should skip over non-executable files within .cordova/hooks
Andrew Grieve created CB-5667: - Summary: Unix platforms should skip over non-executable files within .cordova/hooks Key: CB-5667 URL: https://issues.apache.org/jira/browse/CB-5667 Project: Apache Cordova Issue Type: Bug Components: CLI Reporter: Andrew Grieve Assignee: Andrew Grieve Priority: Minor Right now, if you have two files: winhook.cmd osxhook.sh (+x) You'll get a fatal error instead of skipping the windows hook. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Created] (CB-5669) [BlackBerry10] Add ability to build in release mode without signing
Bryan Higgins created CB-5669: - Summary: [BlackBerry10] Add ability to build in release mode without signing Key: CB-5669 URL: https://issues.apache.org/jira/browse/CB-5669 Project: Apache Cordova Issue Type: Bug Components: BlackBerry Reporter: Bryan Higgins Assignee: Bryan Higgins Fix For: 3.4.0 In some scenarios signing and building may be done on different machines. The tooling should support this. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CB-5666) Add Ubuntu Platform Guide Documentation
[ https://issues.apache.org/jira/browse/CB-5666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13850817#comment-13850817 ] ASF subversion and git services commented on CB-5666: - Commit 0ba031132a86bfb17c7468fd540b72f7c497353b in branch refs/heads/master from [~mwbrooks] [ https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;h=0ba0311 ] [CB-5666] Add Ubuntu platform guide for edge version. Add Ubuntu Platform Guide Documentation --- Key: CB-5666 URL: https://issues.apache.org/jira/browse/CB-5666 Project: Apache Cordova Issue Type: Improvement Components: Docs, Ubuntu Affects Versions: 3.3.0 Reporter: Michael Brooks Assignee: Michael Brooks Add the initial documentation for Cordova-Ubuntu. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Created] (CB-5668) [BlackBerry10] Error using build --release --web-inspector
Bryan Higgins created CB-5668: - Summary: [BlackBerry10] Error using build --release --web-inspector Key: CB-5668 URL: https://issues.apache.org/jira/browse/CB-5668 Project: Apache Cordova Issue Type: Bug Components: BlackBerry Affects Versions: 3.3.0 Reporter: Bryan Higgins Assignee: Bryan Higgins Fix For: 3.4.0 Error message: Application-Development-Mode in Manifest -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CB-5666) Add Ubuntu Platform Guide Documentation
[ https://issues.apache.org/jira/browse/CB-5666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13850812#comment-13850812 ] ASF subversion and git services commented on CB-5666: - Commit 42d015728bdffa1bfe017be33f19d7ded6ca6a4d in branch refs/heads/master from [~kyleN] [ https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;h=42d0157 ] [CB-5666] Add Ubuntu platform guide. Add Ubuntu Platform Guide Documentation --- Key: CB-5666 URL: https://issues.apache.org/jira/browse/CB-5666 Project: Apache Cordova Issue Type: Improvement Components: Docs, Ubuntu Affects Versions: 3.3.0 Reporter: Michael Brooks Assignee: Michael Brooks Add the initial documentation for Cordova-Ubuntu. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CB-5398) Pick image from Library or Photo album on android 4.4
[ https://issues.apache.org/jira/browse/CB-5398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13850761#comment-13850761 ] Mike Billau commented on CB-5398: - Still broken in 4.4.2. Should we file a bug against Android since this is a URI encoding bug and pretty different than the one posted earlier in the thread? Pick image from Library or Photo album on android 4.4 - Key: CB-5398 URL: https://issues.apache.org/jira/browse/CB-5398 Project: Apache Cordova Issue Type: Bug Components: Android, Plugin Camera Affects Versions: 2.9.0, 3.2.0 Environment: android 4.4 Reporter: julio cesar Assignee: Mike Billau An android 4.4 try to pick a photo using pictureSource.PHOTOLIBRARY or pictureSource.SAVEDPHOTOALBUM and return type destinationType.FILE_URI. Now android 4.4, when you select the above options, it opens an open from dialog that let you choose from new places as Recent, Drive, Images and Downloads (the names might not be the same as I use the device in spanish and translated it). If you choose any of them, you get an error, AndroidProtocolHandler, unable to open content URL: the url here with a content://com.android.providers format. I've tested on phonegap 2.9 because this is the version I use, but I suppose it affects all of them. (in fact I use 2.9.1) -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (CB-5664) AppCache's checking event fired more than once per App startup.
[
https://issues.apache.org/jira/browse/CB-5664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Godric Kwok updated CB-5664:
Description:
+Expected Behavior:+
1) AppCache is checked only *once* per App startup.
+Observed Behavior:+
1) AppCache is checked *multiple times* randomly per App startup.
+Steps to repeat:+
0) WebView loading a site with manifest.
1) console.log() AppCache's checking event.
2) Start App, see checking once.
3) *navigator.app.exitApp()*, then re-launches App.
4) First relaunch leads to a single checking still.
5) Repeat the relaunch *a few times*.
6) Then you'll see sometimes it's a double, a triple, or a quadruple (but never
5x).
7) Only a *KILL* from task switcher will reset these accumulations.
+Unwanted Results:+
1) Multiple checking triggers multiple subsequent events (download,
updateready, etc...) that renders the App slow.
2) Multiple updateready triggers multiple swapCache()/reload() that renders
the App appeared broken.
+Code Snippet:+
super.loadUrl( 'http://my.site.with.manifest/' );
document.addEventListener('deviceready', function(){
function logEvent(event) {
console.log('appcache: '+event.type);
}
window.applicationCache.addEventListener('checking', logEvent, false);
window.applicationCache.addEventListener('noupdate', logEvent, false);
window.applicationCache.addEventListener('downloading', logEvent, false);
window.applicationCache.addEventListener('progress', logEvent, false);
window.applicationCache.addEventListener('cached', logEvent, false);
window.applicationCache.addEventListener('updateready', logEvent, false);
window.applicationCache.addEventListener('obsolete', logEvent, false);
window.applicationCache.addEventListener('error', logEvent, false);
document.addEventListener('backbutton', function(){
navigator.app.exitApp();
}, false);
}, false);
+LogCat pattern:+
*(1x)*
12-17 21:11:13.470: I/Web Console(2142): appcache: checking:23
12-17 21:11:13.478: I/Web Console(2142): appcache: noupdate:23
*(1x, but +double+ updateready)*
12-17 21:11:47.775: I/Web Console(2142): appcache: checking:23
12-17 21:11:50.072: I/Web Console(2142): appcache: downloading:23
12-17 21:11:50.072: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.166: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.197: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.697: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.697: I/Web Console(2142): appcache: progress:23
12-17 21:11:50.697: I/Web Console(2142): appcache: updateready:23
12-17 21:11:50.697: I/Web Console(2142): appcache: updateready:23
*(2x)*
12-17 21:12:27.283: I/Web Console(2142): appcache: checking:23
12-17 21:12:27.283: I/Web Console(2142): appcache: checking:23
12-17 21:12:29.759: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:29.759: I/Web Console(2142): appcache: noupdate:23
*(2x)*
12-17 21:12:35.447: I/Web Console(2142): appcache: checking:23
12-17 21:12:35.447: I/Web Console(2142): appcache: checking:23
12-17 21:12:38.025: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:38.025: I/Web Console(2142): appcache: noupdate:23
*(3x)*
12-17 21:12:45.322: I/Web Console(2142): appcache: checking:23
12-17 21:12:45.322: I/Web Console(2142): appcache: checking:23
12-17 21:12:45.322: I/Web Console(2142): appcache: checking:23
12-17 21:12:47.345: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:47.345: I/Web Console(2142): appcache: noupdate:23
12-17 21:12:47.345: I/Web Console(2142): appcache: noupdate:23
was:
+Expected Behavior:+
1) AppCache is checked only *once* per App startup.
+Observed Behavior:+
1) AppCache is checked *multiple times* randomly per App startup.
+Steps to repeat:+
1) console.log() AppCache's checking event.
2) Start App, see checking once.
3) *navigator.app.exitApp()*, then re-launches App.
4) First relaunch leads to a single checking still.
5) Repeat the relaunch *a few times*.
6) Then you'll see sometimes it's a double, a triple, or a quadruple (but never
5x).
7) Only a *KILL* from task switcher will reset these accumulations.
+Unwanted Results:+
1) Multiple checking triggers multiple subsequent events (download,
updateready, etc...) that renders the App slow.
2) Multiple updateready triggers multiple swapCache()/reload() that renders
the App appeared broken.
+Code Snippet:+
document.addEventListener('deviceready', function(){
function logEvent(event) {
console.log('appcache: '+event.type);
}
window.applicationCache.addEventListener('checking', logEvent, false);
window.applicationCache.addEventListener('noupdate', logEvent, false);
window.applicationCache.addEventListener('downloading', logEvent, false);
window.applicationCache.addEventListener('progress', logEvent, false);
window.applicationCache.addEventListener('cached', logEvent, false);
window.applicationCache.addEventListener('updateready', logEvent, false);
[jira] [Commented] (CB-5658) Move plugin docs to plugin repos
[ https://issues.apache.org/jira/browse/CB-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13851204#comment-13851204 ] Andrew Grieve commented on CB-5658: --- ML thread: http://markmail.org/thread/gnoqo7pjdb2v7hre Move plugin docs to plugin repos Key: CB-5658 URL: https://issues.apache.org/jira/browse/CB-5658 Project: Apache Cordova Issue Type: Bug Components: Docs, Plugin Battery Status, Plugin Camera, Plugin Console, Plugin Contacts, Plugin Device, Plugin Device Motion, Plugin Device Orientation, Plugin Dialogs, Plugin File, Plugin File Transfer, Plugin Geolocation, Plugin Globalization, Plugin InAppBrowser, Plugin Media, Plugin Media Capture, Plugin Network Information, Plugin SplashScreen, Plugin Vibration Reporter: Andrew Grieve Assignee: Andrew Grieve This involves: 1. Delete the docs/ directory from all plugins - They contain stale copies of what's in cordova-docs 2. Move plugin information found in cordova-docs into a single README.md file within the respective plugin repos 3. Delete the API Reference section of cordova-docs 4. Add a guide called Cordova Plugins, which contains: - a link to plugins.cordova.io, - a list of the org.apache.cordova plugins, which link to their README.md files on github - e.g. https://github.com/apache/cordova-plugin-media-capture/blob/master/README.md - These can be changed to point at their plugins.cordova.io page when that shows READMEs. - A link to the 3.3 docs, which still have plugin API reference - Mostly, this is for finding non-english versions. Motivation: - Plugins are on a separate release cycle from platforms docs. - The documentation is often mismatched due to this - Pull requests for plugins don't update the plugin docs - But I think they would if the docs were in the same repo Caveats: - This will mess up our current translations story for plugins. - I think this can be fixed up though, by changing out http://crowdin.net push / pull scripts - E.g. have README.md translations go in: cordova-plugin-foo/translations/fr/README.md -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CB-5658) Move plugin docs to plugin repos
[ https://issues.apache.org/jira/browse/CB-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13851242#comment-13851242 ] ASF subversion and git services commented on CB-5658: - Commit 390655dd5b029230647912fbcc7502dc7f4b1bdd in branch refs/heads/dev from [~agrieve] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-battery-status.git;h=390655d ] CB-5658 Delete stale snapshot of plugin docs Move plugin docs to plugin repos Key: CB-5658 URL: https://issues.apache.org/jira/browse/CB-5658 Project: Apache Cordova Issue Type: Bug Components: Docs, Plugin Battery Status, Plugin Camera, Plugin Console, Plugin Contacts, Plugin Device, Plugin Device Motion, Plugin Device Orientation, Plugin Dialogs, Plugin File, Plugin File Transfer, Plugin Geolocation, Plugin Globalization, Plugin InAppBrowser, Plugin Media, Plugin Media Capture, Plugin Network Information, Plugin SplashScreen, Plugin Vibration Reporter: Andrew Grieve Assignee: Andrew Grieve This involves: 1. Delete the docs/ directory from all plugins - They contain stale copies of what's in cordova-docs 2. Move plugin information found in cordova-docs into a single doc/index.md file within the respective plugin repos - Link to this file within each plugin's README.md file 3. Delete the API Reference section of cordova-docs 4. Add a guide called Cordova Plugins, which contains: - a link to plugins.cordova.io, - a list of the org.apache.cordova plugins, which link to their index.md files on github - e.g. https://github.com/apache/cordova-plugin-media-capture/blob/master/README.md - These can be changed to point at their plugins.cordova.io page when that shows READMEs. - A link to the 3.3 docs, which still have plugin API reference - Mostly, this is for finding non-english versions. Motivation: - Plugins are on a separate release cycle from platforms docs. - The documentation is often mismatched due to this - Pull requests for plugins don't update the plugin docs - But I think they would if the docs were in the same repo Caveats: - This will mess up our current translations story for plugins. - I think this can be fixed up though, by changing out http://crowdin.net push / pull scripts - E.g. have README.md translations go in: cordova-plugin-foo/translations/fr/README.md -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CB-5658) Move plugin docs to plugin repos
[ https://issues.apache.org/jira/browse/CB-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13851255#comment-13851255 ] ASF subversion and git services commented on CB-5658: - Commit e06ec8a758d842519a3f37312dcce737507f466f in branch refs/heads/dev from [~agrieve] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-media.git;h=e06ec8a ] CB-5658 Delete stale snapshot of plugin docs Move plugin docs to plugin repos Key: CB-5658 URL: https://issues.apache.org/jira/browse/CB-5658 Project: Apache Cordova Issue Type: Bug Components: Docs, Plugin Battery Status, Plugin Camera, Plugin Console, Plugin Contacts, Plugin Device, Plugin Device Motion, Plugin Device Orientation, Plugin Dialogs, Plugin File, Plugin File Transfer, Plugin Geolocation, Plugin Globalization, Plugin InAppBrowser, Plugin Media, Plugin Media Capture, Plugin Network Information, Plugin SplashScreen, Plugin Vibration Reporter: Andrew Grieve Assignee: Andrew Grieve This involves: 1. Delete the docs/ directory from all plugins - They contain stale copies of what's in cordova-docs 2. Move plugin information found in cordova-docs into a single doc/index.md file within the respective plugin repos - Link to this file within each plugin's README.md file 3. Delete the API Reference section of cordova-docs 4. Add a guide called Cordova Plugins, which contains: - a link to plugins.cordova.io, - a list of the org.apache.cordova plugins, which link to their index.md files on github - e.g. https://github.com/apache/cordova-plugin-media-capture/blob/master/README.md - These can be changed to point at their plugins.cordova.io page when that shows READMEs. - A link to the 3.3 docs, which still have plugin API reference - Mostly, this is for finding non-english versions. Motivation: - Plugins are on a separate release cycle from platforms docs. - The documentation is often mismatched due to this - Pull requests for plugins don't update the plugin docs - But I think they would if the docs were in the same repo Caveats: - This will mess up our current translations story for plugins. - I think this can be fixed up though, by changing out http://crowdin.net push / pull scripts - E.g. have README.md translations go in: cordova-plugin-foo/translations/fr/README.md -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CB-5658) Move plugin docs to plugin repos
[ https://issues.apache.org/jira/browse/CB-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13851251#comment-13851251 ] ASF subversion and git services commented on CB-5658: - Commit 148a13bc8c8e4ee58c938dbe41a14732a33fd5da in branch refs/heads/dev from [~agrieve] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-file-transfer.git;h=148a13b ] CB-5658 Delete stale snapshot of plugin docs Move plugin docs to plugin repos Key: CB-5658 URL: https://issues.apache.org/jira/browse/CB-5658 Project: Apache Cordova Issue Type: Bug Components: Docs, Plugin Battery Status, Plugin Camera, Plugin Console, Plugin Contacts, Plugin Device, Plugin Device Motion, Plugin Device Orientation, Plugin Dialogs, Plugin File, Plugin File Transfer, Plugin Geolocation, Plugin Globalization, Plugin InAppBrowser, Plugin Media, Plugin Media Capture, Plugin Network Information, Plugin SplashScreen, Plugin Vibration Reporter: Andrew Grieve Assignee: Andrew Grieve This involves: 1. Delete the docs/ directory from all plugins - They contain stale copies of what's in cordova-docs 2. Move plugin information found in cordova-docs into a single doc/index.md file within the respective plugin repos - Link to this file within each plugin's README.md file 3. Delete the API Reference section of cordova-docs 4. Add a guide called Cordova Plugins, which contains: - a link to plugins.cordova.io, - a list of the org.apache.cordova plugins, which link to their index.md files on github - e.g. https://github.com/apache/cordova-plugin-media-capture/blob/master/README.md - These can be changed to point at their plugins.cordova.io page when that shows READMEs. - A link to the 3.3 docs, which still have plugin API reference - Mostly, this is for finding non-english versions. Motivation: - Plugins are on a separate release cycle from platforms docs. - The documentation is often mismatched due to this - Pull requests for plugins don't update the plugin docs - But I think they would if the docs were in the same repo Caveats: - This will mess up our current translations story for plugins. - I think this can be fixed up though, by changing out http://crowdin.net push / pull scripts - E.g. have README.md translations go in: cordova-plugin-foo/translations/fr/README.md -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CB-5658) Move plugin docs to plugin repos
[ https://issues.apache.org/jira/browse/CB-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13851258#comment-13851258 ] ASF subversion and git services commented on CB-5658: - Commit c2d22c0671bed942a470a2a033d9450106f0c0e5 in branch refs/heads/dev from [~agrieve] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-splashscreen.git;h=c2d22c0 ] CB-5658 Delete stale snapshot of plugin docs Move plugin docs to plugin repos Key: CB-5658 URL: https://issues.apache.org/jira/browse/CB-5658 Project: Apache Cordova Issue Type: Bug Components: Docs, Plugin Battery Status, Plugin Camera, Plugin Console, Plugin Contacts, Plugin Device, Plugin Device Motion, Plugin Device Orientation, Plugin Dialogs, Plugin File, Plugin File Transfer, Plugin Geolocation, Plugin Globalization, Plugin InAppBrowser, Plugin Media, Plugin Media Capture, Plugin Network Information, Plugin SplashScreen, Plugin Vibration Reporter: Andrew Grieve Assignee: Andrew Grieve This involves: 1. Delete the docs/ directory from all plugins - They contain stale copies of what's in cordova-docs 2. Move plugin information found in cordova-docs into a single doc/index.md file within the respective plugin repos - Link to this file within each plugin's README.md file 3. Delete the API Reference section of cordova-docs 4. Add a guide called Cordova Plugins, which contains: - a link to plugins.cordova.io, - a list of the org.apache.cordova plugins, which link to their index.md files on github - e.g. https://github.com/apache/cordova-plugin-media-capture/blob/master/README.md - These can be changed to point at their plugins.cordova.io page when that shows READMEs. - A link to the 3.3 docs, which still have plugin API reference - Mostly, this is for finding non-english versions. Motivation: - Plugins are on a separate release cycle from platforms docs. - The documentation is often mismatched due to this - Pull requests for plugins don't update the plugin docs - But I think they would if the docs were in the same repo Caveats: - This will mess up our current translations story for plugins. - I think this can be fixed up though, by changing out http://crowdin.net push / pull scripts - E.g. have README.md translations go in: cordova-plugin-foo/translations/fr/README.md -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CB-5658) Move plugin docs to plugin repos
[ https://issues.apache.org/jira/browse/CB-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13851243#comment-13851243 ] ASF subversion and git services commented on CB-5658: - Commit 7574e663156583ebca47350a6682730dc791cbf1 in branch refs/heads/dev from [~agrieve] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-camera.git;h=7574e66 ] CB-5658 Delete stale snapshot of plugin docs Move plugin docs to plugin repos Key: CB-5658 URL: https://issues.apache.org/jira/browse/CB-5658 Project: Apache Cordova Issue Type: Bug Components: Docs, Plugin Battery Status, Plugin Camera, Plugin Console, Plugin Contacts, Plugin Device, Plugin Device Motion, Plugin Device Orientation, Plugin Dialogs, Plugin File, Plugin File Transfer, Plugin Geolocation, Plugin Globalization, Plugin InAppBrowser, Plugin Media, Plugin Media Capture, Plugin Network Information, Plugin SplashScreen, Plugin Vibration Reporter: Andrew Grieve Assignee: Andrew Grieve This involves: 1. Delete the docs/ directory from all plugins - They contain stale copies of what's in cordova-docs 2. Move plugin information found in cordova-docs into a single doc/index.md file within the respective plugin repos - Link to this file within each plugin's README.md file 3. Delete the API Reference section of cordova-docs 4. Add a guide called Cordova Plugins, which contains: - a link to plugins.cordova.io, - a list of the org.apache.cordova plugins, which link to their index.md files on github - e.g. https://github.com/apache/cordova-plugin-media-capture/blob/master/README.md - These can be changed to point at their plugins.cordova.io page when that shows READMEs. - A link to the 3.3 docs, which still have plugin API reference - Mostly, this is for finding non-english versions. Motivation: - Plugins are on a separate release cycle from platforms docs. - The documentation is often mismatched due to this - Pull requests for plugins don't update the plugin docs - But I think they would if the docs were in the same repo Caveats: - This will mess up our current translations story for plugins. - I think this can be fixed up though, by changing out http://crowdin.net push / pull scripts - E.g. have README.md translations go in: cordova-plugin-foo/translations/fr/README.md -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CB-5658) Move plugin docs to plugin repos
[ https://issues.apache.org/jira/browse/CB-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13851249#comment-13851249 ] ASF subversion and git services commented on CB-5658: - Commit a826e662f444b4f57b579bff9551db3aaafdd58b in branch refs/heads/dev from [~agrieve] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-dialogs.git;h=a826e66 ] CB-5658 Delete stale snapshot of plugin docs Move plugin docs to plugin repos Key: CB-5658 URL: https://issues.apache.org/jira/browse/CB-5658 Project: Apache Cordova Issue Type: Bug Components: Docs, Plugin Battery Status, Plugin Camera, Plugin Console, Plugin Contacts, Plugin Device, Plugin Device Motion, Plugin Device Orientation, Plugin Dialogs, Plugin File, Plugin File Transfer, Plugin Geolocation, Plugin Globalization, Plugin InAppBrowser, Plugin Media, Plugin Media Capture, Plugin Network Information, Plugin SplashScreen, Plugin Vibration Reporter: Andrew Grieve Assignee: Andrew Grieve This involves: 1. Delete the docs/ directory from all plugins - They contain stale copies of what's in cordova-docs 2. Move plugin information found in cordova-docs into a single doc/index.md file within the respective plugin repos - Link to this file within each plugin's README.md file 3. Delete the API Reference section of cordova-docs 4. Add a guide called Cordova Plugins, which contains: - a link to plugins.cordova.io, - a list of the org.apache.cordova plugins, which link to their index.md files on github - e.g. https://github.com/apache/cordova-plugin-media-capture/blob/master/README.md - These can be changed to point at their plugins.cordova.io page when that shows READMEs. - A link to the 3.3 docs, which still have plugin API reference - Mostly, this is for finding non-english versions. Motivation: - Plugins are on a separate release cycle from platforms docs. - The documentation is often mismatched due to this - Pull requests for plugins don't update the plugin docs - But I think they would if the docs were in the same repo Caveats: - This will mess up our current translations story for plugins. - I think this can be fixed up though, by changing out http://crowdin.net push / pull scripts - E.g. have README.md translations go in: cordova-plugin-foo/translations/fr/README.md -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CB-5658) Move plugin docs to plugin repos
[ https://issues.apache.org/jira/browse/CB-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13851254#comment-13851254 ] ASF subversion and git services commented on CB-5658: - Commit 97c6f2ba8a112189a20e73b3502ee81bc455e8f3 in branch refs/heads/dev from [~agrieve] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-inappbrowser.git;h=97c6f2b ] CB-5658 Delete stale snapshot of plugin docs Move plugin docs to plugin repos Key: CB-5658 URL: https://issues.apache.org/jira/browse/CB-5658 Project: Apache Cordova Issue Type: Bug Components: Docs, Plugin Battery Status, Plugin Camera, Plugin Console, Plugin Contacts, Plugin Device, Plugin Device Motion, Plugin Device Orientation, Plugin Dialogs, Plugin File, Plugin File Transfer, Plugin Geolocation, Plugin Globalization, Plugin InAppBrowser, Plugin Media, Plugin Media Capture, Plugin Network Information, Plugin SplashScreen, Plugin Vibration Reporter: Andrew Grieve Assignee: Andrew Grieve This involves: 1. Delete the docs/ directory from all plugins - They contain stale copies of what's in cordova-docs 2. Move plugin information found in cordova-docs into a single doc/index.md file within the respective plugin repos - Link to this file within each plugin's README.md file 3. Delete the API Reference section of cordova-docs 4. Add a guide called Cordova Plugins, which contains: - a link to plugins.cordova.io, - a list of the org.apache.cordova plugins, which link to their index.md files on github - e.g. https://github.com/apache/cordova-plugin-media-capture/blob/master/README.md - These can be changed to point at their plugins.cordova.io page when that shows READMEs. - A link to the 3.3 docs, which still have plugin API reference - Mostly, this is for finding non-english versions. Motivation: - Plugins are on a separate release cycle from platforms docs. - The documentation is often mismatched due to this - Pull requests for plugins don't update the plugin docs - But I think they would if the docs were in the same repo Caveats: - This will mess up our current translations story for plugins. - I think this can be fixed up though, by changing out http://crowdin.net push / pull scripts - E.g. have README.md translations go in: cordova-plugin-foo/translations/fr/README.md -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CB-5658) Move plugin docs to plugin repos
[ https://issues.apache.org/jira/browse/CB-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13851252#comment-13851252 ] ASF subversion and git services commented on CB-5658: - Commit 5f1ede9b405caf369375eea28502facd273f55cf in branch refs/heads/dev from [~agrieve] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-geolocation.git;h=5f1ede9 ] CB-5658 Delete stale snapshot of plugin docs Move plugin docs to plugin repos Key: CB-5658 URL: https://issues.apache.org/jira/browse/CB-5658 Project: Apache Cordova Issue Type: Bug Components: Docs, Plugin Battery Status, Plugin Camera, Plugin Console, Plugin Contacts, Plugin Device, Plugin Device Motion, Plugin Device Orientation, Plugin Dialogs, Plugin File, Plugin File Transfer, Plugin Geolocation, Plugin Globalization, Plugin InAppBrowser, Plugin Media, Plugin Media Capture, Plugin Network Information, Plugin SplashScreen, Plugin Vibration Reporter: Andrew Grieve Assignee: Andrew Grieve This involves: 1. Delete the docs/ directory from all plugins - They contain stale copies of what's in cordova-docs 2. Move plugin information found in cordova-docs into a single doc/index.md file within the respective plugin repos - Link to this file within each plugin's README.md file 3. Delete the API Reference section of cordova-docs 4. Add a guide called Cordova Plugins, which contains: - a link to plugins.cordova.io, - a list of the org.apache.cordova plugins, which link to their index.md files on github - e.g. https://github.com/apache/cordova-plugin-media-capture/blob/master/README.md - These can be changed to point at their plugins.cordova.io page when that shows READMEs. - A link to the 3.3 docs, which still have plugin API reference - Mostly, this is for finding non-english versions. Motivation: - Plugins are on a separate release cycle from platforms docs. - The documentation is often mismatched due to this - Pull requests for plugins don't update the plugin docs - But I think they would if the docs were in the same repo Caveats: - This will mess up our current translations story for plugins. - I think this can be fixed up though, by changing out http://crowdin.net push / pull scripts - E.g. have README.md translations go in: cordova-plugin-foo/translations/fr/README.md -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CB-5658) Move plugin docs to plugin repos
[ https://issues.apache.org/jira/browse/CB-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13851248#comment-13851248 ] ASF subversion and git services commented on CB-5658: - Commit f0ae9c80399d96b57f7a6348fd51b97a3be60917 in branch refs/heads/dev from [~agrieve] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-device-orientation.git;h=f0ae9c8 ] CB-5658 Delete stale snapshot of plugin docs Move plugin docs to plugin repos Key: CB-5658 URL: https://issues.apache.org/jira/browse/CB-5658 Project: Apache Cordova Issue Type: Bug Components: Docs, Plugin Battery Status, Plugin Camera, Plugin Console, Plugin Contacts, Plugin Device, Plugin Device Motion, Plugin Device Orientation, Plugin Dialogs, Plugin File, Plugin File Transfer, Plugin Geolocation, Plugin Globalization, Plugin InAppBrowser, Plugin Media, Plugin Media Capture, Plugin Network Information, Plugin SplashScreen, Plugin Vibration Reporter: Andrew Grieve Assignee: Andrew Grieve This involves: 1. Delete the docs/ directory from all plugins - They contain stale copies of what's in cordova-docs 2. Move plugin information found in cordova-docs into a single doc/index.md file within the respective plugin repos - Link to this file within each plugin's README.md file 3. Delete the API Reference section of cordova-docs 4. Add a guide called Cordova Plugins, which contains: - a link to plugins.cordova.io, - a list of the org.apache.cordova plugins, which link to their index.md files on github - e.g. https://github.com/apache/cordova-plugin-media-capture/blob/master/README.md - These can be changed to point at their plugins.cordova.io page when that shows READMEs. - A link to the 3.3 docs, which still have plugin API reference - Mostly, this is for finding non-english versions. Motivation: - Plugins are on a separate release cycle from platforms docs. - The documentation is often mismatched due to this - Pull requests for plugins don't update the plugin docs - But I think they would if the docs were in the same repo Caveats: - This will mess up our current translations story for plugins. - I think this can be fixed up though, by changing out http://crowdin.net push / pull scripts - E.g. have README.md translations go in: cordova-plugin-foo/translations/fr/README.md -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CB-5658) Move plugin docs to plugin repos
[ https://issues.apache.org/jira/browse/CB-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13851245#comment-13851245 ] ASF subversion and git services commented on CB-5658: - Commit 4884d949872e42916ec33b5b328b7a24bcc4895d in branch refs/heads/dev from [~agrieve] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-contacts.git;h=4884d94 ] CB-5658 Delete stale snapshot of plugin docs Move plugin docs to plugin repos Key: CB-5658 URL: https://issues.apache.org/jira/browse/CB-5658 Project: Apache Cordova Issue Type: Bug Components: Docs, Plugin Battery Status, Plugin Camera, Plugin Console, Plugin Contacts, Plugin Device, Plugin Device Motion, Plugin Device Orientation, Plugin Dialogs, Plugin File, Plugin File Transfer, Plugin Geolocation, Plugin Globalization, Plugin InAppBrowser, Plugin Media, Plugin Media Capture, Plugin Network Information, Plugin SplashScreen, Plugin Vibration Reporter: Andrew Grieve Assignee: Andrew Grieve This involves: 1. Delete the docs/ directory from all plugins - They contain stale copies of what's in cordova-docs 2. Move plugin information found in cordova-docs into a single doc/index.md file within the respective plugin repos - Link to this file within each plugin's README.md file 3. Delete the API Reference section of cordova-docs 4. Add a guide called Cordova Plugins, which contains: - a link to plugins.cordova.io, - a list of the org.apache.cordova plugins, which link to their index.md files on github - e.g. https://github.com/apache/cordova-plugin-media-capture/blob/master/README.md - These can be changed to point at their plugins.cordova.io page when that shows READMEs. - A link to the 3.3 docs, which still have plugin API reference - Mostly, this is for finding non-english versions. Motivation: - Plugins are on a separate release cycle from platforms docs. - The documentation is often mismatched due to this - Pull requests for plugins don't update the plugin docs - But I think they would if the docs were in the same repo Caveats: - This will mess up our current translations story for plugins. - I think this can be fixed up though, by changing out http://crowdin.net push / pull scripts - E.g. have README.md translations go in: cordova-plugin-foo/translations/fr/README.md -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CB-5658) Move plugin docs to plugin repos
[ https://issues.apache.org/jira/browse/CB-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13851257#comment-13851257 ] ASF subversion and git services commented on CB-5658: - Commit d71b83e20c8476b83dbaa618536efd056cc1744b in branch refs/heads/dev from [~agrieve] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-network-information.git;h=d71b83e ] CB-5658 Delete stale snapshot of plugin docs Move plugin docs to plugin repos Key: CB-5658 URL: https://issues.apache.org/jira/browse/CB-5658 Project: Apache Cordova Issue Type: Bug Components: Docs, Plugin Battery Status, Plugin Camera, Plugin Console, Plugin Contacts, Plugin Device, Plugin Device Motion, Plugin Device Orientation, Plugin Dialogs, Plugin File, Plugin File Transfer, Plugin Geolocation, Plugin Globalization, Plugin InAppBrowser, Plugin Media, Plugin Media Capture, Plugin Network Information, Plugin SplashScreen, Plugin Vibration Reporter: Andrew Grieve Assignee: Andrew Grieve This involves: 1. Delete the docs/ directory from all plugins - They contain stale copies of what's in cordova-docs 2. Move plugin information found in cordova-docs into a single doc/index.md file within the respective plugin repos - Link to this file within each plugin's README.md file 3. Delete the API Reference section of cordova-docs 4. Add a guide called Cordova Plugins, which contains: - a link to plugins.cordova.io, - a list of the org.apache.cordova plugins, which link to their index.md files on github - e.g. https://github.com/apache/cordova-plugin-media-capture/blob/master/README.md - These can be changed to point at their plugins.cordova.io page when that shows READMEs. - A link to the 3.3 docs, which still have plugin API reference - Mostly, this is for finding non-english versions. Motivation: - Plugins are on a separate release cycle from platforms docs. - The documentation is often mismatched due to this - Pull requests for plugins don't update the plugin docs - But I think they would if the docs were in the same repo Caveats: - This will mess up our current translations story for plugins. - I think this can be fixed up though, by changing out http://crowdin.net push / pull scripts - E.g. have README.md translations go in: cordova-plugin-foo/translations/fr/README.md -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CB-5658) Move plugin docs to plugin repos
[ https://issues.apache.org/jira/browse/CB-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13851247#comment-13851247 ] ASF subversion and git services commented on CB-5658: - Commit fc325b9c034a37f7a225a9ac6bfe137a3fdcfead in branch refs/heads/dev from [~agrieve] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-device-motion.git;h=fc325b9 ] CB-5658 Delete stale snapshot of plugin docs Move plugin docs to plugin repos Key: CB-5658 URL: https://issues.apache.org/jira/browse/CB-5658 Project: Apache Cordova Issue Type: Bug Components: Docs, Plugin Battery Status, Plugin Camera, Plugin Console, Plugin Contacts, Plugin Device, Plugin Device Motion, Plugin Device Orientation, Plugin Dialogs, Plugin File, Plugin File Transfer, Plugin Geolocation, Plugin Globalization, Plugin InAppBrowser, Plugin Media, Plugin Media Capture, Plugin Network Information, Plugin SplashScreen, Plugin Vibration Reporter: Andrew Grieve Assignee: Andrew Grieve This involves: 1. Delete the docs/ directory from all plugins - They contain stale copies of what's in cordova-docs 2. Move plugin information found in cordova-docs into a single doc/index.md file within the respective plugin repos - Link to this file within each plugin's README.md file 3. Delete the API Reference section of cordova-docs 4. Add a guide called Cordova Plugins, which contains: - a link to plugins.cordova.io, - a list of the org.apache.cordova plugins, which link to their index.md files on github - e.g. https://github.com/apache/cordova-plugin-media-capture/blob/master/README.md - These can be changed to point at their plugins.cordova.io page when that shows READMEs. - A link to the 3.3 docs, which still have plugin API reference - Mostly, this is for finding non-english versions. Motivation: - Plugins are on a separate release cycle from platforms docs. - The documentation is often mismatched due to this - Pull requests for plugins don't update the plugin docs - But I think they would if the docs were in the same repo Caveats: - This will mess up our current translations story for plugins. - I think this can be fixed up though, by changing out http://crowdin.net push / pull scripts - E.g. have README.md translations go in: cordova-plugin-foo/translations/fr/README.md -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CB-5658) Move plugin docs to plugin repos
[ https://issues.apache.org/jira/browse/CB-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13851256#comment-13851256 ] ASF subversion and git services commented on CB-5658: - Commit 8af169f6df3f165a47674a87acb55474c4a51c62 in branch refs/heads/dev from [~agrieve] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-media-capture.git;h=8af169f ] CB-5658 Delete stale snapshot of plugin docs Move plugin docs to plugin repos Key: CB-5658 URL: https://issues.apache.org/jira/browse/CB-5658 Project: Apache Cordova Issue Type: Bug Components: Docs, Plugin Battery Status, Plugin Camera, Plugin Console, Plugin Contacts, Plugin Device, Plugin Device Motion, Plugin Device Orientation, Plugin Dialogs, Plugin File, Plugin File Transfer, Plugin Geolocation, Plugin Globalization, Plugin InAppBrowser, Plugin Media, Plugin Media Capture, Plugin Network Information, Plugin SplashScreen, Plugin Vibration Reporter: Andrew Grieve Assignee: Andrew Grieve This involves: 1. Delete the docs/ directory from all plugins - They contain stale copies of what's in cordova-docs 2. Move plugin information found in cordova-docs into a single doc/index.md file within the respective plugin repos - Link to this file within each plugin's README.md file 3. Delete the API Reference section of cordova-docs 4. Add a guide called Cordova Plugins, which contains: - a link to plugins.cordova.io, - a list of the org.apache.cordova plugins, which link to their index.md files on github - e.g. https://github.com/apache/cordova-plugin-media-capture/blob/master/README.md - These can be changed to point at their plugins.cordova.io page when that shows READMEs. - A link to the 3.3 docs, which still have plugin API reference - Mostly, this is for finding non-english versions. Motivation: - Plugins are on a separate release cycle from platforms docs. - The documentation is often mismatched due to this - Pull requests for plugins don't update the plugin docs - But I think they would if the docs were in the same repo Caveats: - This will mess up our current translations story for plugins. - I think this can be fixed up though, by changing out http://crowdin.net push / pull scripts - E.g. have README.md translations go in: cordova-plugin-foo/translations/fr/README.md -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CB-5658) Move plugin docs to plugin repos
[ https://issues.apache.org/jira/browse/CB-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13851250#comment-13851250 ] ASF subversion and git services commented on CB-5658: - Commit c8480221b3b3985900621ea39132a0b379a18ae9 in branch refs/heads/dev from [~agrieve] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-file.git;h=c848022 ] CB-5658 Delete stale snapshot of plugin docs Move plugin docs to plugin repos Key: CB-5658 URL: https://issues.apache.org/jira/browse/CB-5658 Project: Apache Cordova Issue Type: Bug Components: Docs, Plugin Battery Status, Plugin Camera, Plugin Console, Plugin Contacts, Plugin Device, Plugin Device Motion, Plugin Device Orientation, Plugin Dialogs, Plugin File, Plugin File Transfer, Plugin Geolocation, Plugin Globalization, Plugin InAppBrowser, Plugin Media, Plugin Media Capture, Plugin Network Information, Plugin SplashScreen, Plugin Vibration Reporter: Andrew Grieve Assignee: Andrew Grieve This involves: 1. Delete the docs/ directory from all plugins - They contain stale copies of what's in cordova-docs 2. Move plugin information found in cordova-docs into a single doc/index.md file within the respective plugin repos - Link to this file within each plugin's README.md file 3. Delete the API Reference section of cordova-docs 4. Add a guide called Cordova Plugins, which contains: - a link to plugins.cordova.io, - a list of the org.apache.cordova plugins, which link to their index.md files on github - e.g. https://github.com/apache/cordova-plugin-media-capture/blob/master/README.md - These can be changed to point at their plugins.cordova.io page when that shows READMEs. - A link to the 3.3 docs, which still have plugin API reference - Mostly, this is for finding non-english versions. Motivation: - Plugins are on a separate release cycle from platforms docs. - The documentation is often mismatched due to this - Pull requests for plugins don't update the plugin docs - But I think they would if the docs were in the same repo Caveats: - This will mess up our current translations story for plugins. - I think this can be fixed up though, by changing out http://crowdin.net push / pull scripts - E.g. have README.md translations go in: cordova-plugin-foo/translations/fr/README.md -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CB-5658) Move plugin docs to plugin repos
[ https://issues.apache.org/jira/browse/CB-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13851246#comment-13851246 ] ASF subversion and git services commented on CB-5658: - Commit fdf421929a31375624a849972f5d50f77a094b23 in branch refs/heads/dev from [~agrieve] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-device.git;h=fdf4219 ] CB-5658 Delete stale snapshot of plugin docs Move plugin docs to plugin repos Key: CB-5658 URL: https://issues.apache.org/jira/browse/CB-5658 Project: Apache Cordova Issue Type: Bug Components: Docs, Plugin Battery Status, Plugin Camera, Plugin Console, Plugin Contacts, Plugin Device, Plugin Device Motion, Plugin Device Orientation, Plugin Dialogs, Plugin File, Plugin File Transfer, Plugin Geolocation, Plugin Globalization, Plugin InAppBrowser, Plugin Media, Plugin Media Capture, Plugin Network Information, Plugin SplashScreen, Plugin Vibration Reporter: Andrew Grieve Assignee: Andrew Grieve This involves: 1. Delete the docs/ directory from all plugins - They contain stale copies of what's in cordova-docs 2. Move plugin information found in cordova-docs into a single doc/index.md file within the respective plugin repos - Link to this file within each plugin's README.md file 3. Delete the API Reference section of cordova-docs 4. Add a guide called Cordova Plugins, which contains: - a link to plugins.cordova.io, - a list of the org.apache.cordova plugins, which link to their index.md files on github - e.g. https://github.com/apache/cordova-plugin-media-capture/blob/master/README.md - These can be changed to point at their plugins.cordova.io page when that shows READMEs. - A link to the 3.3 docs, which still have plugin API reference - Mostly, this is for finding non-english versions. Motivation: - Plugins are on a separate release cycle from platforms docs. - The documentation is often mismatched due to this - Pull requests for plugins don't update the plugin docs - But I think they would if the docs were in the same repo Caveats: - This will mess up our current translations story for plugins. - I think this can be fixed up though, by changing out http://crowdin.net push / pull scripts - E.g. have README.md translations go in: cordova-plugin-foo/translations/fr/README.md -- This message was sent by Atlassian JIRA (v6.1.4#6159)
