[jira] [Commented] (CB-7838) Contact Picker returns -1 as the id for all contacts
[
https://issues.apache.org/jira/browse/CB-7838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14187308#comment-14187308
]
Ralph S Theart commented on CB-7838:
How can test against the cancelled action if and contact obj is returned on
both a successful choice and a canceled one?
Contact Picker returns -1 as the id for all contacts
Key: CB-7838
URL: https://issues.apache.org/jira/browse/CB-7838
Project: Apache Cordova
Issue Type: Bug
Components: Plugin Contacts
Affects Versions: 3.5.0
Environment: iOS
Reporter: Ralph S Theart
Can anyone confirm that the contacts plug-in returns -1 for any contact id
return from a device but it on the simulator returns a valid unique ID?
Its strange..I have ios8 devices that return -1 for any contact picked...but
the same action on the simulators returns a positive integer.
{code:title=From iOS 8 Device|borderStyle=solid}
{
id: -1,
rawId: null,
displayName: null,
name: {
givenName: Aunte,
formatted: Aunte Aline,
middleName: null,
familyName: Aline,
honorificPrefix: null,
honorificSuffix: null
},
nickname: null,
phoneNumbers: [
{
type: other,
value: 01141223***,
id: 0,
pref: false
}
],
emails: [
{
type: home,
value: vito.**@bluewin.ch,
id: 0,
pref: false
}
],.
{code}
{code:title=From ios-sim}
{
id: 7,
rawId: null,
displayName: null,
name: {
givenName: Test,
formatted: Test,
middleName: null,
familyName: null,
honorificPrefix: null,
honorificSuffix: null
},
nickname: null,
phoneNumbers: [
{
type: home,
value: (954)\u00a0646-7923,
id: 0,
pref: false
}
],
emails: null,
addresses: null,
ims: null,
organizations: null,
birthday: null,
note: null,
photos: null,
categories: null,
urls: null
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Comment Edited] (CB-7838) Contact Picker returns -1 as the id for all contacts
[
https://issues.apache.org/jira/browse/CB-7838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14179467#comment-14179467
]
Ralph S Theart edited comment on CB-7838 at 10/22/14 3:57 PM:
--
sorry about that...
org.apache.cordova.contacts 0.2.14 Contacts
Cordova CLI version: 3.6.3-0.2.13
iOS platform:
Code version: v0.10.25
Cordova version: 0.21.13
Xcode 6.0.1
Build version 6A317
was (Author: drumaboy46):
sorry about that...
Cordova CLI version: 3.6.3-0.2.13
iOS platform:
Code version: v0.10.25
Cordova version: 0.21.13
Xcode 6.0.1
Build version 6A317
Contact Picker returns -1 as the id for all contacts
Key: CB-7838
URL: https://issues.apache.org/jira/browse/CB-7838
Project: Apache Cordova
Issue Type: Bug
Components: Plugin Contacts
Affects Versions: 3.5.0
Environment: iOS
Reporter: Ralph S Theart
Can anyone confirm that the contacts plug-in returns -1 for any contact id
return from a device but it on the simulator returns a valid unique ID?
Its strange..I have ios8 devices that return -1 for any contact picked...but
the same action on the simulators returns a positive integer.
{code:title=From iOS 8 Device|borderStyle=solid}
{
id: -1,
rawId: null,
displayName: null,
name: {
givenName: Aunte,
formatted: Aunte Aline,
middleName: null,
familyName: Aline,
honorificPrefix: null,
honorificSuffix: null
},
nickname: null,
phoneNumbers: [
{
type: other,
value: 01141223***,
id: 0,
pref: false
}
],
emails: [
{
type: home,
value: vito.**@bluewin.ch,
id: 0,
pref: false
}
],.
{code}
{code:title=From ios-sim}
{
id: 7,
rawId: null,
displayName: null,
name: {
givenName: Test,
formatted: Test,
middleName: null,
familyName: null,
honorificPrefix: null,
honorificSuffix: null
},
nickname: null,
phoneNumbers: [
{
type: home,
value: (954)\u00a0646-7923,
id: 0,
pref: false
}
],
emails: null,
addresses: null,
ims: null,
organizations: null,
birthday: null,
note: null,
photos: null,
categories: null,
urls: null
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-7838) Contact Picker returns -1 as the id for all contacts
Ralph S Theart created CB-7838:
--
Summary: Contact Picker returns -1 as the id for all contacts
Key: CB-7838
URL: https://issues.apache.org/jira/browse/CB-7838
Project: Apache Cordova
Issue Type: Bug
Components: iOS, Plugin Contacts
Affects Versions: 3.5.0
Reporter: Ralph S Theart
Can anyone confirm that the contacts plug-in returns -1 for any contact id
return from a device but it on the simulator returns a valid unique ID?
Its strange..I have ios8 devices that return -1 for any contact picked...but
the same action on the simulators returns a positive integer.
{code:title=From iOS 8 Device|borderStyle=solid}
{
id: -1,
rawId: null,
displayName: null,
name: {
givenName: Aunte,
formatted: Aunte Aline,
middleName: null,
familyName: Aline,
honorificPrefix: null,
honorificSuffix: null
},
nickname: null,
phoneNumbers: [
{
type: other,
value: 01141223***,
id: 0,
pref: false
}
],
emails: [
{
type: home,
value: vito.**@bluewin.ch,
id: 0,
pref: false
}
],.
{code}
{code:title=From ios-sim}
{
id: 7,
rawId: null,
displayName: null,
name: {
givenName: Test,
formatted: Test,
middleName: null,
familyName: null,
honorificPrefix: null,
honorificSuffix: null
},
nickname: null,
phoneNumbers: [
{
type: home,
value: (954)\u00a0646-7923,
id: 0,
pref: false
}
],
emails: null,
addresses: null,
ims: null,
organizations: null,
birthday: null,
note: null,
photos: null,
categories: null,
urls: null
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-7838) Contact Picker returns -1 as the id for all contacts
[
https://issues.apache.org/jira/browse/CB-7838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14179467#comment-14179467
]
Ralph S Theart commented on CB-7838:
sorry about that...
Cordova CLI version: 3.6.3-0.2.13
iOS platform:
Code version: v0.10.25
Cordova version: 0.21.13
Xcode 6.0.1
Build version 6A317
Contact Picker returns -1 as the id for all contacts
Key: CB-7838
URL: https://issues.apache.org/jira/browse/CB-7838
Project: Apache Cordova
Issue Type: Bug
Components: Plugin Contacts
Affects Versions: 3.5.0
Environment: iOS
Reporter: Ralph S Theart
Can anyone confirm that the contacts plug-in returns -1 for any contact id
return from a device but it on the simulator returns a valid unique ID?
Its strange..I have ios8 devices that return -1 for any contact picked...but
the same action on the simulators returns a positive integer.
{code:title=From iOS 8 Device|borderStyle=solid}
{
id: -1,
rawId: null,
displayName: null,
name: {
givenName: Aunte,
formatted: Aunte Aline,
middleName: null,
familyName: Aline,
honorificPrefix: null,
honorificSuffix: null
},
nickname: null,
phoneNumbers: [
{
type: other,
value: 01141223***,
id: 0,
pref: false
}
],
emails: [
{
type: home,
value: vito.**@bluewin.ch,
id: 0,
pref: false
}
],.
{code}
{code:title=From ios-sim}
{
id: 7,
rawId: null,
displayName: null,
name: {
givenName: Test,
formatted: Test,
middleName: null,
familyName: null,
honorificPrefix: null,
honorificSuffix: null
},
nickname: null,
phoneNumbers: [
{
type: home,
value: (954)\u00a0646-7923,
id: 0,
pref: false
}
],
emails: null,
addresses: null,
ims: null,
organizations: null,
birthday: null,
note: null,
photos: null,
categories: null,
urls: null
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-7605) navigator.contacts.pickContact does not return on cancel
[
https://issues.apache.org/jira/browse/CB-7605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14170410#comment-14170410
]
Ralph S Theart commented on CB-7605:
Yes this is what is I get in the log from the contacts obj..
{code:javascript}
{
id: -1,
rawId: null,
displayName: null,
name: null,
nickname: null,
phoneNumbers: null,
emails: null,
addresses: null,
ims: null,
organizations: null,
birthday: null,
note: null,
photos: null,
categories: null,
urls: null
}
{code}
navigator.contacts.pickContact does not return on cancel
Key: CB-7605
URL: https://issues.apache.org/jira/browse/CB-7605
Project: Apache Cordova
Issue Type: Bug
Components: Plugin Contacts
Environment: Plugin version : 0.2.13
Xcode : Version 6.0.1 (6A317)
Cordova : 3.5.0-0.2.7
iOS 7.1.2
Reporter: Justin Noel
Assignee: Shazron Abdullah
Fix For: 3.7.0
Choosing the Cancel option on the contact picker fails to process either
contactSuccess or contactError callbacks.
Steps to reproduce :
Trigger contacts picker. Tap the Cancel button. App receives no callback
for a success or failure.
NOTE: When opening picker, get this exception:
{code}Exception - Name: NSRangeException Reason: *** -[__NSArrayM
objectAtIndex:]: index 0 beyond bounds for empty array{code}
After opening the picker the first time and choosing Cancel, the picker will
no longer open.
Sometimes, when opening the picker the first time or another time after
trying repeatedly, this exception shows:
{code}Warning: Attempt to present CDVContactsPicker: 0x17ecd9e0 on
MainViewController: 0x17e1dcf0 while a presentation is in progress!{code}
Sample Code:
{code:javascript}
navigator.contacts.pickContact(
function(contact){
console.log(In service. selected contact=);
console.log(contact);
selectedContact = formatContact(contact);
deferred.resolve( selectedContact );
},function(err){
console.log(Error);
console.log(err);
deferred.reject();
}
);
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-7605) navigator.contacts.pickContact does not return on cancel
[
https://issues.apache.org/jira/browse/CB-7605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14165646#comment-14165646
]
Ralph S Theart commented on CB-7605:
also confirming this issue. However for me the success call back is called on
cancelled is displays json as such:
{code:javascript}
The following contact has been
selected:{id:-1,rawId:null,displayName:null,name:null,nickname:null,phoneNumbers:null,emails:null,addresses:null,ims:null,organizations:null,birthday:null,note:null,photos:null,categories:null,urls:null}
{code}
Node version: v0.10.25
Cordova version: 0.21.13
iOS platform:
Xcode 6.0.1
Build version 6A317
Ralphs-Mac-Pro:URA_APP ralphtheart$ Node version: v0.10.25
navigator.contacts.pickContact does not return on cancel
Key: CB-7605
URL: https://issues.apache.org/jira/browse/CB-7605
Project: Apache Cordova
Issue Type: Bug
Components: Plugin Contacts
Environment: Plugin version : 0.2.13
Xcode : Version 6.0.1 (6A317)
Cordova : 3.5.0-0.2.7
iOS 7.1.2
Reporter: Justin Noel
Choosing the Cancel option on the contact picker fails to process either
contactSuccess or contactError callbacks.
Steps to reproduce :
Trigger contacts picker. Tap the Cancel button. App receives no callback
for a success or failure.
NOTE: When opening picker, get this exception:
{code}Exception - Name: NSRangeException Reason: *** -[__NSArrayM
objectAtIndex:]: index 0 beyond bounds for empty array{code}
After opening the picker the first time and choosing Cancel, the picker will
no longer open.
Sometimes, when opening the picker the first time or another time after
trying repeatedly, this exception shows:
{code}Warning: Attempt to present CDVContactsPicker: 0x17ecd9e0 on
MainViewController: 0x17e1dcf0 while a presentation is in progress!{code}
Sample Code:
{code:javascript}
navigator.contacts.pickContact(
function(contact){
console.log(In service. selected contact=);
console.log(contact);
selectedContact = formatContact(contact);
deferred.resolve( selectedContact );
},function(err){
console.log(Error);
console.log(err);
deferred.reject();
}
);
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-7605) navigator.contacts.pickContact does not return on cancel
[
https://issues.apache.org/jira/browse/CB-7605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14165710#comment-14165710
]
Ralph S Theart commented on CB-7605:
Hmm.. I see but aren't you still getting the exception...
{code}
Exception - Name: NSRangeException Reason: *** -[__NSArrayM objectAtIndex:]:
index 0 beyond bounds for empty array
{code}
At any rate your original question was about doest not return on cancel so
yes we should close.
Thanks
navigator.contacts.pickContact does not return on cancel
Key: CB-7605
URL: https://issues.apache.org/jira/browse/CB-7605
Project: Apache Cordova
Issue Type: Bug
Components: Plugin Contacts
Environment: Plugin version : 0.2.13
Xcode : Version 6.0.1 (6A317)
Cordova : 3.5.0-0.2.7
iOS 7.1.2
Reporter: Justin Noel
Choosing the Cancel option on the contact picker fails to process either
contactSuccess or contactError callbacks.
Steps to reproduce :
Trigger contacts picker. Tap the Cancel button. App receives no callback
for a success or failure.
NOTE: When opening picker, get this exception:
{code}Exception - Name: NSRangeException Reason: *** -[__NSArrayM
objectAtIndex:]: index 0 beyond bounds for empty array{code}
After opening the picker the first time and choosing Cancel, the picker will
no longer open.
Sometimes, when opening the picker the first time or another time after
trying repeatedly, this exception shows:
{code}Warning: Attempt to present CDVContactsPicker: 0x17ecd9e0 on
MainViewController: 0x17e1dcf0 while a presentation is in progress!{code}
Sample Code:
{code:javascript}
navigator.contacts.pickContact(
function(contact){
console.log(In service. selected contact=);
console.log(contact);
selectedContact = formatContact(contact);
deferred.resolve( selectedContact );
},function(err){
console.log(Error);
console.log(err);
deferred.reject();
}
);
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-7605) navigator.contacts.pickContact does not return on cancel
[
https://issues.apache.org/jira/browse/CB-7605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14165753#comment-14165753
]
Ralph S Theart commented on CB-7605:
ok thanks. Are you saying the exception is being caused by a user
error?...something in my usage of the plugin?
navigator.contacts.pickContact does not return on cancel
Key: CB-7605
URL: https://issues.apache.org/jira/browse/CB-7605
Project: Apache Cordova
Issue Type: Bug
Components: Plugin Contacts
Environment: Plugin version : 0.2.13
Xcode : Version 6.0.1 (6A317)
Cordova : 3.5.0-0.2.7
iOS 7.1.2
Reporter: Justin Noel
Fix For: 3.6.0
Choosing the Cancel option on the contact picker fails to process either
contactSuccess or contactError callbacks.
Steps to reproduce :
Trigger contacts picker. Tap the Cancel button. App receives no callback
for a success or failure.
NOTE: When opening picker, get this exception:
{code}Exception - Name: NSRangeException Reason: *** -[__NSArrayM
objectAtIndex:]: index 0 beyond bounds for empty array{code}
After opening the picker the first time and choosing Cancel, the picker will
no longer open.
Sometimes, when opening the picker the first time or another time after
trying repeatedly, this exception shows:
{code}Warning: Attempt to present CDVContactsPicker: 0x17ecd9e0 on
MainViewController: 0x17e1dcf0 while a presentation is in progress!{code}
Sample Code:
{code:javascript}
navigator.contacts.pickContact(
function(contact){
console.log(In service. selected contact=);
console.log(contact);
selectedContact = formatContact(contact);
deferred.resolve( selectedContact );
},function(err){
console.log(Error);
console.log(err);
deferred.reject();
}
);
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-7605) navigator.contacts.pickContact does not return on cancel
[
https://issues.apache.org/jira/browse/CB-7605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14165786#comment-14165786
]
Ralph S Theart commented on CB-7605:
ok thanks :}
navigator.contacts.pickContact does not return on cancel
Key: CB-7605
URL: https://issues.apache.org/jira/browse/CB-7605
Project: Apache Cordova
Issue Type: Bug
Components: Plugin Contacts
Environment: Plugin version : 0.2.13
Xcode : Version 6.0.1 (6A317)
Cordova : 3.5.0-0.2.7
iOS 7.1.2
Reporter: Justin Noel
Fix For: 3.6.0
Choosing the Cancel option on the contact picker fails to process either
contactSuccess or contactError callbacks.
Steps to reproduce :
Trigger contacts picker. Tap the Cancel button. App receives no callback
for a success or failure.
NOTE: When opening picker, get this exception:
{code}Exception - Name: NSRangeException Reason: *** -[__NSArrayM
objectAtIndex:]: index 0 beyond bounds for empty array{code}
After opening the picker the first time and choosing Cancel, the picker will
no longer open.
Sometimes, when opening the picker the first time or another time after
trying repeatedly, this exception shows:
{code}Warning: Attempt to present CDVContactsPicker: 0x17ecd9e0 on
MainViewController: 0x17e1dcf0 while a presentation is in progress!{code}
Sample Code:
{code:javascript}
navigator.contacts.pickContact(
function(contact){
console.log(In service. selected contact=);
console.log(contact);
selectedContact = formatContact(contact);
deferred.resolve( selectedContact );
},function(err){
console.log(Error);
console.log(err);
deferred.reject();
}
);
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-6617) inAppBrowser does not contain the localStorage of the parent window
[
https://issues.apache.org/jira/browse/CB-6617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14144416#comment-14144416
]
Ralph S Theart commented on CB-6617:
can any help me pass data between my trusted local files opened in inappbroswer
and the parent webview please??...if its not possible can someone just say
that?? all of a sudden this issue became unassigned and all watchers were
removed...I'm just trying to see whether or not this is possible.
inAppBrowser does not contain the localStorage of the parent window
---
Key: CB-6617
URL: https://issues.apache.org/jira/browse/CB-6617
Project: Apache Cordova
Issue Type: Bug
Components: Android, iOS, Plugin InAppBrowser
Affects Versions: 3.4.0
Reporter: Ralph S Theart
Labels: android, localstorage
Attachments: Screen Shot 2014-09-19 at 5.15.47 PM.png
Why is it that I can share localStorage information between wbeviews(I refer
to my app and a inappbrowser instance) in iOS but not in Android.
If I do...
{code}
//location: index.html (in my app)
localStorage.setItem('Cheese':'Brie');
{code}
Then if I try to retrieve this data from locally served html file via
inappbroweser in android
{code}
var item = localStorage.getItem('Cheese');
item = null
{code}
It never get set... BUT if I recompile my app and locally served html file
via inAppBroweser then it's there.
I feel like i'm missing something..
How in the world are people passing data back and forth between the app view
and the iab view?? I need to pass deep objects back and forth ...so using url
parameters is unacceptable. Neither is using inject js...as it is not
consistent in android the data does not always make it to the iab
instance and sometimes becomes undefined...I have tested this with LoadStart,
LoadStop...it's just not consistent.
iOS just works...could you help me thanks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CB-6617) inAppBrowser does not contain the localStorage of the parent window
[
https://issues.apache.org/jira/browse/CB-6617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14141060#comment-14141060
]
Ralph S Theart commented on CB-6617:
ok thats fair, let me create a brand new project and I will keep you posted.
Thanks Shazron. I'll be back hopefully by today.
inAppBrowser does not contain the localStorage of the parent window
---
Key: CB-6617
URL: https://issues.apache.org/jira/browse/CB-6617
Project: Apache Cordova
Issue Type: Bug
Components: Android, iOS, Plugin InAppBrowser
Affects Versions: 3.4.0
Reporter: Ralph S Theart
Assignee: Joe Bowser
Labels: android, localstorage
Why is it that I can share localStorage information between wbeviews(I refer
to my app and a inappbrowser instance) in iOS but not in Android.
If I do...
{code}
//location: index.html (in my app)
localStorage.setItem('Cheese':'Brie');
{code}
Then if I try to retrieve this data from locally served html file via
inappbroweser in android
{code}
var item = localStorage.getItem('Cheese');
item = null
{code}
It never get set... BUT if I recompile my app and locally served html file
via inAppBroweser then it's there.
I feel like i'm missing something..
How in the world are people passing data back and forth between the app view
and the iab view?? I need to pass deep objects back and forth ...so using url
parameters is unacceptable. Neither is using inject js...as it is not
consistent in android the data does not always make it to the iab
instance and sometimes becomes undefined...I have tested this with LoadStart,
LoadStop...it's just not consistent.
iOS just works...could you help me thanks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CB-6617) inAppBrowser does not contain the localStorage of the parent window
[
https://issues.apache.org/jira/browse/CB-6617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14141241#comment-14141241
]
Ralph S Theart commented on CB-6617:
ok all updated... I tried..
urapp.loadUrlInApp(cordova.file.applicationDirectory+'/www/pages/test.html');
{code}
html
head
/head
body onload=urapp.initialize()
h3Cordova Test/h3
script type=text/javascript src=../../cordova.js/script
script type=text/javascript
var urapp = {
// Application Constructor
initialize: function() {
this.bindEvents();
},
// Bind Event Listeners
//
// Bind any events that are required on startup. Common events are:
// 'load', 'deviceready', 'offline', and 'online'.
bindEvents: function() {
document.addEventListener('deviceready', this.onDeviceReady,
false);
},
// deviceready Event Handler
//
// The scope of 'this' is the event. In order to call the
'receivedEvent'
// function, we must explicity call 'app.receivedEvent(...);'
onDeviceReady: function() {
alert('ready');
}
}
/script
/body
/html
{code}
the alert never fires...is my codova.js path mess up or something... I even
tried script type=text/javascript src=cordova.js/script but still
nothing. thanks for your help.
inAppBrowser does not contain the localStorage of the parent window
---
Key: CB-6617
URL: https://issues.apache.org/jira/browse/CB-6617
Project: Apache Cordova
Issue Type: Bug
Components: Android, iOS, Plugin InAppBrowser
Affects Versions: 3.4.0
Reporter: Ralph S Theart
Assignee: Joe Bowser
Labels: android, localstorage
Why is it that I can share localStorage information between wbeviews(I refer
to my app and a inappbrowser instance) in iOS but not in Android.
If I do...
{code}
//location: index.html (in my app)
localStorage.setItem('Cheese':'Brie');
{code}
Then if I try to retrieve this data from locally served html file via
inappbroweser in android
{code}
var item = localStorage.getItem('Cheese');
item = null
{code}
It never get set... BUT if I recompile my app and locally served html file
via inAppBroweser then it's there.
I feel like i'm missing something..
How in the world are people passing data back and forth between the app view
and the iab view?? I need to pass deep objects back and forth ...so using url
parameters is unacceptable. Neither is using inject js...as it is not
consistent in android the data does not always make it to the iab
instance and sometimes becomes undefined...I have tested this with LoadStart,
LoadStop...it's just not consistent.
iOS just works...could you help me thanks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CB-6617) inAppBrowser does not contain the localStorage of the parent window
[
https://issues.apache.org/jira/browse/CB-6617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14141275#comment-14141275
]
Ralph S Theart commented on CB-6617:
using _blank with IAB btw
inAppBrowser does not contain the localStorage of the parent window
---
Key: CB-6617
URL: https://issues.apache.org/jira/browse/CB-6617
Project: Apache Cordova
Issue Type: Bug
Components: Android, iOS, Plugin InAppBrowser
Affects Versions: 3.4.0
Reporter: Ralph S Theart
Assignee: Joe Bowser
Labels: android, localstorage
Why is it that I can share localStorage information between wbeviews(I refer
to my app and a inappbrowser instance) in iOS but not in Android.
If I do...
{code}
//location: index.html (in my app)
localStorage.setItem('Cheese':'Brie');
{code}
Then if I try to retrieve this data from locally served html file via
inappbroweser in android
{code}
var item = localStorage.getItem('Cheese');
item = null
{code}
It never get set... BUT if I recompile my app and locally served html file
via inAppBroweser then it's there.
I feel like i'm missing something..
How in the world are people passing data back and forth between the app view
and the iab view?? I need to pass deep objects back and forth ...so using url
parameters is unacceptable. Neither is using inject js...as it is not
consistent in android the data does not always make it to the iab
instance and sometimes becomes undefined...I have tested this with LoadStart,
LoadStop...it's just not consistent.
iOS just works...could you help me thanks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CB-6617) inAppBrowser does not contain the localStorage of the parent window
[
https://issues.apache.org/jira/browse/CB-6617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14141305#comment-14141305
]
Ralph S Theart commented on CB-6617:
ok my js path was wrong...still testing
inAppBrowser does not contain the localStorage of the parent window
---
Key: CB-6617
URL: https://issues.apache.org/jira/browse/CB-6617
Project: Apache Cordova
Issue Type: Bug
Components: Android, iOS, Plugin InAppBrowser
Affects Versions: 3.4.0
Reporter: Ralph S Theart
Assignee: Joe Bowser
Labels: android, localstorage
Why is it that I can share localStorage information between wbeviews(I refer
to my app and a inappbrowser instance) in iOS but not in Android.
If I do...
{code}
//location: index.html (in my app)
localStorage.setItem('Cheese':'Brie');
{code}
Then if I try to retrieve this data from locally served html file via
inappbroweser in android
{code}
var item = localStorage.getItem('Cheese');
item = null
{code}
It never get set... BUT if I recompile my app and locally served html file
via inAppBroweser then it's there.
I feel like i'm missing something..
How in the world are people passing data back and forth between the app view
and the iab view?? I need to pass deep objects back and forth ...so using url
parameters is unacceptable. Neither is using inject js...as it is not
consistent in android the data does not always make it to the iab
instance and sometimes becomes undefined...I have tested this with LoadStart,
LoadStop...it's just not consistent.
iOS just works...could you help me thanks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CB-6617) inAppBrowser does not contain the localStorage of the parent window
[
https://issues.apache.org/jira/browse/CB-6617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14141317#comment-14141317
]
Ralph S Theart commented on CB-6617:
close but I think I'm missing something...
{code}
//IAB
html
head
link href=../css/inAppBrowser.css rel=stylesheet type=text/css
/head
body onload=urapp.initialize()
h3Cordova Test/h3
a style=font-size:100px
onclick=navigator.notification.alert('boss');TEST THIS!/a
script type=text/javascript src=../cordova.js/script
script type=text/javascript
window.onerror = function(message, url, lineNumber) {
parseUrl = location.search.match(/[^/]+$/g);
UrlParts = parseUrl[0].split('?');
FileName = UrlParts[0];
alert(Error: +message+ in +FileName+ at line +lineNumber);
}
var urapp = {
// Application Constructor
initialize: function() {
urapp.bindEvents();
},
// Bind Event Listeners
//
// Bind any events that are required on startup. Common events are:
// 'load', 'deviceready', 'offline', and 'online'.
bindEvents: function() {
//alert('binding');
document.addEventListener('deviceready', urapp.onDeviceReady,
false);
},
// deviceready Event Handler
//
// The scope of 'this' is the event. In order to call the
'receivedEvent'
// function, we must explicity call 'app.receivedEvent(...);'
onDeviceReady: function() {
alert('ready');
}
}
/script
/body
/html
{code}
alert never gets called even though cordova is loading in the IAB ...you can
see the pick that shows it.
inAppBrowser does not contain the localStorage of the parent window
---
Key: CB-6617
URL: https://issues.apache.org/jira/browse/CB-6617
Project: Apache Cordova
Issue Type: Bug
Components: Android, iOS, Plugin InAppBrowser
Affects Versions: 3.4.0
Reporter: Ralph S Theart
Assignee: Joe Bowser
Labels: android, localstorage
Why is it that I can share localStorage information between wbeviews(I refer
to my app and a inappbrowser instance) in iOS but not in Android.
If I do...
{code}
//location: index.html (in my app)
localStorage.setItem('Cheese':'Brie');
{code}
Then if I try to retrieve this data from locally served html file via
inappbroweser in android
{code}
var item = localStorage.getItem('Cheese');
item = null
{code}
It never get set... BUT if I recompile my app and locally served html file
via inAppBroweser then it's there.
I feel like i'm missing something..
How in the world are people passing data back and forth between the app view
and the iab view?? I need to pass deep objects back and forth ...so using url
parameters is unacceptable. Neither is using inject js...as it is not
consistent in android the data does not always make it to the iab
instance and sometimes becomes undefined...I have tested this with LoadStart,
LoadStop...it's just not consistent.
iOS just works...could you help me thanks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CB-6617) inAppBrowser does not contain the localStorage of the parent window
[
https://issues.apache.org/jira/browse/CB-6617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph S Theart updated CB-6617:
---
Attachment: Screen Shot 2014-09-19 at 5.15.47 PM.png
inAppBrowser does not contain the localStorage of the parent window
---
Key: CB-6617
URL: https://issues.apache.org/jira/browse/CB-6617
Project: Apache Cordova
Issue Type: Bug
Components: Android, iOS, Plugin InAppBrowser
Affects Versions: 3.4.0
Reporter: Ralph S Theart
Assignee: Joe Bowser
Labels: android, localstorage
Attachments: Screen Shot 2014-09-19 at 5.15.47 PM.png
Why is it that I can share localStorage information between wbeviews(I refer
to my app and a inappbrowser instance) in iOS but not in Android.
If I do...
{code}
//location: index.html (in my app)
localStorage.setItem('Cheese':'Brie');
{code}
Then if I try to retrieve this data from locally served html file via
inappbroweser in android
{code}
var item = localStorage.getItem('Cheese');
item = null
{code}
It never get set... BUT if I recompile my app and locally served html file
via inAppBroweser then it's there.
I feel like i'm missing something..
How in the world are people passing data back and forth between the app view
and the iab view?? I need to pass deep objects back and forth ...so using url
parameters is unacceptable. Neither is using inject js...as it is not
consistent in android the data does not always make it to the iab
instance and sometimes becomes undefined...I have tested this with LoadStart,
LoadStop...it's just not consistent.
iOS just works...could you help me thanks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CB-6617) inAppBrowser does not contain the localStorage of the parent window
[
https://issues.apache.org/jira/browse/CB-6617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14139966#comment-14139966
]
Ralph S Theart commented on CB-6617:
any news just wanted to know ...I've been trying to use the File API to get the
full resolved url but its not workingcould you let me know how you tested
this..thanks.
inAppBrowser does not contain the localStorage of the parent window
---
Key: CB-6617
URL: https://issues.apache.org/jira/browse/CB-6617
Project: Apache Cordova
Issue Type: Bug
Components: Android, iOS, Plugin InAppBrowser
Affects Versions: 3.4.0
Reporter: Ralph S Theart
Assignee: Joe Bowser
Labels: android, localstorage
Why is it that I can share localStorage information between wbeviews(I refer
to my app and a inappbrowser instance) in iOS but not in Android.
If I do...
{code}
//location: index.html (in my app)
localStorage.setItem('Cheese':'Brie');
{code}
Then if I try to retrieve this data from locally served html file via
inappbroweser in android
{code}
var item = localStorage.getItem('Cheese');
item = null
{code}
It never get set... BUT if I recompile my app and locally served html file
via inAppBroweser then it's there.
I feel like i'm missing something..
How in the world are people passing data back and forth between the app view
and the iab view?? I need to pass deep objects back and forth ...so using url
parameters is unacceptable. Neither is using inject js...as it is not
consistent in android the data does not always make it to the iab
instance and sometimes becomes undefined...I have tested this with LoadStart,
LoadStop...it's just not consistent.
iOS just works...could you help me thanks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CB-6617) inAppBrowser does not contain the localStorage of the parent window
[
https://issues.apache.org/jira/browse/CB-6617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14135846#comment-14135846
]
Ralph S Theart commented on CB-6617:
Hey Shazron I know it's been a while...just wanted to be sure I understood what
you were saying ...are saying I should be able to use cordova.js in IAB? how? I
tried app.loadUrlInApp('file://pages/someFile.html'); and it throws
exception...sorry if I'm confused.
{code}
-[__NSCFString charValue]: unrecognized selector sent to instance 0xbe8e340
2014-09-16 14:02:38.458 URA[21516:70b] *** WebKit discarded an uncaught
exception in the
webView:decidePolicyForNavigationAction:request:frame:decisionListener:
delegate: NSInvalidArgumentException -[__NSCFString charValue]: unrecognized
selector sent to instance 0xbe8e340
{code}
inAppBrowser does not contain the localStorage of the parent window
---
Key: CB-6617
URL: https://issues.apache.org/jira/browse/CB-6617
Project: Apache Cordova
Issue Type: Bug
Components: Android, iOS, Plugin InAppBrowser
Affects Versions: 3.4.0
Reporter: Ralph S Theart
Assignee: Joe Bowser
Labels: android, localstorage
Why is it that I can share localStorage information between wbeviews(I refer
to my app and a inappbrowser instance) in iOS but not in Android.
If I do...
{code}
//location: index.html (in my app)
localStorage.setItem('Cheese':'Brie');
{code}
Then if I try to retrieve this data from locally served html file via
inappbroweser in android
{code}
var item = localStorage.getItem('Cheese');
item = null
{code}
It never get set... BUT if I recompile my app and locally served html file
via inAppBroweser then it's there.
I feel like i'm missing something..
How in the world are people passing data back and forth between the app view
and the iab view?? I need to pass deep objects back and forth ...so using url
parameters is unacceptable. Neither is using inject js...as it is not
consistent in android the data does not always make it to the iab
instance and sometimes becomes undefined...I have tested this with LoadStart,
LoadStop...it's just not consistent.
iOS just works...could you help me thanks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (CB-6617) inAppBrowser does not contain the localStorage of the parent window
[
https://issues.apache.org/jira/browse/CB-6617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14135846#comment-14135846
]
Ralph S Theart edited comment on CB-6617 at 9/16/14 6:48 PM:
-
Hey Shazron I know it's been a while...just wanted to be sure I understood what
you were saying ...are saying I should be able to use cordova.js in IAB? how? I
tried app.loadUrlInApp('file://pages/someFile.html'); and it throws
exception...sorry if I'm confused.
{code}
-[__NSCFString charValue]: unrecognized selector sent to instance 0xbe8e340
2014-09-16 14:02:38.458 URA[21516:70b] *** WebKit discarded an uncaught
exception in the
webView:decidePolicyForNavigationAction:request:frame:decisionListener:
delegate: NSInvalidArgumentException -[__NSCFString charValue]: unrecognized
selector sent to instance 0xbe8e340
{code}
*EDIT*
The error above is related to something else but I still can't get this to
work. How can I used cordova.js within IAB??
was (Author: drumaboy46):
Hey Shazron I know it's been a while...just wanted to be sure I understood what
you were saying ...are saying I should be able to use cordova.js in IAB? how? I
tried app.loadUrlInApp('file://pages/someFile.html'); and it throws
exception...sorry if I'm confused.
{code}
-[__NSCFString charValue]: unrecognized selector sent to instance 0xbe8e340
2014-09-16 14:02:38.458 URA[21516:70b] *** WebKit discarded an uncaught
exception in the
webView:decidePolicyForNavigationAction:request:frame:decisionListener:
delegate: NSInvalidArgumentException -[__NSCFString charValue]: unrecognized
selector sent to instance 0xbe8e340
{code}
inAppBrowser does not contain the localStorage of the parent window
---
Key: CB-6617
URL: https://issues.apache.org/jira/browse/CB-6617
Project: Apache Cordova
Issue Type: Bug
Components: Android, iOS, Plugin InAppBrowser
Affects Versions: 3.4.0
Reporter: Ralph S Theart
Assignee: Joe Bowser
Labels: android, localstorage
Why is it that I can share localStorage information between wbeviews(I refer
to my app and a inappbrowser instance) in iOS but not in Android.
If I do...
{code}
//location: index.html (in my app)
localStorage.setItem('Cheese':'Brie');
{code}
Then if I try to retrieve this data from locally served html file via
inappbroweser in android
{code}
var item = localStorage.getItem('Cheese');
item = null
{code}
It never get set... BUT if I recompile my app and locally served html file
via inAppBroweser then it's there.
I feel like i'm missing something..
How in the world are people passing data back and forth between the app view
and the iab view?? I need to pass deep objects back and forth ...so using url
parameters is unacceptable. Neither is using inject js...as it is not
consistent in android the data does not always make it to the iab
instance and sometimes becomes undefined...I have tested this with LoadStart,
LoadStop...it's just not consistent.
iOS just works...could you help me thanks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CB-6617) inAppBrowser does not contain the localStorage of the parent window
[
https://issues.apache.org/jira/browse/CB-6617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13996021#comment-13996021
]
Ralph S Theart commented on CB-6617:
ok sorry but could you help be understand the security risk from pulling up a
file from within my on application using file://...? I'm unsure of the
risk...sorry noobness.
inAppBrowser does not contain the localStorage of the parent window
---
Key: CB-6617
URL: https://issues.apache.org/jira/browse/CB-6617
Project: Apache Cordova
Issue Type: Bug
Components: Android, iOS, Plugin InAppBrowser
Affects Versions: 3.4.0
Reporter: Ralph S Theart
Assignee: Joe Bowser
Labels: android, localstorage
Why is it that I can share localStorage information between wbeviews(I refer
to my app and a inappbrowser instance) in iOS but not in Android.
If I do...
{code}
//location: index.html (in my app)
localStorage.setItem('Cheese':'Brie');
{code}
Then if I try to retrieve this data from locally served html file via
inappbroweser in android
{code}
var item = localStorage.getItem('Cheese');
item = null
{code}
It never get set... BUT if I recompile my app and locally served html file
via inAppBroweser then it's there.
I feel like i'm missing something..
How in the world are people passing data back and forth between the app view
and the iab view?? I need to pass deep objects back and forth ...so using url
parameters is unacceptable. Neither is using inject js...as it is not
consistent in android the data does not always make it to the iab
instance and sometimes becomes undefined...I have tested this with LoadStart,
LoadStop...it's just not consistent.
iOS just works...could you help me thanks.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (CB-6617) inAppBrowser does not contain the localStorage of the parent window
Ralph S Theart created CB-6617:
--
Summary: inAppBrowser does not contain the localStorage of the
parent window
Key: CB-6617
URL: https://issues.apache.org/jira/browse/CB-6617
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin InAppBrowser
Affects Versions: 3.4.0
Reporter: Ralph S Theart
Why is it that I can share localStorage information between wbeviews(I refer to
my app and a inappbrowser instance) in iOS but not in Android.
If I do...
{code}
//location: index.html (in my app)
localStorage.setItem('Cheese':'Brie');
{code}
Then if I try to retrieve this data from locally served html file via
inappbroweser in android
{code}
var item = localStorage.getItem('Cheese');
item = null
{code}
It never get set... BUT if I recompile my app and locally served html file via
inAppBroweser then it's there.
I feel like i'm missing something..
How in the world are people passing data back and forth between the app view
and the iab view?? I need to pass deep objects back and forth ...so using url
parameters is unacceptable. Neither is using inject js...as it is not
consistent in android the data does not always make it to the iab instance
and sometimes becomes undefined...I have tested this with LoadStart,
LoadStop...it's just not consistent.
iOS just works...could you help me thanks.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6249) Camera fails to return an actual FILE_URI it always returns content://
[
https://issues.apache.org/jira/browse/CB-6249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13960171#comment-13960171
]
Ralph S Theart commented on CB-6249:
ok will do.
Camera fails to return an actual FILE_URI it always returns content://
--
Key: CB-6249
URL: https://issues.apache.org/jira/browse/CB-6249
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin Camera, Plugin File
Affects Versions: 3.4.0
Environment: Current Node Version
v0.10.25
Current Cordova CLI Version
3.4.0-0.1.0
Android
Reporter: Ralph S Theart
Assignee: Ian Clelland
Labels: camera, file
No matter what I do I can not get a url of file:///... all I get is
{code}
content://media/external/images/media/1357
{code}
Here is my very simple code
{code}
navigator.camera.getPicture(function(imageURI){
console.log('GOT IMAGE: '+imageURI);
window.resolveLocalFileSystemURL(imageURI, function(entry){
console.log(entry.name + +entry.fullPath);
}, function(e){
console.log('Some error occured: '+e.code);
});
}, onPhotoFail, {
destinationType: 1,
sourceType: pictureSource,
mediaType : Camera.MediaType.ALLMEDIA,
encodingType: 0,
allowEdit : false,
correctOrientation:true,
saveToPhotoAlbum: false,
quality: 50
});
{code}
I always get content://... for the returned path from camera and even the
same thing when I resolve the url. Can you confirm this bug?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6359) resolveLocalFileSystemURL continues to be inconsistent, now fails specifically on Galaxy Note 3 when capturing video only
[
https://issues.apache.org/jira/browse/CB-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13959100#comment-13959100
]
Ralph S Theart commented on CB-6359:
Great work Ian thanks a lot!
resolveLocalFileSystemURL continues to be inconsistent, now fails
specifically on Galaxy Note 3 when capturing video only
-
Key: CB-6359
URL: https://issues.apache.org/jira/browse/CB-6359
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin File, Plugin Media Capture
Affects Versions: 3.4.0
Environment: On Mac
Cordova info
Current Node Version
v0.10.25
Current Cordova CLI Version
3.4.0-0.1.0
Testing with: Samsung Galaxy Note 3 (Android)...the device is NOT rooted.
Reporter: Ralph S Theart
Assignee: Ian Clelland
Labels: android, capture
Ok this is a very strange bug. Some background first though. I have 10 test
devices at my house so I can test the apps I make. Of the 10 devices 8 are
android. My app works across the board on all of them flawlessly. So I
already know its not something related to my set up or my code. Out of the
*10* devices one specific feature seems to fail on one specific device
(Galaxy Note 3). When you capture video and try to resolve the URI you will
always get error core 5 every single time no matter what changes you make or
conditions. Here is the code.
{code}
navigator.device.capture.captureVideo(function(mediaFiles){
var mediaFilePath = mediaFiles[0].fullPath;
window.resolveLocalFileSystemURL(mediaFilePath, function(){
///never gets this far
}, function(error){
console.log(error.code);
*Always fails with error code 5*
});
}, function(error){
var msg = 'Messages captureVideo():: An error
occurred during video capture: ' + error.code;
console.log(msg, null, 'Uh oh!');
});
{code}
For this device and this specific scenario the path returned by capture is
always something like this:
*file:/storage/extSdCard/DCIM/Camera/20140327_104747.mp4* yes I noticed
the file:/ and have even tried replacing it with file:/// and it still
continues to fail.
btw ...I have a lot of devices I test with with...do you guys have these kind
of facilities? I have built up a rigorous excel sheet full of tests among
which are all of the media type api's. I did this because
resolveLocalFileSystemURL has become a problem child for me since 3.4 I have
already submitted 3 bugs 1 of which was solved and actually made it to the
1.0.1 File-System update. The 2nd one is solved now too. I wouldn't care if
the device this was happening to was old and was on an older firmware like
4.0.3 but this is a popular device especially in our database any help would
be appreciated.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6359) resolveLocalFileSystemURL continues to be inconsistent, now fails specifically on Galaxy Note 3 when capturing video only
[
https://issues.apache.org/jira/browse/CB-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13950666#comment-13950666
]
Ralph S Theart commented on CB-6359:
It worked I was missing root in that list for AndroidExtraFilesystems.
Thanks! 10 for 10 now :}
resolveLocalFileSystemURL continues to be inconsistent, now fails
specifically on Galaxy Note 3 when capturing video only
-
Key: CB-6359
URL: https://issues.apache.org/jira/browse/CB-6359
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin File, Plugin Media Capture
Affects Versions: 3.4.0
Environment: On Mac
Cordova info
Current Node Version
v0.10.25
Current Cordova CLI Version
3.4.0-0.1.0
Testing with: Samsung Galaxy Note 3 (Android)...the device is NOT rooted.
Reporter: Ralph S Theart
Assignee: Ian Clelland
Labels: android, capture
Ok this is a very strange bug. Some background first though. I have 10 test
devices at my house so I can test the apps I make. Of the 10 devices 8 are
android. My app works across the board on all of them flawlessly. So I
already know its not something related to my set up or my code. Out of the
*10* devices one specific feature seems to fail on one specific device
(Galaxy Note 3). When you capture video and try to resolve the URI you will
always get error core 5 every single time no matter what changes you make or
conditions. Here is the code.
{code}
navigator.device.capture.captureVideo(function(mediaFiles){
var mediaFilePath = mediaFiles[0].fullPath;
window.resolveLocalFileSystemURL(mediaFilePath, function(){
///never gets this far
}, function(error){
console.log(error.code);
*Always fails with error code 5*
});
}, function(error){
var msg = 'Messages captureVideo():: An error
occurred during video capture: ' + error.code;
console.log(msg, null, 'Uh oh!');
});
{code}
For this device and this specific scenario the path returned by capture is
always something like this:
*file:/storage/extSdCard/DCIM/Camera/20140327_104747.mp4* yes I noticed
the file:/ and have even tried replacing it with file:/// and it still
continues to fail.
btw ...I have a lot of devices I test with with...do you guys have these kind
of facilities? I have built up a rigorous excel sheet full of tests among
which are all of the media type api's. I did this because
resolveLocalFileSystemURL has become a problem child for me since 3.4 I have
already submitted 3 bugs 1 of which was solved and actually made it to the
1.0.1 File-System update. The 2nd one is solved now too. I wouldn't care if
the device this was happening to was old and was on an older firmware like
4.0.3 but this is a popular device especially in our database any help would
be appreciated.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6359) resolveLocalFileSystemURL continues to be inconsistent, now fails specifically on Galaxy Note 3 when capturing video only
[
https://issues.apache.org/jira/browse/CB-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13950692#comment-13950692
]
Ralph S Theart commented on CB-6359:
Agreed and thanks again.
resolveLocalFileSystemURL continues to be inconsistent, now fails
specifically on Galaxy Note 3 when capturing video only
-
Key: CB-6359
URL: https://issues.apache.org/jira/browse/CB-6359
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin File, Plugin Media Capture
Affects Versions: 3.4.0
Environment: On Mac
Cordova info
Current Node Version
v0.10.25
Current Cordova CLI Version
3.4.0-0.1.0
Testing with: Samsung Galaxy Note 3 (Android)...the device is NOT rooted.
Reporter: Ralph S Theart
Assignee: Ian Clelland
Labels: android, capture
Ok this is a very strange bug. Some background first though. I have 10 test
devices at my house so I can test the apps I make. Of the 10 devices 8 are
android. My app works across the board on all of them flawlessly. So I
already know its not something related to my set up or my code. Out of the
*10* devices one specific feature seems to fail on one specific device
(Galaxy Note 3). When you capture video and try to resolve the URI you will
always get error core 5 every single time no matter what changes you make or
conditions. Here is the code.
{code}
navigator.device.capture.captureVideo(function(mediaFiles){
var mediaFilePath = mediaFiles[0].fullPath;
window.resolveLocalFileSystemURL(mediaFilePath, function(){
///never gets this far
}, function(error){
console.log(error.code);
*Always fails with error code 5*
});
}, function(error){
var msg = 'Messages captureVideo():: An error
occurred during video capture: ' + error.code;
console.log(msg, null, 'Uh oh!');
});
{code}
For this device and this specific scenario the path returned by capture is
always something like this:
*file:/storage/extSdCard/DCIM/Camera/20140327_104747.mp4* yes I noticed
the file:/ and have even tried replacing it with file:/// and it still
continues to fail.
btw ...I have a lot of devices I test with with...do you guys have these kind
of facilities? I have built up a rigorous excel sheet full of tests among
which are all of the media type api's. I did this because
resolveLocalFileSystemURL has become a problem child for me since 3.4 I have
already submitted 3 bugs 1 of which was solved and actually made it to the
1.0.1 File-System update. The 2nd one is solved now too. I wouldn't care if
the device this was happening to was old and was on an older firmware like
4.0.3 but this is a popular device especially in our database any help would
be appreciated.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6359) resolveLocalFileSystemURL continues to be inconsistent, now fails specifically on Galaxy Note 3 when capturing video only
[
https://issues.apache.org/jira/browse/CB-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13949707#comment-13949707
]
Ralph S Theart commented on CB-6359:
sure should I rm the current file system plugin first before installing
org.apache.cordova.file-system-roots?
resolveLocalFileSystemURL continues to be inconsistent, now fails
specifically on Galaxy Note 3 when capturing video only
-
Key: CB-6359
URL: https://issues.apache.org/jira/browse/CB-6359
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin File, Plugin Media Capture
Affects Versions: 3.4.0
Environment: On Mac
Cordova info
Current Node Version
v0.10.25
Current Cordova CLI Version
3.4.0-0.1.0
Testing with: Samsung Galaxy Note 3 (Android)...the device is NOT rooted.
Reporter: Ralph S Theart
Assignee: Ian Clelland
Labels: android, capture
Ok this is a very strange bug. Some background first though. I have 10 test
devices at my house so I can test the apps I make. Of the 10 devices 8 are
android. My app works across the board on all of them flawlessly. So I
already know its not something related to my set up or my code. Out of the
*10* devices one specific feature seems to fail on one specific device
(Galaxy Note 3). When you capture video and try to resolve the URI you will
always get error core 5 every single time no matter what changes you make or
conditions. Here is the code.
{code}
navigator.device.capture.captureVideo(function(mediaFiles){
var mediaFilePath = mediaFiles[0].fullPath;
window.resolveLocalFileSystemURL(mediaFilePath, function(){
///never gets this far
}, function(error){
console.log(error.code);
*Always fails with error code 5*
});
}, function(error){
var msg = 'Messages captureVideo():: An error
occurred during video capture: ' + error.code;
console.log(msg, null, 'Uh oh!');
});
{code}
For this device and this specific scenario the path returned by capture is
always something like this:
*file:/storage/extSdCard/DCIM/Camera/20140327_104747.mp4* yes I noticed
the file:/ and have even tried replacing it with file:/// and it still
continues to fail.
btw ...I have a lot of devices I test with with...do you guys have these kind
of facilities. I'm more than happy to help with any testing...I built up a
rigorous excel sheet full of tests among which are all of the media type
api's. I did this because resolveLocalFileSystemURL has become a problem
child for me since 3.4 I have already submitted 3 bugs 1 of which was solved
and actually made it to the 1.0.1 File-System update. The 2nd one is solved
now too. I wouldn't care if the device this was happening to was old and was
on an older firmware like 4.0.3 but this is a popular device especially in
our database any help would be appreciated.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6359) resolveLocalFileSystemURL continues to be inconsistent, now fails specifically on Galaxy Note 3 when capturing video only
[
https://issues.apache.org/jira/browse/CB-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13949747#comment-13949747
]
Ralph S Theart commented on CB-6359:
ok maybe I missed something but media capture continues to return
file:/storage/extSdCard/DCIM/Camera/20140327_141754.mp4 may be I missed a step?
resolveLocalFileSystemURL continues to be inconsistent, now fails
specifically on Galaxy Note 3 when capturing video only
-
Key: CB-6359
URL: https://issues.apache.org/jira/browse/CB-6359
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin File, Plugin Media Capture
Affects Versions: 3.4.0
Environment: On Mac
Cordova info
Current Node Version
v0.10.25
Current Cordova CLI Version
3.4.0-0.1.0
Testing with: Samsung Galaxy Note 3 (Android)...the device is NOT rooted.
Reporter: Ralph S Theart
Assignee: Ian Clelland
Labels: android, capture
Ok this is a very strange bug. Some background first though. I have 10 test
devices at my house so I can test the apps I make. Of the 10 devices 8 are
android. My app works across the board on all of them flawlessly. So I
already know its not something related to my set up or my code. Out of the
*10* devices one specific feature seems to fail on one specific device
(Galaxy Note 3). When you capture video and try to resolve the URI you will
always get error core 5 every single time no matter what changes you make or
conditions. Here is the code.
{code}
navigator.device.capture.captureVideo(function(mediaFiles){
var mediaFilePath = mediaFiles[0].fullPath;
window.resolveLocalFileSystemURL(mediaFilePath, function(){
///never gets this far
}, function(error){
console.log(error.code);
*Always fails with error code 5*
});
}, function(error){
var msg = 'Messages captureVideo():: An error
occurred during video capture: ' + error.code;
console.log(msg, null, 'Uh oh!');
});
{code}
For this device and this specific scenario the path returned by capture is
always something like this:
*file:/storage/extSdCard/DCIM/Camera/20140327_104747.mp4* yes I noticed
the file:/ and have even tried replacing it with file:/// and it still
continues to fail.
btw ...I have a lot of devices I test with with...do you guys have these kind
of facilities. I'm more than happy to help with any testing...I built up a
rigorous excel sheet full of tests among which are all of the media type
api's. I did this because resolveLocalFileSystemURL has become a problem
child for me since 3.4 I have already submitted 3 bugs 1 of which was solved
and actually made it to the 1.0.1 File-System update. The 2nd one is solved
now too. I wouldn't care if the device this was happening to was old and was
on an older firmware like 4.0.3 but this is a popular device especially in
our database any help would be appreciated.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6359) resolveLocalFileSystemURL continues to be inconsistent, now fails specifically on Galaxy Note 3 when capturing video only
[
https://issues.apache.org/jira/browse/CB-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13949808#comment-13949808
]
Ralph S Theart commented on CB-6359:
no it continues to fail with
{code}
window.resolveLocalFileSystemURL(file:///storage/extSdCard/DCIM/Camera/20140327_141754.mp4,function(){
//never gets here
},function(){
//continues to fail error
Error Coede: (5) Error Message: Unknown Error
});
{code}
anything I have to add in the cofig.xml file?
do I have to call window.resolveLocalFileSystemURL() another way?
resolveLocalFileSystemURL continues to be inconsistent, now fails
specifically on Galaxy Note 3 when capturing video only
-
Key: CB-6359
URL: https://issues.apache.org/jira/browse/CB-6359
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin File, Plugin Media Capture
Affects Versions: 3.4.0
Environment: On Mac
Cordova info
Current Node Version
v0.10.25
Current Cordova CLI Version
3.4.0-0.1.0
Testing with: Samsung Galaxy Note 3 (Android)...the device is NOT rooted.
Reporter: Ralph S Theart
Assignee: Ian Clelland
Labels: android, capture
Ok this is a very strange bug. Some background first though. I have 10 test
devices at my house so I can test the apps I make. Of the 10 devices 8 are
android. My app works across the board on all of them flawlessly. So I
already know its not something related to my set up or my code. Out of the
*10* devices one specific feature seems to fail on one specific device
(Galaxy Note 3). When you capture video and try to resolve the URI you will
always get error core 5 every single time no matter what changes you make or
conditions. Here is the code.
{code}
navigator.device.capture.captureVideo(function(mediaFiles){
var mediaFilePath = mediaFiles[0].fullPath;
window.resolveLocalFileSystemURL(mediaFilePath, function(){
///never gets this far
}, function(error){
console.log(error.code);
*Always fails with error code 5*
});
}, function(error){
var msg = 'Messages captureVideo():: An error
occurred during video capture: ' + error.code;
console.log(msg, null, 'Uh oh!');
});
{code}
For this device and this specific scenario the path returned by capture is
always something like this:
*file:/storage/extSdCard/DCIM/Camera/20140327_104747.mp4* yes I noticed
the file:/ and have even tried replacing it with file:/// and it still
continues to fail.
btw ...I have a lot of devices I test with with...do you guys have these kind
of facilities. I'm more than happy to help with any testing...I built up a
rigorous excel sheet full of tests among which are all of the media type
api's. I did this because resolveLocalFileSystemURL has become a problem
child for me since 3.4 I have already submitted 3 bugs 1 of which was solved
and actually made it to the 1.0.1 File-System update. The 2nd one is solved
now too. I wouldn't care if the device this was happening to was old and was
on an older firmware like 4.0.3 but this is a popular device especially in
our database any help would be appreciated.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (CB-6359) resolveLocalFileSystemURL continues to be inconsistent, now fails specifically on Galaxy Note 3 when capturing video only
[
https://issues.apache.org/jira/browse/CB-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph S Theart updated CB-6359:
---
Description:
Ok this is a very strange bug. Some background first though. I have 10 test
devices at my house so I can test the apps I make. Of the 10 devices 8 are
android. My app works across the board on all of them flawlessly. So I already
know its not something related to my set up or my code. Out of the *10* devices
one specific feature seems to fail on one specific device (Galaxy Note 3). When
you capture video and try to resolve the URI you will always get error core 5
every single time no matter what changes you make or conditions. Here is the
code.
{code}
navigator.device.capture.captureVideo(function(mediaFiles){
var mediaFilePath = mediaFiles[0].fullPath;
window.resolveLocalFileSystemURL(mediaFilePath, function(){
///never gets this far
}, function(error){
console.log(error.code);
*Always fails with error code 5*
});
}, function(error){
var msg = 'Messages captureVideo():: An error
occurred during video capture: ' + error.code;
console.log(msg, null, 'Uh oh!');
});
{code}
For this device and this specific scenario the path returned by capture is
always something like this:
*file:/storage/extSdCard/DCIM/Camera/20140327_104747.mp4* yes I noticed the
file:/ and have even tried replacing it with file:/// and it still
continues to fail.
btw ...I have a lot of devices I test with with...do you guys have these kind
of facilities? I have built up a rigorous excel sheet full of tests among which
are all of the media type api's. I did this because resolveLocalFileSystemURL
has become a problem child for me since 3.4 I have already submitted 3 bugs 1
of which was solved and actually made it to the 1.0.1 File-System update. The
2nd one is solved now too. I wouldn't care if the device this was happening to
was old and was on an older firmware like 4.0.3 but this is a popular device
especially in our database any help would be appreciated.
was:
Ok this is a very strange bug. Some background first though. I have 10 test
devices at my house so I can test the apps I make. Of the 10 devices 8 are
android. My app works across the board on all of them flawlessly. So I already
know its not something related to my set up or my code. Out of the *10* devices
one specific feature seems to fail on one specific device (Galaxy Note 3). When
you capture video and try to resolve the URI you will always get error core 5
every single time no matter what changes you make or conditions. Here is the
code.
{code}
navigator.device.capture.captureVideo(function(mediaFiles){
var mediaFilePath = mediaFiles[0].fullPath;
window.resolveLocalFileSystemURL(mediaFilePath, function(){
///never gets this far
}, function(error){
console.log(error.code);
*Always fails with error code 5*
});
}, function(error){
var msg = 'Messages captureVideo():: An error
occurred during video capture: ' + error.code;
console.log(msg, null, 'Uh oh!');
});
{code}
For this device and this specific scenario the path returned by capture is
always something like this:
*file:/storage/extSdCard/DCIM/Camera/20140327_104747.mp4* yes I noticed the
file:/ and have even tried replacing it with file:/// and it still
continues to fail.
btw ...I have a lot of devices I test with with...do you guys have these kind
of facilities. I'm more than happy to help with any testing...I built up a
rigorous excel sheet full of tests among which are all of the media type api's.
I did this because resolveLocalFileSystemURL has become a problem child for me
since 3.4 I have already submitted 3 bugs 1 of which was solved and actually
made it to the 1.0.1 File-System update. The 2nd one is solved now too. I
wouldn't care if the device this was happening to was old and was on an older
firmware like 4.0.3 but this is a popular device especially in our database any
help would be appreciated.
resolveLocalFileSystemURL continues to be inconsistent, now fails
specifically on Galaxy Note 3 when capturing video only
-
Key: CB-6359
URL: https://issues.apache.org/jira/browse/CB-6359
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin File, Plugin Media Capture
Affects Versions: 3.4.0
Environment: On
[jira] [Commented] (CB-6359) resolveLocalFileSystemURL continues to be inconsistent, now fails specifically on Galaxy Note 3 when capturing video only
[
https://issues.apache.org/jira/browse/CB-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13949934#comment-13949934
]
Ralph S Theart commented on CB-6359:
also I am on current version=0.2.8 is this latest?...thanks again for your
help Ian.
resolveLocalFileSystemURL continues to be inconsistent, now fails
specifically on Galaxy Note 3 when capturing video only
-
Key: CB-6359
URL: https://issues.apache.org/jira/browse/CB-6359
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin File, Plugin Media Capture
Affects Versions: 3.4.0
Environment: On Mac
Cordova info
Current Node Version
v0.10.25
Current Cordova CLI Version
3.4.0-0.1.0
Testing with: Samsung Galaxy Note 3 (Android)...the device is NOT rooted.
Reporter: Ralph S Theart
Assignee: Ian Clelland
Labels: android, capture
Ok this is a very strange bug. Some background first though. I have 10 test
devices at my house so I can test the apps I make. Of the 10 devices 8 are
android. My app works across the board on all of them flawlessly. So I
already know its not something related to my set up or my code. Out of the
*10* devices one specific feature seems to fail on one specific device
(Galaxy Note 3). When you capture video and try to resolve the URI you will
always get error core 5 every single time no matter what changes you make or
conditions. Here is the code.
{code}
navigator.device.capture.captureVideo(function(mediaFiles){
var mediaFilePath = mediaFiles[0].fullPath;
window.resolveLocalFileSystemURL(mediaFilePath, function(){
///never gets this far
}, function(error){
console.log(error.code);
*Always fails with error code 5*
});
}, function(error){
var msg = 'Messages captureVideo():: An error
occurred during video capture: ' + error.code;
console.log(msg, null, 'Uh oh!');
});
{code}
For this device and this specific scenario the path returned by capture is
always something like this:
*file:/storage/extSdCard/DCIM/Camera/20140327_104747.mp4* yes I noticed
the file:/ and have even tried replacing it with file:/// and it still
continues to fail.
btw ...I have a lot of devices I test with with...do you guys have these kind
of facilities? I have built up a rigorous excel sheet full of tests among
which are all of the media type api's. I did this because
resolveLocalFileSystemURL has become a problem child for me since 3.4 I have
already submitted 3 bugs 1 of which was solved and actually made it to the
1.0.1 File-System update. The 2nd one is solved now too. I wouldn't care if
the device this was happening to was old and was on an older firmware like
4.0.3 but this is a popular device especially in our database any help would
be appreciated.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Comment Edited] (CB-6249) Camera fails to return an actual FILE_URI it always returns content://
[ https://issues.apache.org/jira/browse/CB-6249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13939523#comment-13939523 ] Ralph S Theart edited comment on CB-6249 at 3/18/14 5:45 PM: - Thanks you for you detailed explanation and I understand. I think for the most part it would return a file:// since it did that consistently with all the 276 unique android devices in our database from 2012 till a week ago since the new phonegap was introduce. The problem is when uploading a file to a backend service what is the back end supposed to do with a file called 4331 or some other obscure naming convention since the content uri's can't be resolved to expose the name of the file. I don't care about it's location since I move the file anyway. Remember this issue only exist with the _returned uri from the file picker of the camera plugin_ all other api like media capture return a file URI. What I love to see added is something that would at least give you the name of the file so when you moved it you could name it that with in the fileEntry.moveTo() method. Using trying to switch case through mime types is more unreliable. I ran a test case in which video/mp4 was actually .3gpp on the Galaxy tab. I would love you see this as part of a files properties; so obviously keep *name* = _content:144_ as it is but maybe have something like *trueName*: _image.png_ does this make sense? This would be helpful since the move is always successful with the content URLs anyway. All I need is the file name..thats it. The work flow I always had and the work flow that would solve this issue would be 1. Pick image or video from file picker of camera api 2. Grab the files name, not the numerical value attached to the content url but it's real file name...image.png or whatever the path of file:/// is irrelevant at this point. 3. Move the file and rename it with the real name you just got 4. Every one is happy including this guy. I don't even know if what I am asking is even possible so I'm not presuming this to be possible but let know your thoughts. For now I have no choice but to muck through the mime type craziness ;}. Thanks Ian again for all of your help...have had a great experience with Phonegap, team, and these threads. was (Author: drumaboy46): Thanks you for you detailed explanation and I understand. I think for the most part it would return a file:// since it did that consistently with all the 276 unique android devices in our database from 2012 till a week ago since the new phonegap was introduce. The problem is when uploading a file to a backend service what is the back end supposed to do with a file called 4331 or some other obscure naming convention since the content uri's can't be resolved to expose the name of the file. I don't care about it's location since I move the file anyway. Remember this issue only exist with the _returned uri from the file picker of the camera plugin_ all other api like media capture return a file URI. What I love to see added is something that would at least give you the name of the file so when you moved it you could name it that with in the fileEntry.moveTo() method. Using trying to switch case through mime types is more unreliable. I ran a test case in which video/mp4 was actually .3gpp on the Galaxy tab. I would love you see this as part of a files properties; so obviously keep *name* = _content:144_ as it is but maybe have something like *trueName*: _image.png_ does this make sense. This would be helpful since the move is always successful with the content URLs The work flow I always had and that would solve this issue would be 1. Pick image or video from file picker of camera api 2. Grab the files name, not the numerical value attached to the content url but it's real file name...image.png or whatever the path of file:/// is irrelevant at this point. 3. Move the file and rename it with the real name you just got 4. Every one is happy including this guy. I don't even know if what I am asking is even possible so I'm not presuming this to be possible but let know your thoughts. For now I have no choice but to muck through the mime type craziness ;}. Thanks Ian again for all of your help...have had a great experience with Phonegap, team, and these threads. Camera fails to return an actual FILE_URI it always returns content:// -- Key: CB-6249 URL: https://issues.apache.org/jira/browse/CB-6249 Project: Apache Cordova Issue Type: Bug Components: Android, Plugin Camera, Plugin File Affects Versions: 3.4.0 Environment: Current Node Version v0.10.25 Current Cordova CLI Version 3.4.0-0.1.0 Android Reporter: Ralph S Theart Labels:
[jira] [Commented] (CB-6249) Camera fails to return an actual FILE_URI it always returns content://
[
https://issues.apache.org/jira/browse/CB-6249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13939523#comment-13939523
]
Ralph S Theart commented on CB-6249:
Thanks you for you detailed explanation and I understand. I think for the most
part it would return a file:// since it did that consistently with all the 276
unique android devices in our database from 2012 till a week ago since the new
phonegap was introduce. The problem is when uploading a file to a backend
service what is the back end supposed to do with a file called 4331 or some
other obscure naming convention since the content uri's can't be resolved to
expose the name of the file. I don't care about it's location since I move the
file anyway. Remember this issue only exist with the _returned uri from the
file picker of the camera plugin_ all other api like media capture return a
file URI. What I love to see added is something that would at least give you
the name of the file so when you moved it you could name it that with in the
fileEntry.moveTo() method. Using trying to switch case through mime types is
more unreliable. I ran a test case in which video/mp4 was actually .3gpp on the
Galaxy tab. I would love you see this as part of a files properties;
so obviously keep *name* = _content:144_ as it is but maybe have something
like *trueName*: _image.png_
does this make sense. This would be helpful since the move is always
successful with the content URLs
The work flow I always had and that would solve this issue would be
1. Pick image or video from file picker of camera api
2. Grab the files name, not the numerical value attached to the content url but
it's real file name...image.png or whatever the path of file:/// is irrelevant
at this point.
3. Move the file and rename it with the real name you just got
4. Every one is happy including this guy.
I don't even know if what I am asking is even possible so I'm not presuming
this to be possible but let know your thoughts. For now I have no choice but to
muck through the mime type craziness ;}.
Thanks Ian again for all of your help...have had a great experience with
Phonegap, team, and these threads.
Camera fails to return an actual FILE_URI it always returns content://
--
Key: CB-6249
URL: https://issues.apache.org/jira/browse/CB-6249
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin Camera, Plugin File
Affects Versions: 3.4.0
Environment: Current Node Version
v0.10.25
Current Cordova CLI Version
3.4.0-0.1.0
Android
Reporter: Ralph S Theart
Labels: camera, file
No matter what I do I can not get a url of file:///... all I get is
{code}
content://media/external/images/media/1357
{code}
Here is my very simple code
{code}
navigator.camera.getPicture(function(imageURI){
console.log('GOT IMAGE: '+imageURI);
window.resolveLocalFileSystemURL(imageURI, function(entry){
console.log(entry.name + +entry.fullPath);
}, function(e){
console.log('Some error occured: '+e.code);
});
}, onPhotoFail, {
destinationType: 1,
sourceType: pictureSource,
mediaType : Camera.MediaType.ALLMEDIA,
encodingType: 0,
allowEdit : false,
correctOrientation:true,
saveToPhotoAlbum: false,
quality: 50
});
{code}
I always get content://... for the returned path from camera and even the
same thing when I resolve the url. Can you confirm this bug?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Comment Edited] (CB-6249) Camera fails to return an actual FILE_URI it always returns content://
[ https://issues.apache.org/jira/browse/CB-6249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13939523#comment-13939523 ] Ralph S Theart edited comment on CB-6249 at 3/18/14 5:49 PM: - Thank you for you detailed explanation and I understand. I think for the most part it would return a file:// since it did that consistently with all the 276 unique android devices in our database from 2012 till a week ago since the new phonegap was introduce. The problem is when uploading a file to a backend service what is the back end supposed to do with a file called 4331 or some other obscure naming convention since the content uri's can't be resolved to expose the name of the file. I don't care about it's location since I move the file anyway. Remember this issue only exist with the _returned uri from the file picker of the camera plugin_ all other api like media capture return a file URI. What I love to see added is something that would at least give you the name of the file so when you moved it you could name it that with in the fileEntry.moveTo() method. Trying to switch case through mime types is more unreliable. I ran a test case in which video/mp4 was actually .3gpp on the Galaxy tab. I would love to see _this_ as part of a files properties: filesName or trueFilesName or something like that. so obviously keep *name* = _content:144_ as it is but maybe have something like *trueName*: _image.png_ does this make sense? This would be helpful since moveTo is always successful with the content URLs anyway. All I need to know is the file name..thats it. The work flow I always had and the work flow that would solve this issue could be: 1. Pick image or video from file picker of camera api 2. Grab the files name, not the numerical value attached to the content url but it's real file name...image.png or whatever the path of file:/// is irrelevant at this point. 3. Move the file and rename it with the real name you just got 4. Every one is happy including this guy. I don't even know if what I am asking is even possible so I'm not presuming this to be possible but let me know your thoughts. For now I have no choice but to muck through the mime type craziness ;}. Thanks Ian again for all of your help...have had a great experience with Phonegap, team, and these threads. was (Author: drumaboy46): Thanks you for you detailed explanation and I understand. I think for the most part it would return a file:// since it did that consistently with all the 276 unique android devices in our database from 2012 till a week ago since the new phonegap was introduce. The problem is when uploading a file to a backend service what is the back end supposed to do with a file called 4331 or some other obscure naming convention since the content uri's can't be resolved to expose the name of the file. I don't care about it's location since I move the file anyway. Remember this issue only exist with the _returned uri from the file picker of the camera plugin_ all other api like media capture return a file URI. What I love to see added is something that would at least give you the name of the file so when you moved it you could name it that with in the fileEntry.moveTo() method. Using trying to switch case through mime types is more unreliable. I ran a test case in which video/mp4 was actually .3gpp on the Galaxy tab. I would love you see this as part of a files properties; so obviously keep *name* = _content:144_ as it is but maybe have something like *trueName*: _image.png_ does this make sense? This would be helpful since the move is always successful with the content URLs anyway. All I need is the file name..thats it. The work flow I always had and the work flow that would solve this issue would be 1. Pick image or video from file picker of camera api 2. Grab the files name, not the numerical value attached to the content url but it's real file name...image.png or whatever the path of file:/// is irrelevant at this point. 3. Move the file and rename it with the real name you just got 4. Every one is happy including this guy. I don't even know if what I am asking is even possible so I'm not presuming this to be possible but let know your thoughts. For now I have no choice but to muck through the mime type craziness ;}. Thanks Ian again for all of your help...have had a great experience with Phonegap, team, and these threads. Camera fails to return an actual FILE_URI it always returns content:// -- Key: CB-6249 URL: https://issues.apache.org/jira/browse/CB-6249 Project: Apache Cordova Issue Type: Bug Components: Android, Plugin Camera, Plugin File Affects Versions: 3.4.0 Environment: Current Node Version
[jira] [Commented] (CB-6249) Camera fails to return an actual FILE_URI it always returns content://
[
https://issues.apache.org/jira/browse/CB-6249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938343#comment-13938343
]
Ralph S Theart commented on CB-6249:
Yes this is what I'm already doing and its not working
{code}
window.requestFileSystem(LocalFileSystem.PERSISTENT, 0,
function(fileSys) {
console.log('window.requestFileSystem...'+uri);
fileSys.root.getDirectory(messages, {create: true,
exclusive: false}, function(dir) {
fileEntry.moveTo(dir, null,
Messaging.listFilesInMessagesDirectory, Messaging.fail);
}, function(error){
console.log('Messages moveFile()
fileSys.root.getDirectory():: Could not get directory');
});
}, function(error){
console.log('Messages moveFile()
window.requestFileSystem():: Could not get file system.');
});
{code}
In the above example the uri was content://media/external/images/media/1435
when I move it and use null in fileEntry.moveTo() like in your example for the
name...it just uses saves the file as 1435 which to me doesn't make any sense.
It just save the file as the number at the end of the content uri...super
annoying because if I upload it I have no idea what type of media it is. On iOS
the file name including the extension is returned. I think I may be doing
something wrong since I seem to be the only one with this issue :}
I've used every method available to try to get a file URI like I use to get
with previous versions of phonegap
{code}
I/Web Console( 7758): Messages moveFile(fullPath):: About to move file:
/media/external/images/media/1435:140
I/Web Console( 7758): Messages moveFile(toURL):: About to move file:
content://media/external/images/media/1435:141
I/Web Console( 7758): Messages moveFile(toNativeURL):: About to move file:
content://media/external/images/media/1435:142
its the same uri each time...which again makes no sense...to me anyway..I could
be wrong...and I'm ok with that..just trying to find a solution.
{code}
Yes I need to know...when choosing content from the lib it doesn't limit you to
images but videos as well. As you know playing video locally on android is
troublesome so I need to now when I have a video v.s. an image so I can preview
it to the user with the right code and for other reason as well.
Also your code dind't seem to work I keep getting this error ...don't you have
to pass the directory as an object?
{code}
I/Web Console( 5181): URI:
content://com.sec.android.gallery3d.provider/picasa/item/5624002846809387650:134
E/Web Console( 5181): Wrong type for parameter parent of Entry.moveTo:
Expected Object, but got Function.:413
I/Web Console( 5181): processMessage failed: Message: S01 File1894715692
{fullPath:\/com.sec.android.gallery3d.provider\/picasa\/item\/5624002846809387650,filesystemName:content,isDirectory:false,nativeURL:content:\/\/com.sec.android.gallery3d.provider\/picasa\/item\/5624002846809387650,filesystem:1,isFile:true,name:5624002846809387650}:1034
I/Web Console( 5181): processMessage failed: Error: TypeError: Wrong type for
parameter parent of Entry.moveTo: Expected Object, but got Function.:1035
I/Web Console( 5181): processMessage failed: Stack: TypeError: Wrong type for
parameter parent of Entry.moveTo: Expected Object, but got Function.
I/Web Console( 5181): at TypeError (anonymous)
I/Web Console( 5181): at Object.checkArgs
(file:///android_asset/www/cordova.js:415:15)
I/Web Console( 5181): at Entry.moveTo
(file:///android_asset/www/plugins/org.apache.cordova.file/www/Entry.js:105:15)
I/Web Console( 5181): at
file:///android_asset/www/js/api/messaging.js:121:13
I/Web Console( 5181): at success
(file:///android_asset/www/plugins/org.apache.cordova.file/www/resolveLocalFileSystemURI.js:55:17)
I/Web Console( 5181): at Object.cordova.callbackFromNative
(file:///android_asset/www/cordova.js:292:54)
I/Web Console( 5181): at processMessage
(file:///android_asset/www/cordova.js:1029:21)
I/Web Console( 5181): at Function.androidExec.processMessages
(file:///android_asset/www/cordova.js:1063:13)
I/Web Console( 5181): at pollOnce
(file:///android_asset/www/cordova.js:933:17)
I/Web Console( 5181): at pollOnceFromOnlineEvent
(file:///android_asset/www/cordova.js:928:5):1036
{code}
Camera fails to return an actual FILE_URI it always returns content://
--
Key: CB-6249
URL: https://issues.apache.org/jira/browse/CB-6249
Project: Apache
[jira] [Commented] (CB-6249) Camera fails to return an actual FILE_URI it always returns content://
[
https://issues.apache.org/jira/browse/CB-6249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938383#comment-13938383
]
Ralph S Theart commented on CB-6249:
Yes I thought of using getMetadata...but there doesn't seem to be a properties
list of that method in the phonegap documentation is it something like this
fileEntry.getMetadata(function(data){
console.log(data.mimetype);
},function(e){
//some error
});
I think this would solve my problem.
Also sounds like from your explanations not being able to retrieve a relevant
uir like file:///emulated/0/SomeFolder/pic1.png is the intended behaviour for
phonegap 3.4 on Androids...if so I'd like to change the status of this issue
from bug to trivial...do you agree?
Camera fails to return an actual FILE_URI it always returns content://
--
Key: CB-6249
URL: https://issues.apache.org/jira/browse/CB-6249
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin Camera, Plugin File
Affects Versions: 3.4.0
Environment: Current Node Version
v0.10.25
Current Cordova CLI Version
3.4.0-0.1.0
Android
Reporter: Ralph S Theart
Labels: camera, file
No matter what I do I can not get a url of file:///... all I get is
{code}
content://media/external/images/media/1357
{code}
Here is my very simple code
{code}
navigator.camera.getPicture(function(imageURI){
console.log('GOT IMAGE: '+imageURI);
window.resolveLocalFileSystemURL(imageURI, function(entry){
console.log(entry.name + +entry.fullPath);
}, function(e){
console.log('Some error occured: '+e.code);
});
}, onPhotoFail, {
destinationType: 1,
sourceType: pictureSource,
mediaType : Camera.MediaType.ALLMEDIA,
encodingType: 0,
allowEdit : false,
correctOrientation:true,
saveToPhotoAlbum: false,
quality: 50
});
{code}
I always get content://... for the returned path from camera and even the
same thing when I resolve the url. Can you confirm this bug?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6249) Camera fails to return an actual FILE_URI it always returns content://
[
https://issues.apache.org/jira/browse/CB-6249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938529#comment-13938529
]
Ralph S Theart commented on CB-6249:
As I surmised getMetadata on contains _modificationTime_ and _size_ as its
properties...so this method is useless for me.
Is it even possible to get the FILE_URL back like I was able to do before I
updated to phonegap 3.0.0+ when I was on 2.8 it returned the file name +
extension on android devices...why the change?? Definitely need a work around
Camera fails to return an actual FILE_URI it always returns content://
--
Key: CB-6249
URL: https://issues.apache.org/jira/browse/CB-6249
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin Camera, Plugin File
Affects Versions: 3.4.0
Environment: Current Node Version
v0.10.25
Current Cordova CLI Version
3.4.0-0.1.0
Android
Reporter: Ralph S Theart
Labels: camera, file
No matter what I do I can not get a url of file:///... all I get is
{code}
content://media/external/images/media/1357
{code}
Here is my very simple code
{code}
navigator.camera.getPicture(function(imageURI){
console.log('GOT IMAGE: '+imageURI);
window.resolveLocalFileSystemURL(imageURI, function(entry){
console.log(entry.name + +entry.fullPath);
}, function(e){
console.log('Some error occured: '+e.code);
});
}, onPhotoFail, {
destinationType: 1,
sourceType: pictureSource,
mediaType : Camera.MediaType.ALLMEDIA,
encodingType: 0,
allowEdit : false,
correctOrientation:true,
saveToPhotoAlbum: false,
quality: 50
});
{code}
I always get content://... for the returned path from camera and even the
same thing when I resolve the url. Can you confirm this bug?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Comment Edited] (CB-6249) Camera fails to return an actual FILE_URI it always returns content://
[
https://issues.apache.org/jira/browse/CB-6249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938529#comment-13938529
]
Ralph S Theart edited comment on CB-6249 at 3/17/14 11:05 PM:
--
As I surmised getMetadata **only** contains _modificationTime_ and _size_ as
its properties...so this method is useless for me.
Is it even possible to get the FILE_URL back like I was able to do before I
updated to phonegap 3.0.0+ when I was on 2.8 it returned the file name +
extension on android devices...why the change?? Definitely need a work around
was (Author: drumaboy46):
As I surmised getMetadata on contains _modificationTime_ and _size_ as its
properties...so this method is useless for me.
Is it even possible to get the FILE_URL back like I was able to do before I
updated to phonegap 3.0.0+ when I was on 2.8 it returned the file name +
extension on android devices...why the change?? Definitely need a work around
Camera fails to return an actual FILE_URI it always returns content://
--
Key: CB-6249
URL: https://issues.apache.org/jira/browse/CB-6249
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin Camera, Plugin File
Affects Versions: 3.4.0
Environment: Current Node Version
v0.10.25
Current Cordova CLI Version
3.4.0-0.1.0
Android
Reporter: Ralph S Theart
Labels: camera, file
No matter what I do I can not get a url of file:///... all I get is
{code}
content://media/external/images/media/1357
{code}
Here is my very simple code
{code}
navigator.camera.getPicture(function(imageURI){
console.log('GOT IMAGE: '+imageURI);
window.resolveLocalFileSystemURL(imageURI, function(entry){
console.log(entry.name + +entry.fullPath);
}, function(e){
console.log('Some error occured: '+e.code);
});
}, onPhotoFail, {
destinationType: 1,
sourceType: pictureSource,
mediaType : Camera.MediaType.ALLMEDIA,
encodingType: 0,
allowEdit : false,
correctOrientation:true,
saveToPhotoAlbum: false,
quality: 50
});
{code}
I always get content://... for the returned path from camera and even the
same thing when I resolve the url. Can you confirm this bug?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6249) Camera fails to return an actual FILE_URI it always returns content://
[
https://issues.apache.org/jira/browse/CB-6249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938844#comment-13938844
]
Ralph S Theart commented on CB-6249:
Yes if you can look more into it that would be great. using file
FileEntry.file() is a bit of a drag but it does return the mime type will test
other phone since in the Android world with devices anyway there is no real
standard it seems ...ive seen 3ggp, 3gp, ogg, avi etc...hopefully the mime-type
returned will be what the file is.
Camera fails to return an actual FILE_URI it always returns content://
--
Key: CB-6249
URL: https://issues.apache.org/jira/browse/CB-6249
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin Camera, Plugin File
Affects Versions: 3.4.0
Environment: Current Node Version
v0.10.25
Current Cordova CLI Version
3.4.0-0.1.0
Android
Reporter: Ralph S Theart
Labels: camera, file
No matter what I do I can not get a url of file:///... all I get is
{code}
content://media/external/images/media/1357
{code}
Here is my very simple code
{code}
navigator.camera.getPicture(function(imageURI){
console.log('GOT IMAGE: '+imageURI);
window.resolveLocalFileSystemURL(imageURI, function(entry){
console.log(entry.name + +entry.fullPath);
}, function(e){
console.log('Some error occured: '+e.code);
});
}, onPhotoFail, {
destinationType: 1,
sourceType: pictureSource,
mediaType : Camera.MediaType.ALLMEDIA,
encodingType: 0,
allowEdit : false,
correctOrientation:true,
saveToPhotoAlbum: false,
quality: 50
});
{code}
I always get content://... for the returned path from camera and even the
same thing when I resolve the url. Can you confirm this bug?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6249) Camera fails to return an actual FILE_URI it always returns content://
[
https://issues.apache.org/jira/browse/CB-6249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13935670#comment-13935670
]
Ralph S Theart commented on CB-6249:
sorry dev'ing on mac. I have xcode and eclishped installed since I dev for
these two device types exclusively. I experience the same issue on all android
platforms no matter the version.
Camera fails to return an actual FILE_URI it always returns content://
--
Key: CB-6249
URL: https://issues.apache.org/jira/browse/CB-6249
Project: Apache Cordova
Issue Type: Bug
Components: Plugin Camera, Plugin File
Affects Versions: 3.4.0
Environment: Current Node Version
v0.10.25
Current Cordova CLI Version
3.4.0-0.1.0
Reporter: Ralph S Theart
Labels: camera, file
No matter what I do I can not get a url of file:///... all I get is
{code}
content://media/external/images/media/1357
{code}
Here is my very simple code
{code}
navigator.camera.getPicture(function(imageURI){
console.log('GOT IMAGE: '+imageURI);
window.resolveLocalFileSystemURL(imageURI, function(entry){
console.log(entry.name + +entry.fullPath);
}, function(e){
console.log('Some error occured: '+e.code);
});
}, onPhotoFail, {
destinationType: 1,
sourceType: pictureSource,
mediaType : Camera.MediaType.ALLMEDIA,
encodingType: 0,
allowEdit : false,
correctOrientation:true,
saveToPhotoAlbum: false,
quality: 50
});
{code}
I always get content://... for the returned path from camera and even the
same thing when I resolve the url. Can you confirm this bug?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-5838) Android 4.4 - Path returned from Camera plugin FILE_URI is not readable
[
https://issues.apache.org/jira/browse/CB-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13934009#comment-13934009
]
Ralph S Theart commented on CB-5838:
this absolutely does not work...need the file
`content://media/external/images/media/`
Android 4.4 - Path returned from Camera plugin FILE_URI is not readable
---
Key: CB-5838
URL: https://issues.apache.org/jira/browse/CB-5838
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin Camera
Affects Versions: 3.3.0
Reporter: Lindsey Simon
Assignee: Andrew Grieve
I'm calling the plugin like so (pasted below). When I take the file uri and
try to load it into another interface, like the ExifInterface I get the
following error:
E/JHEAD ( 6734): can't open
'file:///storage/emulated/0/DCIM/Camera/1390266145786.jpg'
---
var cameraOptions = {
quality: 100,
destinationType: Camera.DestinationType.FILE_URI,
sourceType: Camera.PictureSourceType.CAMERA,
allowEdit: true,
encodingType: Camera.EncodingType.JPEG,
targetWidth: 800,
saveToPhotoAlbum: true
};
navigator.camera.getPicture(
_.bind(this.onPhotoSuccess_, this),
_.bind(this.onPhotoError_, this),
cameraOptions);
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-5838) Android 4.4 - Path returned from Camera plugin FILE_URI is not readable
[
https://issues.apache.org/jira/browse/CB-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13934011#comment-13934011
]
Ralph S Theart commented on CB-5838:
btw when you take a picture a file:/// path is returned when using FILE_URI but
when choose anything from the gallery it gives back uri but not one you can use
normally in a case where you would want to use the extension.
Android 4.4 - Path returned from Camera plugin FILE_URI is not readable
---
Key: CB-5838
URL: https://issues.apache.org/jira/browse/CB-5838
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin Camera
Affects Versions: 3.3.0
Reporter: Lindsey Simon
Assignee: Andrew Grieve
I'm calling the plugin like so (pasted below). When I take the file uri and
try to load it into another interface, like the ExifInterface I get the
following error:
E/JHEAD ( 6734): can't open
'file:///storage/emulated/0/DCIM/Camera/1390266145786.jpg'
---
var cameraOptions = {
quality: 100,
destinationType: Camera.DestinationType.FILE_URI,
sourceType: Camera.PictureSourceType.CAMERA,
allowEdit: true,
encodingType: Camera.EncodingType.JPEG,
targetWidth: 800,
saveToPhotoAlbum: true
};
navigator.camera.getPicture(
_.bind(this.onPhotoSuccess_, this),
_.bind(this.onPhotoError_, this),
cameraOptions);
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (CB-6249) Camera fails to return an actual FILE_URI it always returns content://
Ralph S Theart created CB-6249:
--
Summary: Camera fails to return an actual FILE_URI it always
returns content://
Key: CB-6249
URL: https://issues.apache.org/jira/browse/CB-6249
Project: Apache Cordova
Issue Type: Bug
Components: Plugin Camera, Plugin File
Affects Versions: 3.4.0
Environment: Current Node Version
v0.10.25
Current Cordova CLI Version
3.4.0-0.1.0
Reporter: Ralph S Theart
No matter what I do I can not get a url of file:///... all I get is
{code}
content://media/external/images/media/1357
{code}
Here is my very simple code
{code}
navigator.camera.getPicture(function(imageURI){
console.log('GOT IMAGE: '+imageURI);
window.resolveLocalFileSystemURL(imageURI, function(entry){
console.log(entry.name + +entry.fullPath);
}, function(e){
console.log('Some error occured: '+e.code);
});
}, onPhotoFail, {
destinationType: 1,
sourceType: pictureSource,
mediaType : Camera.MediaType.ALLMEDIA,
encodingType: 0,
allowEdit : false,
correctOrientation:true,
saveToPhotoAlbum: false,
quality: 50
});
{code}
I always get content://... for the returned path from camera and even the same
thing when I resolve the url. Can you confirm this bug?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6135) Camera api takes long time to return uri when using Camera.DestinationType.FILE_URI
[
https://issues.apache.org/jira/browse/CB-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13922099#comment-13922099
]
Ralph S Theart commented on CB-6135:
since update to 3.4 everything the load time is normal.
Camera api takes long time to return uri when using
Camera.DestinationType.FILE_URI
---
Key: CB-6135
URL: https://issues.apache.org/jira/browse/CB-6135
Project: Apache Cordova
Issue Type: Bug
Components: Plugin Camera
Affects Versions: 3.3.0
Reporter: Ralph S Theart
Labels: camera, ios
Fix For: 3.4.0
For some reason there is a slight pause(it's very noticeable, almost seems
like app is about to crash) when choosing an image from the photo library
when use FILE_URI...if I use NATIVE_URL when I choose a picture there is no
such pause.
Here is some code:
captureImage: function(){
var onPhotoFail = function(message){
//console.log(message);
}
var pictureSource; // picture source
var destinationType; // sets the format of returned value
var onPhotoConfirm = function(buttonIndex){
destinationType = Camera.DestinationType.NATIVE_URI;
switch(buttonIndex)
{
case 1:
pictureSource=
Camera.PictureSourceType.CAMERA;
break;
case 2:
pictureSource=
Camera.PictureSourceType.PHOTOLIBRARY;
break;
}
if(buttonIndex == 1 || buttonIndex == 2){
navigator.camera.getPicture(Messaging.createFileEntry, onPhotoFail, {
destinationType: 1,
sourceType: pictureSource,
mediaType : Camera.MediaType.ALLMEDIA,
/*encodingType: Camera.EncodingType.JPEG,
*/
allowEdit : false,
saveToPhotoAlbum: false,
quality: 50
});
}
}
urapp.notify.confirm('Image Capture','What would you like to
do?',[Take Photo,Choose Existing, 'Cancel'],onPhotoConfirm);
},
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Closed] (CB-6135) Camera api takes long time to return uri when using Camera.DestinationType.FILE_URI
[
https://issues.apache.org/jira/browse/CB-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph S Theart closed CB-6135.
--
Resolution: Fixed
Fix Version/s: 3.4.0
Camera api takes long time to return uri when using
Camera.DestinationType.FILE_URI
---
Key: CB-6135
URL: https://issues.apache.org/jira/browse/CB-6135
Project: Apache Cordova
Issue Type: Bug
Components: Plugin Camera
Affects Versions: 3.3.0
Reporter: Ralph S Theart
Labels: camera, ios
Fix For: 3.4.0
For some reason there is a slight pause(it's very noticeable, almost seems
like app is about to crash) when choosing an image from the photo library
when use FILE_URI...if I use NATIVE_URL when I choose a picture there is no
such pause.
Here is some code:
captureImage: function(){
var onPhotoFail = function(message){
//console.log(message);
}
var pictureSource; // picture source
var destinationType; // sets the format of returned value
var onPhotoConfirm = function(buttonIndex){
destinationType = Camera.DestinationType.NATIVE_URI;
switch(buttonIndex)
{
case 1:
pictureSource=
Camera.PictureSourceType.CAMERA;
break;
case 2:
pictureSource=
Camera.PictureSourceType.PHOTOLIBRARY;
break;
}
if(buttonIndex == 1 || buttonIndex == 2){
navigator.camera.getPicture(Messaging.createFileEntry, onPhotoFail, {
destinationType: 1,
sourceType: pictureSource,
mediaType : Camera.MediaType.ALLMEDIA,
/*encodingType: Camera.EncodingType.JPEG,
*/
allowEdit : false,
saveToPhotoAlbum: false,
quality: 50
});
}
}
urapp.notify.confirm('Image Capture','What would you like to
do?',[Take Photo,Choose Existing, 'Cancel'],onPhotoConfirm);
},
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6148) wrong filesystem properties in entry after moveTo()
[
https://issues.apache.org/jira/browse/CB-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13919211#comment-13919211
]
Ralph S Theart commented on CB-6148:
I'm sorry this might be a dumb question but how do you update the plugin so
that I can test the changes in the dev branch I tried:
cordova plugin add org.apache.cordova.file#dev
but it say it's already installed. I'm having the same issue as this user...and
have wasted a lot of time thinking it was an issue with my code. The docs are
unclear how one should update a plugin via CLI. I was able to successfully
update from 3.3.1 to 3.4.0 today but trying to figure out how to update the
file api since it continually fails. Hasn't worked since I went 3.0can not
move a file for the life of me.
wrong filesystem properties in entry after moveTo()
---
Key: CB-6148
URL: https://issues.apache.org/jira/browse/CB-6148
Project: Apache Cordova
Issue Type: Bug
Components: Plugin File
Affects Versions: 3.4.0
Environment: iOS6
iOS7
Reporter: Dominik Pesch
Assignee: Ian Clelland
To store pictures persistent in our app, we move the image files from the
temporary folder to the persistent folder. The code breaks after upgrading to
Cordova 3.4.0 and file plugin 1.0.0 (and 1.0.1).
We've found that the filesystem object in the moveTo success callback entry
parameter has got wrong value (please notice pseudo code below).
Below you'll see the Xcode log output:
{noformat}
2014-03-02 21:31:43.672 Finanzchecker[509:907] fileSys.name: persistent
2014-03-02 21:31:43.682 Finanzchecker[509:907] fileSys.root.name: /
2014-03-02 21:31:43.687 Finanzchecker[509:907] fileSys.root.fullPath: /
2014-03-02 21:31:43.717 Finanzchecker[509:907] dir.name: pics
2014-03-02 21:31:43.726 Finanzchecker[509:907] dir.fullPath: /pics/
2014-03-02 21:31:43.778 Finanzchecker[509:907] newFileEntry.name:
pic1393792303602.jpg
2014-03-02 21:31:43.784 Finanzchecker[509:907] newFileEntry.fullPath:
/pics/pic1393792303602.jpg
2014-03-02 21:31:43.796 Finanzchecker[509:907] newFileEntry.nativeURL:
file:///var/mobile/Applications/82A8A0EF-8012-4D7E-B78D-EA3A4C2B7CBF/Documents/pics/pic1393792303602.jpg
2014-03-02 21:31:43.802 Finanzchecker[509:907] newFileEntry.toURL():
cdvfile://localhost/temporary/pics/pic1393792303602.jpg
2014-03-02 21:31:43.815 Finanzchecker[509:907] newFileEntry.filesystem.name:
temporary
2014-03-02 21:31:43.820 Finanzchecker[509:907]
newFileEntry.filesystem.root.name: '/'
2014-03-02 21:31:43.820 Finanzchecker[509:907]
newFileEntry.filesystem.root.fullPath: '/'
{noformat}
*Our problem:*
We had expected that newFileEntry.filesystem.name has to be 'persistent'
(instead it is 'temporary') . newFileEntry.toURL returns the wrong cdvfile
URL (please see Xcode output above).
{code:JavaScript|title=Shortened pseudo code:|borderStyle=solid}
// ... will be called from navigator.camera.getPicture(...)
function picSuccess(imageUrl)
{
window.resolveLocalFileSystemURL(imageUrl, _fileEntrySuccess,
_handleFileError);
function _fileEntrySuccess(tmpFileEntry)
{
var newFileName = pic + new Date().getTime() + '.jpg';
window.requestFileSystem(LocalFileSystem.PERSISTENT, 0, function(fileSys)
{
console.log(fileSys.name: + fileSys.name);
console.log(fileSys.root.name: + fileSys.root.name);
console.log(fileSys.root.fullPath: + fileSys.root.fullPath);
fileSys.root.getDirectory(pics, { create: true, exclusive: false },
function(dir)
{
console.log(dir.name: + dir.name);
console.log(dir.fullPath: + dir.fullPath);
tmpFileEntry.moveTo(dir, newFileName, function(newFileEntry)
{
console.log(newFileEntry.name: + newFileEntry.name);
console.log(newFileEntry.fullPath: + newFileEntry.fullPath);
console.log(newFileEntry.nativeURL: + newFileEntry.nativeURL);
console.log(newFileEntry.toURL(): + newFileEntry.toURL());
console.log(newFileEntry.filesystem.name: +
newFileEntry.filesystem.name);
console.log(newFileEntry.filesystem.fullPath: +
newFileEntry.filesystem.fullPath);
_fileMovedSuccess(newFileEntry);
}, _handleFileError)
})
},
_handleFileError);
}
function _fileMovedSuccess(entry)
{
// ...
}
}
{code}
We've tested this with Cordova 3.4.0 and cordova file plugin 1.0.0 and 1.0.1
(https://github.com/apache/cordova-plugin-file.git
21e119692ab9c9fb2912dc69e2c6d4b05307e3e2).
// corrected the example (some typos)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Comment Edited] (CB-6148) wrong filesystem properties in entry after moveTo()
[
https://issues.apache.org/jira/browse/CB-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13919211#comment-13919211
]
Ralph S Theart edited comment on CB-6148 at 3/4/14 10:28 AM:
-
I'm sorry this might be a dumb question but how do you update the plugin so
that I can test the changes in the dev branch I tried:
cordova plugin add org.apache.cordova.file#dev
but it say it's already installed. I'm having the same issue as this user...and
have wasted a lot of time thinking it was an issue with my code. The docs are
unclear how one should update a plugin via CLI. I was able to successfully
update from 3.3.1 to 3.4.0 today but trying to figure out how to update the
file api since it continually fails. Hasn't worked since I went 3.0can not
move a file for the life of me.
*EDIT*
sorry for the silly question found https://cordova.apache.org/ ...wish there
was an update command for the plugins as some of the plugins are dependent on
others.
was (Author: drumaboy46):
I'm sorry this might be a dumb question but how do you update the plugin so
that I can test the changes in the dev branch I tried:
cordova plugin add org.apache.cordova.file#dev
but it say it's already installed. I'm having the same issue as this user...and
have wasted a lot of time thinking it was an issue with my code. The docs are
unclear how one should update a plugin via CLI. I was able to successfully
update from 3.3.1 to 3.4.0 today but trying to figure out how to update the
file api since it continually fails. Hasn't worked since I went 3.0can not
move a file for the life of me.
sorry for the silly question found https://cordova.apache.org/ ...wish there
was an update command for the plugins as some of the plugins are dependent on
others.
wrong filesystem properties in entry after moveTo()
---
Key: CB-6148
URL: https://issues.apache.org/jira/browse/CB-6148
Project: Apache Cordova
Issue Type: Bug
Components: Plugin File
Affects Versions: 3.4.0
Environment: iOS6
iOS7
Reporter: Dominik Pesch
Assignee: Ian Clelland
To store pictures persistent in our app, we move the image files from the
temporary folder to the persistent folder. The code breaks after upgrading to
Cordova 3.4.0 and file plugin 1.0.0 (and 1.0.1).
We've found that the filesystem object in the moveTo success callback entry
parameter has got wrong value (please notice pseudo code below).
Below you'll see the Xcode log output:
{noformat}
2014-03-02 21:31:43.672 Finanzchecker[509:907] fileSys.name: persistent
2014-03-02 21:31:43.682 Finanzchecker[509:907] fileSys.root.name: /
2014-03-02 21:31:43.687 Finanzchecker[509:907] fileSys.root.fullPath: /
2014-03-02 21:31:43.717 Finanzchecker[509:907] dir.name: pics
2014-03-02 21:31:43.726 Finanzchecker[509:907] dir.fullPath: /pics/
2014-03-02 21:31:43.778 Finanzchecker[509:907] newFileEntry.name:
pic1393792303602.jpg
2014-03-02 21:31:43.784 Finanzchecker[509:907] newFileEntry.fullPath:
/pics/pic1393792303602.jpg
2014-03-02 21:31:43.796 Finanzchecker[509:907] newFileEntry.nativeURL:
file:///var/mobile/Applications/82A8A0EF-8012-4D7E-B78D-EA3A4C2B7CBF/Documents/pics/pic1393792303602.jpg
2014-03-02 21:31:43.802 Finanzchecker[509:907] newFileEntry.toURL():
cdvfile://localhost/temporary/pics/pic1393792303602.jpg
2014-03-02 21:31:43.815 Finanzchecker[509:907] newFileEntry.filesystem.name:
temporary
2014-03-02 21:31:43.820 Finanzchecker[509:907]
newFileEntry.filesystem.root.name: '/'
2014-03-02 21:31:43.820 Finanzchecker[509:907]
newFileEntry.filesystem.root.fullPath: '/'
{noformat}
*Our problem:*
We had expected that newFileEntry.filesystem.name has to be 'persistent'
(instead it is 'temporary') . newFileEntry.toURL returns the wrong cdvfile
URL (please see Xcode output above).
{code:JavaScript|title=Shortened pseudo code:|borderStyle=solid}
// ... will be called from navigator.camera.getPicture(...)
function picSuccess(imageUrl)
{
window.resolveLocalFileSystemURL(imageUrl, _fileEntrySuccess,
_handleFileError);
function _fileEntrySuccess(tmpFileEntry)
{
var newFileName = pic + new Date().getTime() + '.jpg';
window.requestFileSystem(LocalFileSystem.PERSISTENT, 0, function(fileSys)
{
console.log(fileSys.name: + fileSys.name);
console.log(fileSys.root.name: + fileSys.root.name);
console.log(fileSys.root.fullPath: + fileSys.root.fullPath);
fileSys.root.getDirectory(pics, { create: true, exclusive: false },
function(dir)
{
console.log(dir.name: + dir.name);
console.log(dir.fullPath: + dir.fullPath);
tmpFileEntry.moveTo(dir, newFileName, function(newFileEntry)
{
console.log(newFileEntry.name: +
[jira] [Comment Edited] (CB-6148) wrong filesystem properties in entry after moveTo()
[
https://issues.apache.org/jira/browse/CB-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13919211#comment-13919211
]
Ralph S Theart edited comment on CB-6148 at 3/4/14 10:28 AM:
-
I'm sorry this might be a dumb question but how do you update the plugin so
that I can test the changes in the dev branch I tried:
cordova plugin add org.apache.cordova.file#dev
but it say it's already installed. I'm having the same issue as this user...and
have wasted a lot of time thinking it was an issue with my code. The docs are
unclear how one should update a plugin via CLI. I was able to successfully
update from 3.3.1 to 3.4.0 today but trying to figure out how to update the
file api since it continually fails. Hasn't worked since I went 3.0can not
move a file for the life of me.
sorry for the silly question found (https://cordova.apache.org/)...wish there
was an update command for the plugins as some of the plugins are dependent on
others.
was (Author: drumaboy46):
I'm sorry this might be a dumb question but how do you update the plugin so
that I can test the changes in the dev branch I tried:
cordova plugin add org.apache.cordova.file#dev
but it say it's already installed. I'm having the same issue as this user...and
have wasted a lot of time thinking it was an issue with my code. The docs are
unclear how one should update a plugin via CLI. I was able to successfully
update from 3.3.1 to 3.4.0 today but trying to figure out how to update the
file api since it continually fails. Hasn't worked since I went 3.0can not
move a file for the life of me.
wrong filesystem properties in entry after moveTo()
---
Key: CB-6148
URL: https://issues.apache.org/jira/browse/CB-6148
Project: Apache Cordova
Issue Type: Bug
Components: Plugin File
Affects Versions: 3.4.0
Environment: iOS6
iOS7
Reporter: Dominik Pesch
Assignee: Ian Clelland
To store pictures persistent in our app, we move the image files from the
temporary folder to the persistent folder. The code breaks after upgrading to
Cordova 3.4.0 and file plugin 1.0.0 (and 1.0.1).
We've found that the filesystem object in the moveTo success callback entry
parameter has got wrong value (please notice pseudo code below).
Below you'll see the Xcode log output:
{noformat}
2014-03-02 21:31:43.672 Finanzchecker[509:907] fileSys.name: persistent
2014-03-02 21:31:43.682 Finanzchecker[509:907] fileSys.root.name: /
2014-03-02 21:31:43.687 Finanzchecker[509:907] fileSys.root.fullPath: /
2014-03-02 21:31:43.717 Finanzchecker[509:907] dir.name: pics
2014-03-02 21:31:43.726 Finanzchecker[509:907] dir.fullPath: /pics/
2014-03-02 21:31:43.778 Finanzchecker[509:907] newFileEntry.name:
pic1393792303602.jpg
2014-03-02 21:31:43.784 Finanzchecker[509:907] newFileEntry.fullPath:
/pics/pic1393792303602.jpg
2014-03-02 21:31:43.796 Finanzchecker[509:907] newFileEntry.nativeURL:
file:///var/mobile/Applications/82A8A0EF-8012-4D7E-B78D-EA3A4C2B7CBF/Documents/pics/pic1393792303602.jpg
2014-03-02 21:31:43.802 Finanzchecker[509:907] newFileEntry.toURL():
cdvfile://localhost/temporary/pics/pic1393792303602.jpg
2014-03-02 21:31:43.815 Finanzchecker[509:907] newFileEntry.filesystem.name:
temporary
2014-03-02 21:31:43.820 Finanzchecker[509:907]
newFileEntry.filesystem.root.name: '/'
2014-03-02 21:31:43.820 Finanzchecker[509:907]
newFileEntry.filesystem.root.fullPath: '/'
{noformat}
*Our problem:*
We had expected that newFileEntry.filesystem.name has to be 'persistent'
(instead it is 'temporary') . newFileEntry.toURL returns the wrong cdvfile
URL (please see Xcode output above).
{code:JavaScript|title=Shortened pseudo code:|borderStyle=solid}
// ... will be called from navigator.camera.getPicture(...)
function picSuccess(imageUrl)
{
window.resolveLocalFileSystemURL(imageUrl, _fileEntrySuccess,
_handleFileError);
function _fileEntrySuccess(tmpFileEntry)
{
var newFileName = pic + new Date().getTime() + '.jpg';
window.requestFileSystem(LocalFileSystem.PERSISTENT, 0, function(fileSys)
{
console.log(fileSys.name: + fileSys.name);
console.log(fileSys.root.name: + fileSys.root.name);
console.log(fileSys.root.fullPath: + fileSys.root.fullPath);
fileSys.root.getDirectory(pics, { create: true, exclusive: false },
function(dir)
{
console.log(dir.name: + dir.name);
console.log(dir.fullPath: + dir.fullPath);
tmpFileEntry.moveTo(dir, newFileName, function(newFileEntry)
{
console.log(newFileEntry.name: + newFileEntry.name);
console.log(newFileEntry.fullPath: + newFileEntry.fullPath);
console.log(newFileEntry.nativeURL: + newFileEntry.nativeURL);
[jira] [Comment Edited] (CB-6148) wrong filesystem properties in entry after moveTo()
[
https://issues.apache.org/jira/browse/CB-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13919211#comment-13919211
]
Ralph S Theart edited comment on CB-6148 at 3/4/14 10:28 AM:
-
I'm sorry this might be a dumb question but how do you update the plugin so
that I can test the changes in the dev branch I tried:
cordova plugin add org.apache.cordova.file#dev
but it say it's already installed. I'm having the same issue as this user...and
have wasted a lot of time thinking it was an issue with my code. The docs are
unclear how one should update a plugin via CLI. I was able to successfully
update from 3.3.1 to 3.4.0 today but trying to figure out how to update the
file api since it continually fails. Hasn't worked since I went 3.0can not
move a file for the life of me.
sorry for the silly question found https://cordova.apache.org/...wish there was
an update command for the plugins as some of the plugins are dependent on
others.
was (Author: drumaboy46):
I'm sorry this might be a dumb question but how do you update the plugin so
that I can test the changes in the dev branch I tried:
cordova plugin add org.apache.cordova.file#dev
but it say it's already installed. I'm having the same issue as this user...and
have wasted a lot of time thinking it was an issue with my code. The docs are
unclear how one should update a plugin via CLI. I was able to successfully
update from 3.3.1 to 3.4.0 today but trying to figure out how to update the
file api since it continually fails. Hasn't worked since I went 3.0can not
move a file for the life of me.
sorry for the silly question found (https://cordova.apache.org/)...wish there
was an update command for the plugins as some of the plugins are dependent on
others.
wrong filesystem properties in entry after moveTo()
---
Key: CB-6148
URL: https://issues.apache.org/jira/browse/CB-6148
Project: Apache Cordova
Issue Type: Bug
Components: Plugin File
Affects Versions: 3.4.0
Environment: iOS6
iOS7
Reporter: Dominik Pesch
Assignee: Ian Clelland
To store pictures persistent in our app, we move the image files from the
temporary folder to the persistent folder. The code breaks after upgrading to
Cordova 3.4.0 and file plugin 1.0.0 (and 1.0.1).
We've found that the filesystem object in the moveTo success callback entry
parameter has got wrong value (please notice pseudo code below).
Below you'll see the Xcode log output:
{noformat}
2014-03-02 21:31:43.672 Finanzchecker[509:907] fileSys.name: persistent
2014-03-02 21:31:43.682 Finanzchecker[509:907] fileSys.root.name: /
2014-03-02 21:31:43.687 Finanzchecker[509:907] fileSys.root.fullPath: /
2014-03-02 21:31:43.717 Finanzchecker[509:907] dir.name: pics
2014-03-02 21:31:43.726 Finanzchecker[509:907] dir.fullPath: /pics/
2014-03-02 21:31:43.778 Finanzchecker[509:907] newFileEntry.name:
pic1393792303602.jpg
2014-03-02 21:31:43.784 Finanzchecker[509:907] newFileEntry.fullPath:
/pics/pic1393792303602.jpg
2014-03-02 21:31:43.796 Finanzchecker[509:907] newFileEntry.nativeURL:
file:///var/mobile/Applications/82A8A0EF-8012-4D7E-B78D-EA3A4C2B7CBF/Documents/pics/pic1393792303602.jpg
2014-03-02 21:31:43.802 Finanzchecker[509:907] newFileEntry.toURL():
cdvfile://localhost/temporary/pics/pic1393792303602.jpg
2014-03-02 21:31:43.815 Finanzchecker[509:907] newFileEntry.filesystem.name:
temporary
2014-03-02 21:31:43.820 Finanzchecker[509:907]
newFileEntry.filesystem.root.name: '/'
2014-03-02 21:31:43.820 Finanzchecker[509:907]
newFileEntry.filesystem.root.fullPath: '/'
{noformat}
*Our problem:*
We had expected that newFileEntry.filesystem.name has to be 'persistent'
(instead it is 'temporary') . newFileEntry.toURL returns the wrong cdvfile
URL (please see Xcode output above).
{code:JavaScript|title=Shortened pseudo code:|borderStyle=solid}
// ... will be called from navigator.camera.getPicture(...)
function picSuccess(imageUrl)
{
window.resolveLocalFileSystemURL(imageUrl, _fileEntrySuccess,
_handleFileError);
function _fileEntrySuccess(tmpFileEntry)
{
var newFileName = pic + new Date().getTime() + '.jpg';
window.requestFileSystem(LocalFileSystem.PERSISTENT, 0, function(fileSys)
{
console.log(fileSys.name: + fileSys.name);
console.log(fileSys.root.name: + fileSys.root.name);
console.log(fileSys.root.fullPath: + fileSys.root.fullPath);
fileSys.root.getDirectory(pics, { create: true, exclusive: false },
function(dir)
{
console.log(dir.name: + dir.name);
console.log(dir.fullPath: + dir.fullPath);
tmpFileEntry.moveTo(dir, newFileName, function(newFileEntry)
{
console.log(newFileEntry.name: +
[jira] [Comment Edited] (CB-6148) wrong filesystem properties in entry after moveTo()
[
https://issues.apache.org/jira/browse/CB-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13919211#comment-13919211
]
Ralph S Theart edited comment on CB-6148 at 3/4/14 10:28 AM:
-
I'm sorry this might be a dumb question but how do you update the plugin so
that I can test the changes in the dev branch I tried:
cordova plugin add org.apache.cordova.file#dev
but it say it's already installed. I'm having the same issue as this user...and
have wasted a lot of time thinking it was an issue with my code. The docs are
unclear how one should update a plugin via CLI. I was able to successfully
update from 3.3.1 to 3.4.0 today but trying to figure out how to update the
file api since it continually fails. Hasn't worked since I went 3.0can not
move a file for the life of me.
sorry for the silly question found https://cordova.apache.org/ ...wish there
was an update command for the plugins as some of the plugins are dependent on
others.
was (Author: drumaboy46):
I'm sorry this might be a dumb question but how do you update the plugin so
that I can test the changes in the dev branch I tried:
cordova plugin add org.apache.cordova.file#dev
but it say it's already installed. I'm having the same issue as this user...and
have wasted a lot of time thinking it was an issue with my code. The docs are
unclear how one should update a plugin via CLI. I was able to successfully
update from 3.3.1 to 3.4.0 today but trying to figure out how to update the
file api since it continually fails. Hasn't worked since I went 3.0can not
move a file for the life of me.
sorry for the silly question found https://cordova.apache.org/...wish there was
an update command for the plugins as some of the plugins are dependent on
others.
wrong filesystem properties in entry after moveTo()
---
Key: CB-6148
URL: https://issues.apache.org/jira/browse/CB-6148
Project: Apache Cordova
Issue Type: Bug
Components: Plugin File
Affects Versions: 3.4.0
Environment: iOS6
iOS7
Reporter: Dominik Pesch
Assignee: Ian Clelland
To store pictures persistent in our app, we move the image files from the
temporary folder to the persistent folder. The code breaks after upgrading to
Cordova 3.4.0 and file plugin 1.0.0 (and 1.0.1).
We've found that the filesystem object in the moveTo success callback entry
parameter has got wrong value (please notice pseudo code below).
Below you'll see the Xcode log output:
{noformat}
2014-03-02 21:31:43.672 Finanzchecker[509:907] fileSys.name: persistent
2014-03-02 21:31:43.682 Finanzchecker[509:907] fileSys.root.name: /
2014-03-02 21:31:43.687 Finanzchecker[509:907] fileSys.root.fullPath: /
2014-03-02 21:31:43.717 Finanzchecker[509:907] dir.name: pics
2014-03-02 21:31:43.726 Finanzchecker[509:907] dir.fullPath: /pics/
2014-03-02 21:31:43.778 Finanzchecker[509:907] newFileEntry.name:
pic1393792303602.jpg
2014-03-02 21:31:43.784 Finanzchecker[509:907] newFileEntry.fullPath:
/pics/pic1393792303602.jpg
2014-03-02 21:31:43.796 Finanzchecker[509:907] newFileEntry.nativeURL:
file:///var/mobile/Applications/82A8A0EF-8012-4D7E-B78D-EA3A4C2B7CBF/Documents/pics/pic1393792303602.jpg
2014-03-02 21:31:43.802 Finanzchecker[509:907] newFileEntry.toURL():
cdvfile://localhost/temporary/pics/pic1393792303602.jpg
2014-03-02 21:31:43.815 Finanzchecker[509:907] newFileEntry.filesystem.name:
temporary
2014-03-02 21:31:43.820 Finanzchecker[509:907]
newFileEntry.filesystem.root.name: '/'
2014-03-02 21:31:43.820 Finanzchecker[509:907]
newFileEntry.filesystem.root.fullPath: '/'
{noformat}
*Our problem:*
We had expected that newFileEntry.filesystem.name has to be 'persistent'
(instead it is 'temporary') . newFileEntry.toURL returns the wrong cdvfile
URL (please see Xcode output above).
{code:JavaScript|title=Shortened pseudo code:|borderStyle=solid}
// ... will be called from navigator.camera.getPicture(...)
function picSuccess(imageUrl)
{
window.resolveLocalFileSystemURL(imageUrl, _fileEntrySuccess,
_handleFileError);
function _fileEntrySuccess(tmpFileEntry)
{
var newFileName = pic + new Date().getTime() + '.jpg';
window.requestFileSystem(LocalFileSystem.PERSISTENT, 0, function(fileSys)
{
console.log(fileSys.name: + fileSys.name);
console.log(fileSys.root.name: + fileSys.root.name);
console.log(fileSys.root.fullPath: + fileSys.root.fullPath);
fileSys.root.getDirectory(pics, { create: true, exclusive: false },
function(dir)
{
console.log(dir.name: + dir.name);
console.log(dir.fullPath: + dir.fullPath);
tmpFileEntry.moveTo(dir, newFileName, function(newFileEntry)
{
console.log(newFileEntry.name: +
[jira] [Commented] (CB-6148) wrong filesystem properties in entry after moveTo()
[
https://issues.apache.org/jira/browse/CB-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13919236#comment-13919236
]
Ralph S Theart commented on CB-6148:
Thanks Dominik..btw the .m files are almost never automatically added for me
but I know you guy's are working on it ...should I file and issue or is this
and xcode thing?
wrong filesystem properties in entry after moveTo()
---
Key: CB-6148
URL: https://issues.apache.org/jira/browse/CB-6148
Project: Apache Cordova
Issue Type: Bug
Components: Plugin File
Affects Versions: 3.4.0
Environment: iOS6
iOS7
Reporter: Dominik Pesch
Assignee: Ian Clelland
To store pictures persistent in our app, we move the image files from the
temporary folder to the persistent folder. The code breaks after upgrading to
Cordova 3.4.0 and file plugin 1.0.0 (and 1.0.1).
We've found that the filesystem object in the moveTo success callback entry
parameter has got wrong value (please notice pseudo code below).
Below you'll see the Xcode log output:
{noformat}
2014-03-02 21:31:43.672 Finanzchecker[509:907] fileSys.name: persistent
2014-03-02 21:31:43.682 Finanzchecker[509:907] fileSys.root.name: /
2014-03-02 21:31:43.687 Finanzchecker[509:907] fileSys.root.fullPath: /
2014-03-02 21:31:43.717 Finanzchecker[509:907] dir.name: pics
2014-03-02 21:31:43.726 Finanzchecker[509:907] dir.fullPath: /pics/
2014-03-02 21:31:43.778 Finanzchecker[509:907] newFileEntry.name:
pic1393792303602.jpg
2014-03-02 21:31:43.784 Finanzchecker[509:907] newFileEntry.fullPath:
/pics/pic1393792303602.jpg
2014-03-02 21:31:43.796 Finanzchecker[509:907] newFileEntry.nativeURL:
file:///var/mobile/Applications/82A8A0EF-8012-4D7E-B78D-EA3A4C2B7CBF/Documents/pics/pic1393792303602.jpg
2014-03-02 21:31:43.802 Finanzchecker[509:907] newFileEntry.toURL():
cdvfile://localhost/temporary/pics/pic1393792303602.jpg
2014-03-02 21:31:43.815 Finanzchecker[509:907] newFileEntry.filesystem.name:
temporary
2014-03-02 21:31:43.820 Finanzchecker[509:907]
newFileEntry.filesystem.root.name: '/'
2014-03-02 21:31:43.820 Finanzchecker[509:907]
newFileEntry.filesystem.root.fullPath: '/'
{noformat}
*Our problem:*
We had expected that newFileEntry.filesystem.name has to be 'persistent'
(instead it is 'temporary') . newFileEntry.toURL returns the wrong cdvfile
URL (please see Xcode output above).
{code:JavaScript|title=Shortened pseudo code:|borderStyle=solid}
// ... will be called from navigator.camera.getPicture(...)
function picSuccess(imageUrl)
{
window.resolveLocalFileSystemURL(imageUrl, _fileEntrySuccess,
_handleFileError);
function _fileEntrySuccess(tmpFileEntry)
{
var newFileName = pic + new Date().getTime() + '.jpg';
window.requestFileSystem(LocalFileSystem.PERSISTENT, 0, function(fileSys)
{
console.log(fileSys.name: + fileSys.name);
console.log(fileSys.root.name: + fileSys.root.name);
console.log(fileSys.root.fullPath: + fileSys.root.fullPath);
fileSys.root.getDirectory(pics, { create: true, exclusive: false },
function(dir)
{
console.log(dir.name: + dir.name);
console.log(dir.fullPath: + dir.fullPath);
tmpFileEntry.moveTo(dir, newFileName, function(newFileEntry)
{
console.log(newFileEntry.name: + newFileEntry.name);
console.log(newFileEntry.fullPath: + newFileEntry.fullPath);
console.log(newFileEntry.nativeURL: + newFileEntry.nativeURL);
console.log(newFileEntry.toURL(): + newFileEntry.toURL());
console.log(newFileEntry.filesystem.name: +
newFileEntry.filesystem.name);
console.log(newFileEntry.filesystem.fullPath: +
newFileEntry.filesystem.fullPath);
_fileMovedSuccess(newFileEntry);
}, _handleFileError)
})
},
_handleFileError);
}
function _fileMovedSuccess(entry)
{
// ...
}
}
{code}
We've tested this with Cordova 3.4.0 and cordova file plugin 1.0.0 and 1.0.1
(https://github.com/apache/cordova-plugin-file.git
21e119692ab9c9fb2912dc69e2c6d4b05307e3e2).
// corrected the example (some typos)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6148) wrong filesystem properties in entry after moveTo()
[
https://issues.apache.org/jira/browse/CB-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13919264#comment-13919264
]
Ralph S Theart commented on CB-6148:
Also moveTo continues to fail even after trying #dev and the new code...sigh I
don't get it...why does it keep failing. I've tried everything...were you able
to reproduce this error as well?
wrong filesystem properties in entry after moveTo()
---
Key: CB-6148
URL: https://issues.apache.org/jira/browse/CB-6148
Project: Apache Cordova
Issue Type: Bug
Components: Plugin File
Affects Versions: 3.4.0
Environment: iOS6
iOS7
Reporter: Dominik Pesch
Assignee: Ian Clelland
To store pictures persistent in our app, we move the image files from the
temporary folder to the persistent folder. The code breaks after upgrading to
Cordova 3.4.0 and file plugin 1.0.0 (and 1.0.1).
We've found that the filesystem object in the moveTo success callback entry
parameter has got wrong value (please notice pseudo code below).
Below you'll see the Xcode log output:
{noformat}
2014-03-02 21:31:43.672 Finanzchecker[509:907] fileSys.name: persistent
2014-03-02 21:31:43.682 Finanzchecker[509:907] fileSys.root.name: /
2014-03-02 21:31:43.687 Finanzchecker[509:907] fileSys.root.fullPath: /
2014-03-02 21:31:43.717 Finanzchecker[509:907] dir.name: pics
2014-03-02 21:31:43.726 Finanzchecker[509:907] dir.fullPath: /pics/
2014-03-02 21:31:43.778 Finanzchecker[509:907] newFileEntry.name:
pic1393792303602.jpg
2014-03-02 21:31:43.784 Finanzchecker[509:907] newFileEntry.fullPath:
/pics/pic1393792303602.jpg
2014-03-02 21:31:43.796 Finanzchecker[509:907] newFileEntry.nativeURL:
file:///var/mobile/Applications/82A8A0EF-8012-4D7E-B78D-EA3A4C2B7CBF/Documents/pics/pic1393792303602.jpg
2014-03-02 21:31:43.802 Finanzchecker[509:907] newFileEntry.toURL():
cdvfile://localhost/temporary/pics/pic1393792303602.jpg
2014-03-02 21:31:43.815 Finanzchecker[509:907] newFileEntry.filesystem.name:
temporary
2014-03-02 21:31:43.820 Finanzchecker[509:907]
newFileEntry.filesystem.root.name: '/'
2014-03-02 21:31:43.820 Finanzchecker[509:907]
newFileEntry.filesystem.root.fullPath: '/'
{noformat}
*Our problem:*
We had expected that newFileEntry.filesystem.name has to be 'persistent'
(instead it is 'temporary') . newFileEntry.toURL returns the wrong cdvfile
URL (please see Xcode output above).
{code:JavaScript|title=Shortened pseudo code:|borderStyle=solid}
// ... will be called from navigator.camera.getPicture(...)
function picSuccess(imageUrl)
{
window.resolveLocalFileSystemURL(imageUrl, _fileEntrySuccess,
_handleFileError);
function _fileEntrySuccess(tmpFileEntry)
{
var newFileName = pic + new Date().getTime() + '.jpg';
window.requestFileSystem(LocalFileSystem.PERSISTENT, 0, function(fileSys)
{
console.log(fileSys.name: + fileSys.name);
console.log(fileSys.root.name: + fileSys.root.name);
console.log(fileSys.root.fullPath: + fileSys.root.fullPath);
fileSys.root.getDirectory(pics, { create: true, exclusive: false },
function(dir)
{
console.log(dir.name: + dir.name);
console.log(dir.fullPath: + dir.fullPath);
tmpFileEntry.moveTo(dir, newFileName, function(newFileEntry)
{
console.log(newFileEntry.name: + newFileEntry.name);
console.log(newFileEntry.fullPath: + newFileEntry.fullPath);
console.log(newFileEntry.nativeURL: + newFileEntry.nativeURL);
console.log(newFileEntry.toURL(): + newFileEntry.toURL());
console.log(newFileEntry.filesystem.name: +
newFileEntry.filesystem.name);
console.log(newFileEntry.filesystem.fullPath: +
newFileEntry.filesystem.fullPath);
_fileMovedSuccess(newFileEntry);
}, _handleFileError)
})
},
_handleFileError);
}
function _fileMovedSuccess(entry)
{
// ...
}
}
{code}
We've tested this with Cordova 3.4.0 and cordova file plugin 1.0.0 and 1.0.1
(https://github.com/apache/cordova-plugin-file.git
21e119692ab9c9fb2912dc69e2c6d4b05307e3e2).
// corrected the example (some typos)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Comment Edited] (CB-6148) wrong filesystem properties in entry after moveTo()
[
https://issues.apache.org/jira/browse/CB-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13919264#comment-13919264
]
Ralph S Theart edited comment on CB-6148 at 3/4/14 11:22 AM:
-
Also moveTo continues to fail even after trying #dev and the new code...sigh I
don't get it...why does it keep failing. I've tried everything...were you able
to reproduce this error as well?
*EDIT*
spoke way too soon...it does work!...its 6am..I'm going to bed. Ah the weakness
devs ..we can't sleep unless it's some what solved. great work.
was (Author: drumaboy46):
Also moveTo continues to fail even after trying #dev and the new code...sigh I
don't get it...why does it keep failing. I've tried everything...were you able
to reproduce this error as well?
*EDIT*
spoke wait too soon...it does work!...its 6am..I'm going to bed. Ah the that
the weakness of a dev ..we can't sleep unless it's some what solved.
wrong filesystem properties in entry after moveTo()
---
Key: CB-6148
URL: https://issues.apache.org/jira/browse/CB-6148
Project: Apache Cordova
Issue Type: Bug
Components: Plugin File
Affects Versions: 3.4.0
Environment: iOS6
iOS7
Reporter: Dominik Pesch
Assignee: Ian Clelland
To store pictures persistent in our app, we move the image files from the
temporary folder to the persistent folder. The code breaks after upgrading to
Cordova 3.4.0 and file plugin 1.0.0 (and 1.0.1).
We've found that the filesystem object in the moveTo success callback entry
parameter has got wrong value (please notice pseudo code below).
Below you'll see the Xcode log output:
{noformat}
2014-03-02 21:31:43.672 Finanzchecker[509:907] fileSys.name: persistent
2014-03-02 21:31:43.682 Finanzchecker[509:907] fileSys.root.name: /
2014-03-02 21:31:43.687 Finanzchecker[509:907] fileSys.root.fullPath: /
2014-03-02 21:31:43.717 Finanzchecker[509:907] dir.name: pics
2014-03-02 21:31:43.726 Finanzchecker[509:907] dir.fullPath: /pics/
2014-03-02 21:31:43.778 Finanzchecker[509:907] newFileEntry.name:
pic1393792303602.jpg
2014-03-02 21:31:43.784 Finanzchecker[509:907] newFileEntry.fullPath:
/pics/pic1393792303602.jpg
2014-03-02 21:31:43.796 Finanzchecker[509:907] newFileEntry.nativeURL:
file:///var/mobile/Applications/82A8A0EF-8012-4D7E-B78D-EA3A4C2B7CBF/Documents/pics/pic1393792303602.jpg
2014-03-02 21:31:43.802 Finanzchecker[509:907] newFileEntry.toURL():
cdvfile://localhost/temporary/pics/pic1393792303602.jpg
2014-03-02 21:31:43.815 Finanzchecker[509:907] newFileEntry.filesystem.name:
temporary
2014-03-02 21:31:43.820 Finanzchecker[509:907]
newFileEntry.filesystem.root.name: '/'
2014-03-02 21:31:43.820 Finanzchecker[509:907]
newFileEntry.filesystem.root.fullPath: '/'
{noformat}
*Our problem:*
We had expected that newFileEntry.filesystem.name has to be 'persistent'
(instead it is 'temporary') . newFileEntry.toURL returns the wrong cdvfile
URL (please see Xcode output above).
{code:JavaScript|title=Shortened pseudo code:|borderStyle=solid}
// ... will be called from navigator.camera.getPicture(...)
function picSuccess(imageUrl)
{
window.resolveLocalFileSystemURL(imageUrl, _fileEntrySuccess,
_handleFileError);
function _fileEntrySuccess(tmpFileEntry)
{
var newFileName = pic + new Date().getTime() + '.jpg';
window.requestFileSystem(LocalFileSystem.PERSISTENT, 0, function(fileSys)
{
console.log(fileSys.name: + fileSys.name);
console.log(fileSys.root.name: + fileSys.root.name);
console.log(fileSys.root.fullPath: + fileSys.root.fullPath);
fileSys.root.getDirectory(pics, { create: true, exclusive: false },
function(dir)
{
console.log(dir.name: + dir.name);
console.log(dir.fullPath: + dir.fullPath);
tmpFileEntry.moveTo(dir, newFileName, function(newFileEntry)
{
console.log(newFileEntry.name: + newFileEntry.name);
console.log(newFileEntry.fullPath: + newFileEntry.fullPath);
console.log(newFileEntry.nativeURL: + newFileEntry.nativeURL);
console.log(newFileEntry.toURL(): + newFileEntry.toURL());
console.log(newFileEntry.filesystem.name: +
newFileEntry.filesystem.name);
console.log(newFileEntry.filesystem.fullPath: +
newFileEntry.filesystem.fullPath);
_fileMovedSuccess(newFileEntry);
}, _handleFileError)
})
},
_handleFileError);
}
function _fileMovedSuccess(entry)
{
// ...
}
}
{code}
We've tested this with Cordova 3.4.0 and cordova file plugin 1.0.0 and 1.0.1
(https://github.com/apache/cordova-plugin-file.git
21e119692ab9c9fb2912dc69e2c6d4b05307e3e2).
// corrected the example (some typos)
--
This message was sent
[jira] [Comment Edited] (CB-6148) wrong filesystem properties in entry after moveTo()
[
https://issues.apache.org/jira/browse/CB-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13919264#comment-13919264
]
Ralph S Theart edited comment on CB-6148 at 3/4/14 11:21 AM:
-
Also moveTo continues to fail even after trying #dev and the new code...sigh I
don't get it...why does it keep failing. I've tried everything...were you able
to reproduce this error as well?
*EDIT*
spoke wait too soon...it does work!...its 6am..I'm going to bed. Ah the that
the weakness of a dev ..we can't sleep unless it's some what solved.
was (Author: drumaboy46):
Also moveTo continues to fail even after trying #dev and the new code...sigh I
don't get it...why does it keep failing. I've tried everything...were you able
to reproduce this error as well?
wrong filesystem properties in entry after moveTo()
---
Key: CB-6148
URL: https://issues.apache.org/jira/browse/CB-6148
Project: Apache Cordova
Issue Type: Bug
Components: Plugin File
Affects Versions: 3.4.0
Environment: iOS6
iOS7
Reporter: Dominik Pesch
Assignee: Ian Clelland
To store pictures persistent in our app, we move the image files from the
temporary folder to the persistent folder. The code breaks after upgrading to
Cordova 3.4.0 and file plugin 1.0.0 (and 1.0.1).
We've found that the filesystem object in the moveTo success callback entry
parameter has got wrong value (please notice pseudo code below).
Below you'll see the Xcode log output:
{noformat}
2014-03-02 21:31:43.672 Finanzchecker[509:907] fileSys.name: persistent
2014-03-02 21:31:43.682 Finanzchecker[509:907] fileSys.root.name: /
2014-03-02 21:31:43.687 Finanzchecker[509:907] fileSys.root.fullPath: /
2014-03-02 21:31:43.717 Finanzchecker[509:907] dir.name: pics
2014-03-02 21:31:43.726 Finanzchecker[509:907] dir.fullPath: /pics/
2014-03-02 21:31:43.778 Finanzchecker[509:907] newFileEntry.name:
pic1393792303602.jpg
2014-03-02 21:31:43.784 Finanzchecker[509:907] newFileEntry.fullPath:
/pics/pic1393792303602.jpg
2014-03-02 21:31:43.796 Finanzchecker[509:907] newFileEntry.nativeURL:
file:///var/mobile/Applications/82A8A0EF-8012-4D7E-B78D-EA3A4C2B7CBF/Documents/pics/pic1393792303602.jpg
2014-03-02 21:31:43.802 Finanzchecker[509:907] newFileEntry.toURL():
cdvfile://localhost/temporary/pics/pic1393792303602.jpg
2014-03-02 21:31:43.815 Finanzchecker[509:907] newFileEntry.filesystem.name:
temporary
2014-03-02 21:31:43.820 Finanzchecker[509:907]
newFileEntry.filesystem.root.name: '/'
2014-03-02 21:31:43.820 Finanzchecker[509:907]
newFileEntry.filesystem.root.fullPath: '/'
{noformat}
*Our problem:*
We had expected that newFileEntry.filesystem.name has to be 'persistent'
(instead it is 'temporary') . newFileEntry.toURL returns the wrong cdvfile
URL (please see Xcode output above).
{code:JavaScript|title=Shortened pseudo code:|borderStyle=solid}
// ... will be called from navigator.camera.getPicture(...)
function picSuccess(imageUrl)
{
window.resolveLocalFileSystemURL(imageUrl, _fileEntrySuccess,
_handleFileError);
function _fileEntrySuccess(tmpFileEntry)
{
var newFileName = pic + new Date().getTime() + '.jpg';
window.requestFileSystem(LocalFileSystem.PERSISTENT, 0, function(fileSys)
{
console.log(fileSys.name: + fileSys.name);
console.log(fileSys.root.name: + fileSys.root.name);
console.log(fileSys.root.fullPath: + fileSys.root.fullPath);
fileSys.root.getDirectory(pics, { create: true, exclusive: false },
function(dir)
{
console.log(dir.name: + dir.name);
console.log(dir.fullPath: + dir.fullPath);
tmpFileEntry.moveTo(dir, newFileName, function(newFileEntry)
{
console.log(newFileEntry.name: + newFileEntry.name);
console.log(newFileEntry.fullPath: + newFileEntry.fullPath);
console.log(newFileEntry.nativeURL: + newFileEntry.nativeURL);
console.log(newFileEntry.toURL(): + newFileEntry.toURL());
console.log(newFileEntry.filesystem.name: +
newFileEntry.filesystem.name);
console.log(newFileEntry.filesystem.fullPath: +
newFileEntry.filesystem.fullPath);
_fileMovedSuccess(newFileEntry);
}, _handleFileError)
})
},
_handleFileError);
}
function _fileMovedSuccess(entry)
{
// ...
}
}
{code}
We've tested this with Cordova 3.4.0 and cordova file plugin 1.0.0 and 1.0.1
(https://github.com/apache/cordova-plugin-file.git
21e119692ab9c9fb2912dc69e2c6d4b05307e3e2).
// corrected the example (some typos)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6148) wrong filesystem properties in entry after moveTo()
[
https://issues.apache.org/jira/browse/CB-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13919412#comment-13919412
]
Ralph S Theart commented on CB-6148:
Yes thanks again.
wrong filesystem properties in entry after moveTo()
---
Key: CB-6148
URL: https://issues.apache.org/jira/browse/CB-6148
Project: Apache Cordova
Issue Type: Bug
Components: Plugin File
Affects Versions: 3.4.0
Environment: iOS6
iOS7
Reporter: Dominik Pesch
Assignee: Ian Clelland
To store pictures persistent in our app, we move the image files from the
temporary folder to the persistent folder. The code breaks after upgrading to
Cordova 3.4.0 and file plugin 1.0.0 (and 1.0.1).
We've found that the filesystem object in the moveTo success callback entry
parameter has got wrong value (please notice pseudo code below).
Below you'll see the Xcode log output:
{noformat}
2014-03-02 21:31:43.672 Finanzchecker[509:907] fileSys.name: persistent
2014-03-02 21:31:43.682 Finanzchecker[509:907] fileSys.root.name: /
2014-03-02 21:31:43.687 Finanzchecker[509:907] fileSys.root.fullPath: /
2014-03-02 21:31:43.717 Finanzchecker[509:907] dir.name: pics
2014-03-02 21:31:43.726 Finanzchecker[509:907] dir.fullPath: /pics/
2014-03-02 21:31:43.778 Finanzchecker[509:907] newFileEntry.name:
pic1393792303602.jpg
2014-03-02 21:31:43.784 Finanzchecker[509:907] newFileEntry.fullPath:
/pics/pic1393792303602.jpg
2014-03-02 21:31:43.796 Finanzchecker[509:907] newFileEntry.nativeURL:
file:///var/mobile/Applications/82A8A0EF-8012-4D7E-B78D-EA3A4C2B7CBF/Documents/pics/pic1393792303602.jpg
2014-03-02 21:31:43.802 Finanzchecker[509:907] newFileEntry.toURL():
cdvfile://localhost/temporary/pics/pic1393792303602.jpg
2014-03-02 21:31:43.815 Finanzchecker[509:907] newFileEntry.filesystem.name:
temporary
2014-03-02 21:31:43.820 Finanzchecker[509:907]
newFileEntry.filesystem.root.name: '/'
2014-03-02 21:31:43.820 Finanzchecker[509:907]
newFileEntry.filesystem.root.fullPath: '/'
{noformat}
*Our problem:*
We had expected that newFileEntry.filesystem.name has to be 'persistent'
(instead it is 'temporary') . newFileEntry.toURL returns the wrong cdvfile
URL (please see Xcode output above).
{code:JavaScript|title=Shortened pseudo code:|borderStyle=solid}
// ... will be called from navigator.camera.getPicture(...)
function picSuccess(imageUrl)
{
window.resolveLocalFileSystemURL(imageUrl, _fileEntrySuccess,
_handleFileError);
function _fileEntrySuccess(tmpFileEntry)
{
var newFileName = pic + new Date().getTime() + '.jpg';
window.requestFileSystem(LocalFileSystem.PERSISTENT, 0, function(fileSys)
{
console.log(fileSys.name: + fileSys.name);
console.log(fileSys.root.name: + fileSys.root.name);
console.log(fileSys.root.fullPath: + fileSys.root.fullPath);
fileSys.root.getDirectory(pics, { create: true, exclusive: false },
function(dir)
{
console.log(dir.name: + dir.name);
console.log(dir.fullPath: + dir.fullPath);
tmpFileEntry.moveTo(dir, newFileName, function(newFileEntry)
{
console.log(newFileEntry.name: + newFileEntry.name);
console.log(newFileEntry.fullPath: + newFileEntry.fullPath);
console.log(newFileEntry.nativeURL: + newFileEntry.nativeURL);
console.log(newFileEntry.toURL(): + newFileEntry.toURL());
console.log(newFileEntry.filesystem.name: +
newFileEntry.filesystem.name);
console.log(newFileEntry.filesystem.fullPath: +
newFileEntry.filesystem.fullPath);
_fileMovedSuccess(newFileEntry);
}, _handleFileError)
})
},
_handleFileError);
}
function _fileMovedSuccess(entry)
{
// ...
}
}
{code}
We've tested this with Cordova 3.4.0 and cordova file plugin 1.0.0 and 1.0.1
(https://github.com/apache/cordova-plugin-file.git
21e119692ab9c9fb2912dc69e2c6d4b05307e3e2).
// corrected the example (some typos)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6116) Cordova resolveLocalFileSystemURL success call back failing on iOS
[
https://issues.apache.org/jira/browse/CB-6116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13915936#comment-13915936
]
Ralph S Theart commented on CB-6116:
I tried your suggestion but to no avail. I did cordova info so at least you
know what I have if it might help
Current Node Version: v0.10.25
Current Cordova CLI Version: 3.3.1-0.4.2
I noticed that when I have the camera option
*destinationType = Camera.DestinationType.FILE_URI;*
There is a slight pause after I have chosen and image...it just sits there for
a few milliseconds. It's noticeably slower than if I set it to NATIVE_URI for
some reason.
At any rate here is the new code I tried with a fixed path to a temp image I
verified existed by using xcode's Organizer to look at my application.
{quote}
urlToResolve =
'file://localhost/var/mobile/Applications/B819A941-0CBF-4321-9B1D-94E2B01DAE97/tmp/cdv_photo_001.jpg';
window.resolveLocalFileSystemURL(urlToResolve, function(fileEntry){
console.log('RESOLVED');
}, function(error){
console.log('COULD NOT RESOLVE');
});
{quote}
None of the call backs ever gets called...what should I do...I have not idea
what the issue is?? If I use remove the urlToResolve that I have and feed it
dynamically from the call back of navigator.camera.getPicture() with NATIVE_URI
set, the success callback gets triggered and it will say RESOLVED...something
wrong with the camera api?
Cordova resolveLocalFileSystemURL success call back failing on iOS
--
Key: CB-6116
URL: https://issues.apache.org/jira/browse/CB-6116
Project: Apache Cordova
Issue Type: Bug
Components: iOS, Plugin Camera, Plugin File
Affects Versions: 3.3.0
Reporter: Ralph S Theart
Assignee: Ian Clelland
Labels: camera, file, plugin, resolveLocalFileSystemURI
I've just created a new project and installed the file and file-transfer
api's via CLI. I have already created a working app previously so I know how
to use phonegap and have been doing so for a few years now.
Here is the code:
uri from navigator.camera.getPicture():
file:///localhost/var/mobile/Applications/96B4705C-C70D-4340-9A42-HJ1F28355D43/tmp/cdv_photo_015.jpg
window.resolveLocalFileSystemURL(uri, function(fileEntry){
console.log(fileEntry.name);
}, function(error){
console.log('about to resolve this files errors');
console.log(error.code);
});
Nothing ever gets outputted in the console debugging window ...and yes I have
debug installed cause I have console.log() in other parts of my code that
show up.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (CB-6116) Cordova resolveLocalFileSystemURL success call back failing on iOS
[
https://issues.apache.org/jira/browse/CB-6116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13915937#comment-13915937
]
Ralph S Theart commented on CB-6116:
sorry posted this after I saw your comment.
File: v1.0.0
Camera: v0.2.7
Cordova resolveLocalFileSystemURL success call back failing on iOS
--
Key: CB-6116
URL: https://issues.apache.org/jira/browse/CB-6116
Project: Apache Cordova
Issue Type: Bug
Components: iOS, Plugin Camera, Plugin File
Affects Versions: 3.3.0
Reporter: Ralph S Theart
Assignee: Ian Clelland
Labels: camera, file, plugin, resolveLocalFileSystemURI
I've just created a new project and installed the file and file-transfer
api's via CLI. I have already created a working app previously so I know how
to use phonegap and have been doing so for a few years now.
Here is the code:
uri from navigator.camera.getPicture():
file:///localhost/var/mobile/Applications/96B4705C-C70D-4340-9A42-HJ1F28355D43/tmp/cdv_photo_015.jpg
window.resolveLocalFileSystemURL(uri, function(fileEntry){
console.log(fileEntry.name);
}, function(error){
console.log('about to resolve this files errors');
console.log(error.code);
});
Nothing ever gets outputted in the console debugging window ...and yes I have
debug installed cause I have console.log() in other parts of my code that
show up.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (CB-6116) Cordova resolveLocalFileSystemURL success call back failing on iOS
[
https://issues.apache.org/jira/browse/CB-6116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13915951#comment-13915951
]
Ralph S Theart commented on CB-6116:
Thanks Ian I'm going to try some more things. It's so strange but I think you
might be right. I've also already uninstalled file-transfer/file and
reinstalled. I'll you know how further testing goes.
Cordova resolveLocalFileSystemURL success call back failing on iOS
--
Key: CB-6116
URL: https://issues.apache.org/jira/browse/CB-6116
Project: Apache Cordova
Issue Type: Bug
Components: iOS, Plugin Camera, Plugin File
Affects Versions: 3.3.0
Reporter: Ralph S Theart
Assignee: Ian Clelland
Labels: camera, file, plugin, resolveLocalFileSystemURI
I've just created a new project and installed the file and file-transfer
api's via CLI. I have already created a working app previously so I know how
to use phonegap and have been doing so for a few years now.
Here is the code:
uri from navigator.camera.getPicture():
file:///localhost/var/mobile/Applications/96B4705C-C70D-4340-9A42-HJ1F28355D43/tmp/cdv_photo_015.jpg
window.resolveLocalFileSystemURL(uri, function(fileEntry){
console.log(fileEntry.name);
}, function(error){
console.log('about to resolve this files errors');
console.log(error.code);
});
Nothing ever gets outputted in the console debugging window ...and yes I have
debug installed cause I have console.log() in other parts of my code that
show up.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (CB-6116) Cordova resolveLocalFileSystemURL success call back failing on iOS
[
https://issues.apache.org/jira/browse/CB-6116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13915956#comment-13915956
]
Ralph S Theart commented on CB-6116:
Really wish the site would auto update comments...keep commenting before I get
your comments :/
Just tried your suggestion and of course it worked.
Cordova resolveLocalFileSystemURL success call back failing on iOS
--
Key: CB-6116
URL: https://issues.apache.org/jira/browse/CB-6116
Project: Apache Cordova
Issue Type: Bug
Components: iOS, Plugin Camera, Plugin File
Affects Versions: 3.3.0
Reporter: Ralph S Theart
Assignee: Ian Clelland
Labels: camera, file, plugin, resolveLocalFileSystemURI
I've just created a new project and installed the file and file-transfer
api's via CLI. I have already created a working app previously so I know how
to use phonegap and have been doing so for a few years now.
Here is the code:
uri from navigator.camera.getPicture():
file:///localhost/var/mobile/Applications/96B4705C-C70D-4340-9A42-HJ1F28355D43/tmp/cdv_photo_015.jpg
window.resolveLocalFileSystemURL(uri, function(fileEntry){
console.log(fileEntry.name);
}, function(error){
console.log('about to resolve this files errors');
console.log(error.code);
});
Nothing ever gets outputted in the console debugging window ...and yes I have
debug installed cause I have console.log() in other parts of my code that
show up.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (CB-6116) Cordova resolveLocalFileSystemURL success call back failing on iOS
[
https://issues.apache.org/jira/browse/CB-6116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13915963#comment-13915963
]
Ralph S Theart commented on CB-6116:
Also using the fixed url without localhost I get it to resolve as stated in my
last comment. But to further test the camera api when I use...
NATIVE_URL: ['Camera'] took '*185*.970947' ms.
vs.
FILE_URI: ['Camera'] took '*1321*.890137' ms.
see the diff ..it's weird. I have done anything extra just followed the docs of
cordova.
Cordova resolveLocalFileSystemURL success call back failing on iOS
--
Key: CB-6116
URL: https://issues.apache.org/jira/browse/CB-6116
Project: Apache Cordova
Issue Type: Bug
Components: iOS, Plugin Camera, Plugin File
Affects Versions: 3.3.0
Reporter: Ralph S Theart
Assignee: Ian Clelland
Labels: camera, file, plugin, resolveLocalFileSystemURI
I've just created a new project and installed the file and file-transfer
api's via CLI. I have already created a working app previously so I know how
to use phonegap and have been doing so for a few years now.
Here is the code:
uri from navigator.camera.getPicture():
file:///localhost/var/mobile/Applications/96B4705C-C70D-4340-9A42-HJ1F28355D43/tmp/cdv_photo_015.jpg
window.resolveLocalFileSystemURL(uri, function(fileEntry){
console.log(fileEntry.name);
}, function(error){
console.log('about to resolve this files errors');
console.log(error.code);
});
Nothing ever gets outputted in the console debugging window ...and yes I have
debug installed cause I have console.log() in other parts of my code that
show up.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Comment Edited] (CB-6116) Cordova resolveLocalFileSystemURL success call back failing on iOS
[
https://issues.apache.org/jira/browse/CB-6116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13915963#comment-13915963
]
Ralph S Theart edited comment on CB-6116 at 2/28/14 4:42 PM:
-
Also using the fixed url without localhost I get it to resolve as stated in my
last comment. But to further test the camera api when I use...
NATIVE_URL: ['Camera'] took '*185*.970947' ms.
vs.
FILE_URI: ['Camera'] took '*1321*.890137' ms.
see the diff ..it's weird. I haven't done anything extra just followed the docs
of cordova.
was (Author: drumaboy46):
Also using the fixed url without localhost I get it to resolve as stated in my
last comment. But to further test the camera api when I use...
NATIVE_URL: ['Camera'] took '*185*.970947' ms.
vs.
FILE_URI: ['Camera'] took '*1321*.890137' ms.
see the diff ..it's weird. I have done anything extra just followed the docs of
cordova.
Cordova resolveLocalFileSystemURL success call back failing on iOS
--
Key: CB-6116
URL: https://issues.apache.org/jira/browse/CB-6116
Project: Apache Cordova
Issue Type: Bug
Components: iOS, Plugin Camera, Plugin File
Affects Versions: 3.3.0
Reporter: Ralph S Theart
Assignee: Ian Clelland
Labels: camera, file, plugin, resolveLocalFileSystemURI
I've just created a new project and installed the file and file-transfer
api's via CLI. I have already created a working app previously so I know how
to use phonegap and have been doing so for a few years now.
Here is the code:
uri from navigator.camera.getPicture():
file:///localhost/var/mobile/Applications/96B4705C-C70D-4340-9A42-HJ1F28355D43/tmp/cdv_photo_015.jpg
window.resolveLocalFileSystemURL(uri, function(fileEntry){
console.log(fileEntry.name);
}, function(error){
console.log('about to resolve this files errors');
console.log(error.code);
});
Nothing ever gets outputted in the console debugging window ...and yes I have
debug installed cause I have console.log() in other parts of my code that
show up.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (CB-6116) Cordova resolveLocalFileSystemURL success call back failing on iOS
[
https://issues.apache.org/jira/browse/CB-6116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13915979#comment-13915979
]
Ralph S Theart commented on CB-6116:
sure thanks again Ian..also if fix won't make it by v1.0.1 should I just string
replace the url to be file:/// without /localhost/ there right? in the mean
time.
Cordova resolveLocalFileSystemURL success call back failing on iOS
--
Key: CB-6116
URL: https://issues.apache.org/jira/browse/CB-6116
Project: Apache Cordova
Issue Type: Bug
Components: iOS, Plugin Camera, Plugin File
Affects Versions: 3.3.0
Reporter: Ralph S Theart
Assignee: Ian Clelland
Labels: camera, file, plugin, resolveLocalFileSystemURI
I've just created a new project and installed the file and file-transfer
api's via CLI. I have already created a working app previously so I know how
to use phonegap and have been doing so for a few years now.
Here is the code:
uri from navigator.camera.getPicture():
file:///localhost/var/mobile/Applications/96B4705C-C70D-4340-9A42-HJ1F28355D43/tmp/cdv_photo_015.jpg
window.resolveLocalFileSystemURL(uri, function(fileEntry){
console.log(fileEntry.name);
}, function(error){
console.log('about to resolve this files errors');
console.log(error.code);
});
Nothing ever gets outputted in the console debugging window ...and yes I have
debug installed cause I have console.log() in other parts of my code that
show up.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Created] (CB-6135) Camera api takes long time to return uri when using Camera.DestinationType.FILE_URI
Ralph S Theart created CB-6135:
--
Summary: Camera api takes long time to return uri when using
Camera.DestinationType.FILE_URI
Key: CB-6135
URL: https://issues.apache.org/jira/browse/CB-6135
Project: Apache Cordova
Issue Type: Bug
Components: iOS
Affects Versions: 3.3.0
Reporter: Ralph S Theart
For some reason there is a slight pause(it's very noticeable, almost seems like
app is about to crash) when choosing an image from the photo library when use
FILE_URI...if I use NATIVE_URL when I choose a picture there is no such pause.
Here is some code:
captureImage: function(){
var onPhotoFail = function(message){
//console.log(message);
}
var pictureSource; // picture source
var destinationType; // sets the format of returned value
var onPhotoConfirm = function(buttonIndex){
destinationType = Camera.DestinationType.NATIVE_URI;
switch(buttonIndex)
{
case 1:
pictureSource=
Camera.PictureSourceType.CAMERA;
break;
case 2:
pictureSource=
Camera.PictureSourceType.PHOTOLIBRARY;
break;
}
if(buttonIndex == 1 || buttonIndex == 2){
navigator.camera.getPicture(Messaging.createFileEntry, onPhotoFail, {
destinationType: 1,
sourceType: pictureSource,
mediaType : Camera.MediaType.ALLMEDIA,
/* encodingType: Camera.EncodingType.JPEG,
*/
allowEdit : false,
saveToPhotoAlbum: false,
quality: 50
});
}
}
urapp.notify.confirm('Image Capture','What would you like to
do?',[Take Photo,Choose Existing, 'Cancel'],onPhotoConfirm);
},
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Created] (CB-6116) Cordova resolveLocalFileSystemURL success call back failing on iOS
Ralph S Theart created CB-6116:
--
Summary: Cordova resolveLocalFileSystemURL success call back
failing on iOS
Key: CB-6116
URL: https://issues.apache.org/jira/browse/CB-6116
Project: Apache Cordova
Issue Type: Bug
Components: iOS, Plugin Camera, Plugin File
Affects Versions: 3.3.0
Reporter: Ralph S Theart
I've just created a new project and installed the file and file-transfer api's
via CLI. I have already created a working app previously so I know how to use
phonegap and have been doing so for a few years now.
Here is the code:
uri from navigator.camera.getPicture():
file:///localhost/var/mobile/Applications/96B4705C-C70D-4340-9A42-HJ1F28355D43/tmp/cdv_photo_015.jpg
window.resolveLocalFileSystemURL(uri, function(fileEntry){
console.log(fileEntry.name);
}, function(error){
console.log('about to resolve this files errors');
console.log(error.code);
});
Nothing ever gets outputted in the console debugging window ...and yes I have
debug installed cause I have console.log() in other parts of my code that show
up.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
