[jira] [Resolved] (CB-7687) iOS8 : Unable to use iosExtraFileSystems
[
https://issues.apache.org/jira/browse/CB-7687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thibault Durand resolved CB-7687.
-
Resolution: Fixed
Well, it was an undocumented feature that works, to make it work you should do
that:
All credit for this answer goes to Wei Li:
https://github.com/weili-feedhenry/dotfiles/issues/1 , and you should read his
post on cordova file system plugin:
http://www.feedhenry.com/several-ways-avoid-problems-cordova-file-api-mobile-apps/
Apparently the File API doc is not up to date, in order to retrieve the file
system you wanted, you need to change the request file system type in
requestFileSystem call. For example:
window.requestFileSystem(3, 0, function(fs){
alert(dataDirectory = + cordova.file.dataDirectory);
alert(root = + fs.root.toURL());
fs.root.getFile(test.txt, {create: true, exclusive: true});
}, function(){
alert(failed to get file system”)
});
notice that the file system type in the above call is “3” - given that you only
added the following preferences in the config.xml file:
If you change the value of iosExtraFilesystems, you may need to adjust the
value of the request type accordingly.
iOS8 : Unable to use iosExtraFileSystems
Key: CB-7687
URL: https://issues.apache.org/jira/browse/CB-7687
Project: Apache Cordova
Issue Type: Bug
Components: Plugin File
Affects Versions: 3.4.0, 3.5.0, 3.6.0
Environment: iOS 8
Reporter: Thibault Durand
Hello,
I'm working with the filesystem plugin and i've an issue on iOS.
I need to open a filesystem on the Library/NoCloud directory, the
documentation on github says that we should set these two variable in the
config.xml:
preference name=iosPersistentFileLocation value=Library /
preference name=iosExtraFilesystems value=library-nosync /
But when i request the filesystem it gave me this path: Library/files , and
i'm unable to move to Library/NoCloud because the root is files.
window.requestFileSystem(LocalFileSystem.PERSISTENT, 0, function(fs) {
console.log(init fs sucess);
},function(error) {
console.log(Error init fs+ error.code);
});
I don't know if it's a bug or i've misinterpreted the documentation.
To reproduce it, you can:
- create a test app
- install the file system plugin
- set these two variable in config.xml:
preference name=iosPersistentFileLocation value=Library /
preference name=iosExtraFilesystems value=library-nosync /
- request the file system, the path is: Library/files
Thanks a lot.
Best regards,
Thibault
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CB-7687) iOS8 : Unable to use iosExtraFileSystems
[
https://issues.apache.org/jira/browse/CB-7687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14156691#comment-14156691
]
Thibault Durand commented on CB-7687:
-
I've send a pull request for the documentation on github :
https://github.com/apache/cordova-plugin-file/pull/82
iOS8 : Unable to use iosExtraFileSystems
Key: CB-7687
URL: https://issues.apache.org/jira/browse/CB-7687
Project: Apache Cordova
Issue Type: Bug
Components: Plugin File
Affects Versions: 3.4.0, 3.5.0, 3.6.0
Environment: iOS 8
Reporter: Thibault Durand
Hello,
I'm working with the filesystem plugin and i've an issue on iOS.
I need to open a filesystem on the Library/NoCloud directory, the
documentation on github says that we should set these two variable in the
config.xml:
preference name=iosPersistentFileLocation value=Library /
preference name=iosExtraFilesystems value=library-nosync /
But when i request the filesystem it gave me this path: Library/files , and
i'm unable to move to Library/NoCloud because the root is files.
window.requestFileSystem(LocalFileSystem.PERSISTENT, 0, function(fs) {
console.log(init fs sucess);
},function(error) {
console.log(Error init fs+ error.code);
});
I don't know if it's a bug or i've misinterpreted the documentation.
To reproduce it, you can:
- create a test app
- install the file system plugin
- set these two variable in config.xml:
preference name=iosPersistentFileLocation value=Library /
preference name=iosExtraFilesystems value=library-nosync /
- request the file system, the path is: Library/files
Thanks a lot.
Best regards,
Thibault
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CB-6011) Cordova Media doesn't work properly on Kindle Fire (Android 2.3)
[
https://issues.apache.org/jira/browse/CB-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thibault Durand updated CB-6011:
Description:
Hello,
I have an issue with my Kindle Fire (Android 2.3)
First, i've managed to create a sample app to reproduce the bug:
https://github.com/mosalingua/cordova-sampleapp-bug-media-sound-kindle
You can download the apk here :
https://github.com/mosalingua/cordova-sampleapp-bug-media-sound-kindle/raw/master/platforms/android/bin/HelloWorld-debug.apk
This app just has a button to play a sound, and we can visualise the Media
Callback when they are called.
And the problem is that on the Kindle Fire (Based on Android OS 2.3.3), the
callback mediaSuccess isn't called.
I've tested on these devices:
- Kindle Fire (1st GEN), Android 2.3.3 = KO
- Nexus 7, Android 4.4 = OK
- Samsung Galaxy S1, Android 2.3.3 = OK
- Samsung Galaxy S2, Android 4.0.4 = OK
As i've released my app on Amazon, i'm currently blocked on this platform to
keep releasing update, mi last update was based on cordova 2.7, which worked
fine on Kindle.
I've dug into the Media Plugin, and i've find out that int the AudioPlayer.java
, the setState method is working just fine, and send this message to the
javascript part with the correct status. ( 4 == MEDIA_STOPPED )
cordova.require('org.apache.cordova.media.Media').onStatus('c5f1ec7b-9cdf-0a49-3f62-0def8bd2d9b2',
1, 4);
But, when i put a console.log in the Media.onStatus callback in the Media.js
file, i don't get anything, it seems that the message isn't caught.
So my question is : Do you see how that could be possible ?
Thanks, i can give you more information if needed.
Best regards,
Thibault
was:
Hello,
I have an issue with my Kindle Fire (Android 2.3)
First, i've managed to create a sample app to reproduce the bug:
https://github.com/mosalingua/cordova-sampleapp-bug-media-sound-kindle
You can download the apk here :
https://github.com/mosalingua/cordova-sampleapp-bug-media-sound-kindle/raw/master/platforms/android/bin/HelloWorld-debug.apk
This app just has a button to play a sound, and we can visualise the Media
Callback when they are called.
And the problem is that on the Kindle Fire (Based on Android OS 2.3.3), the
callback mediaSuccess isn't called.
I've tested on these devices:
- Kindle Fire (1st GEN), Android 2.3.3 = KO
- Nexus 7, Android 4.4 = OK
- Samsung Galaxy S1, Android 2.3.3 = OK
- Samsung Galaxy S2, Android 4.0.4 = OK
As i've released my app on Amazon, i'm currently blocked on this platform to
keep releasing update, mi last update was bases on cordova 2.7, which worked
fine on Kindle.
I've dug into the Media Plugin, and i've find out that int the AudioPlayer.java
, the setState method is working just fine, and send this message to the
javascript part with the correct status. ( 4 == MEDIA_STOPPED )
cordova.require('org.apache.cordova.media.Media').onStatus('c5f1ec7b-9cdf-0a49-3f62-0def8bd2d9b2',
1, 4);
But, when i put a console.log in the Media.onStatus callback in the Media.js
file, i don't get anything, it seems that the message isn't caught.
So my question is : Do you see how that could be possible ?
Thanks, i can give you more information if needed.
Best regards,
Thibault
Cordova Media doesn't work properly on Kindle Fire (Android 2.3)
Key: CB-6011
URL: https://issues.apache.org/jira/browse/CB-6011
Project: Apache Cordova
Issue Type: Bug
Components: Android
Affects Versions: 3.3.0
Environment: Kindle Fire (1st generation ), Based on Android OS 2.3.3
Reporter: Thibault Durand
Priority: Blocker
Hello,
I have an issue with my Kindle Fire (Android 2.3)
First, i've managed to create a sample app to reproduce the bug:
https://github.com/mosalingua/cordova-sampleapp-bug-media-sound-kindle
You can download the apk here :
https://github.com/mosalingua/cordova-sampleapp-bug-media-sound-kindle/raw/master/platforms/android/bin/HelloWorld-debug.apk
This app just has a button to play a sound, and we can visualise the Media
Callback when they are called.
And the problem is that on the Kindle Fire (Based on Android OS 2.3.3), the
callback mediaSuccess isn't called.
I've tested on these devices:
- Kindle Fire (1st GEN), Android 2.3.3 = KO
- Nexus 7, Android 4.4 = OK
- Samsung Galaxy S1, Android 2.3.3 = OK
- Samsung Galaxy S2, Android 4.0.4 = OK
As i've released my app on Amazon, i'm currently blocked on this platform to
keep releasing update, mi last update was based on cordova 2.7, which worked
fine on Kindle.
I've dug into the Media Plugin, and i've find out that int the
AudioPlayer.java , the setState method is working just fine, and send this
message to the javascript part with the correct status. ( 4 == MEDIA_STOPPED )
[jira] [Updated] (CB-6011) Cordova Media doesn't work properly on Kindle Fire (Android 2.3)
[
https://issues.apache.org/jira/browse/CB-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thibault Durand updated CB-6011:
Description:
Hello,
I have an issue with my Kindle Fire (Android 2.3)
First, i've managed to create a sample app to reproduce the bug:
https://github.com/mosalingua/cordova-sampleapp-bug-media-sound-kindle
You can download the apk here :
https://github.com/mosalingua/cordova-sampleapp-bug-media-sound-kindle/raw/master/platforms/android/bin/HelloWorld-debug.apk
This app just has a button to play a sound, and we can visualise the Media
Callback when they are called.
And the problem is that on the Kindle Fire (Based on Android OS 2.3.3), the
callback mediaSuccess isn't called.
I've tested on these devices:
- Kindle Fire (1st GEN), Android 2.3.3 = KO
- Nexus 7, Android 4.4 = OK
- Samsung Galaxy S1, Android 2.3.3 = OK
- Samsung Galaxy S2, Android 4.0.4 = OK
As i've released my app on Amazon, i'm currently blocked on this platform to
keep releasing update, my last update was based on cordova 2.7, which worked
fine on Kindle.
I've dug into the Media Plugin, and i've find out that in the AudioPlayer.java
, the setState method is working just fine, and send this message to the
javascript part with the correct status ( 4 == MEDIA_STOPPED ):
cordova.require('org.apache.cordova.media.Media').onStatus('c5f1ec7b-9cdf-0a49-3f62-0def8bd2d9b2',
1, 4);
But, when i put a console.log in the Media.onStatus callback in the Media.js
file, i don't get anything, it seems that the message isn't caught.
So my question is : Do you see how that could be possible ?
Thanks, i can give you more information if needed.
Best regards,
Thibault
was:
Hello,
I have an issue with my Kindle Fire (Android 2.3)
First, i've managed to create a sample app to reproduce the bug:
https://github.com/mosalingua/cordova-sampleapp-bug-media-sound-kindle
You can download the apk here :
https://github.com/mosalingua/cordova-sampleapp-bug-media-sound-kindle/raw/master/platforms/android/bin/HelloWorld-debug.apk
This app just has a button to play a sound, and we can visualise the Media
Callback when they are called.
And the problem is that on the Kindle Fire (Based on Android OS 2.3.3), the
callback mediaSuccess isn't called.
I've tested on these devices:
- Kindle Fire (1st GEN), Android 2.3.3 = KO
- Nexus 7, Android 4.4 = OK
- Samsung Galaxy S1, Android 2.3.3 = OK
- Samsung Galaxy S2, Android 4.0.4 = OK
As i've released my app on Amazon, i'm currently blocked on this platform to
keep releasing update, mi last update was based on cordova 2.7, which worked
fine on Kindle.
I've dug into the Media Plugin, and i've find out that int the AudioPlayer.java
, the setState method is working just fine, and send this message to the
javascript part with the correct status. ( 4 == MEDIA_STOPPED )
cordova.require('org.apache.cordova.media.Media').onStatus('c5f1ec7b-9cdf-0a49-3f62-0def8bd2d9b2',
1, 4);
But, when i put a console.log in the Media.onStatus callback in the Media.js
file, i don't get anything, it seems that the message isn't caught.
So my question is : Do you see how that could be possible ?
Thanks, i can give you more information if needed.
Best regards,
Thibault
Cordova Media doesn't work properly on Kindle Fire (Android 2.3)
Key: CB-6011
URL: https://issues.apache.org/jira/browse/CB-6011
Project: Apache Cordova
Issue Type: Bug
Components: Android
Affects Versions: 3.3.0
Environment: Kindle Fire (1st generation ), Based on Android OS 2.3.3
Reporter: Thibault Durand
Priority: Blocker
Hello,
I have an issue with my Kindle Fire (Android 2.3)
First, i've managed to create a sample app to reproduce the bug:
https://github.com/mosalingua/cordova-sampleapp-bug-media-sound-kindle
You can download the apk here :
https://github.com/mosalingua/cordova-sampleapp-bug-media-sound-kindle/raw/master/platforms/android/bin/HelloWorld-debug.apk
This app just has a button to play a sound, and we can visualise the Media
Callback when they are called.
And the problem is that on the Kindle Fire (Based on Android OS 2.3.3), the
callback mediaSuccess isn't called.
I've tested on these devices:
- Kindle Fire (1st GEN), Android 2.3.3 = KO
- Nexus 7, Android 4.4 = OK
- Samsung Galaxy S1, Android 2.3.3 = OK
- Samsung Galaxy S2, Android 4.0.4 = OK
As i've released my app on Amazon, i'm currently blocked on this platform to
keep releasing update, my last update was based on cordova 2.7, which worked
fine on Kindle.
I've dug into the Media Plugin, and i've find out that in the
AudioPlayer.java , the setState method is working just fine, and send this
message to the javascript part with the correct status ( 4 == MEDIA_STOPPED ):
[jira] [Created] (CB-5955) Media.onStatus method do not catch some message that are correctly send by the Media.js (plugin cordova media), the Media.onStatus method do not catch some message that are
Thibault Durand created CB-5955: --- Summary: Media.onStatus method do not catch some message that are correctly send by the Media.js (plugin cordova media), the Media.onStatus method do not catch some message that are correctly send by the AudioPlayer.java Key: CB-5955 URL: https://issues.apache.org/jira/browse/CB-5955 Project: Apache Cordova Issue Type: Bug Components: CordovaJS Affects Versions: 3.3.0, 3.2.0, 3.1.0, 3.0.0 Environment: Kindle Fire , Android 2.3 Reporter: Thibault Durand -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CB-5955) Media.onStatus method do not catch some message that are correctly send by the Media.js (plugin cordova media), the Media.onStatus method do not catch some message that are
[
https://issues.apache.org/jira/browse/CB-5955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thibault Durand updated CB-5955:
Description:
Hi,
I have a really weird issue with my Kindle Fire (Android 2.3) , i'll try to
explain it the best i can (i don't fully understand the problem and it may be
not a problem on your side). First, i'm not able to do a sample app to
reproduce this bug. (it happens sometimes on my device, but when i do a test
app, i never get it)
I have a piece of code that need to get the MediaSuccess (or Error) callback
after playing an audio file, and sometimes, it's juste isn't called.
I've dug into the Media Plugin, and i've find out that int the AudioPlayer.java
, the setState method is working just fine, and send this message to the
javascript part with the correct status. ( 4 == MEDIA_STOPPED )
cordova.require('org.apache.cordova.media.Media').onStatus('c5f1ec7b-9cdf-0a49-3f62-0def8bd2d9b2',
1, 4);
But, when i put a console.log in the Media.onStatus callback in the Media.js
file, i don't get anything, it seems that the message isn't catched.
So my question is : Do you see how that could be possible ?
Thanks, i can give you more information if needed.
Best regards,
Thibault
Media.onStatus method do not catch some message that are correctly send by
the Media.js (plugin cordova media), the Media.onStatus method do not catch
some message that are correctly send by the AudioPlayer.java
---
Key: CB-5955
URL: https://issues.apache.org/jira/browse/CB-5955
Project: Apache Cordova
Issue Type: Bug
Components: CordovaJS
Affects Versions: 3.0.0, 3.1.0, 3.2.0, 3.3.0
Environment: Kindle Fire , Android 2.3
Reporter: Thibault Durand
Hi,
I have a really weird issue with my Kindle Fire (Android 2.3) , i'll try to
explain it the best i can (i don't fully understand the problem and it may be
not a problem on your side). First, i'm not able to do a sample app to
reproduce this bug. (it happens sometimes on my device, but when i do a test
app, i never get it)
I have a piece of code that need to get the MediaSuccess (or Error) callback
after playing an audio file, and sometimes, it's juste isn't called.
I've dug into the Media Plugin, and i've find out that int the
AudioPlayer.java , the setState method is working just fine, and send this
message to the javascript part with the correct status. ( 4 == MEDIA_STOPPED
)
cordova.require('org.apache.cordova.media.Media').onStatus('c5f1ec7b-9cdf-0a49-3f62-0def8bd2d9b2',
1, 4);
But, when i put a console.log in the Media.onStatus callback in the Media.js
file, i don't get anything, it seems that the message isn't catched.
So my question is : Do you see how that could be possible ?
Thanks, i can give you more information if needed.
Best regards,
Thibault
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (CB-5955) Media.onStatus method do not catch some message that are correctly send by the AudioPlayer.java
[
https://issues.apache.org/jira/browse/CB-5955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thibault Durand updated CB-5955:
Summary: Media.onStatus method do not catch some message that are correctly
send by the AudioPlayer.java (was: Media.onStatus method do not catch some
message that are correctly send by the Media.js (plugin cordova media), the
Media.onStatus method do not catch some message that are correctly send by the
AudioPlayer.java)
Media.onStatus method do not catch some message that are correctly send by
the AudioPlayer.java
---
Key: CB-5955
URL: https://issues.apache.org/jira/browse/CB-5955
Project: Apache Cordova
Issue Type: Bug
Components: CordovaJS
Affects Versions: 3.0.0, 3.1.0, 3.2.0, 3.3.0
Environment: Kindle Fire , Android 2.3
Reporter: Thibault Durand
Hi,
I have a really weird issue with my Kindle Fire (Android 2.3) , i'll try to
explain it the best i can (i don't fully understand the problem and it may be
not a problem on your side). First, i'm not able to do a sample app to
reproduce this bug. (it happens sometimes on my device, but when i do a test
app, i never get it)
I have a piece of code that need to get the MediaSuccess (or Error) callback
after playing an audio file, and sometimes, it's juste isn't called.
I've dug into the Media Plugin, and i've find out that int the
AudioPlayer.java , the setState method is working just fine, and send this
message to the javascript part with the correct status. ( 4 == MEDIA_STOPPED
)
cordova.require('org.apache.cordova.media.Media').onStatus('c5f1ec7b-9cdf-0a49-3f62-0def8bd2d9b2',
1, 4);
But, when i put a console.log in the Media.onStatus callback in the Media.js
file, i don't get anything, it seems that the message isn't catched.
So my question is : Do you see how that could be possible ?
Thanks, i can give you more information if needed.
Best regards,
Thibault
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (CB-5955) Media.onStatus method do not catch some message that are correctly send by the AudioPlayer.java
[
https://issues.apache.org/jira/browse/CB-5955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thibault Durand updated CB-5955:
Description:
Hi,
I have a really weird issue with my Kindle Fire (Android 2.3) , i'll try to
explain it the best i can (i don't fully understand the problem and it may be
not a problem on your side). First, i'm not able to do a sample app to
reproduce this bug. (it happens sometimes on my device, but when i do a test
app, i never get it)
I have a piece of code that need to get the MediaSuccess (or Error) callback
after playing an audio file, and sometimes, it's juste isn't called.
I've dug into the Media Plugin, and i've find out that int the AudioPlayer.java
, the setState method is working just fine, and send this message to the
javascript part with the correct status. ( 4 == MEDIA_STOPPED )
cordova.require('org.apache.cordova.media.Media').onStatus('c5f1ec7b-9cdf-0a49-3f62-0def8bd2d9b2',
1, 4);
But, when i put a console.log in the Media.onStatus callback in the Media.js
file, i don't get anything, it seems that the message isn't caught.
So my question is : Do you see how that could be possible ?
Thanks, i can give you more information if needed.
Best regards,
Thibault
was:
Hi,
I have a really weird issue with my Kindle Fire (Android 2.3) , i'll try to
explain it the best i can (i don't fully understand the problem and it may be
not a problem on your side). First, i'm not able to do a sample app to
reproduce this bug. (it happens sometimes on my device, but when i do a test
app, i never get it)
I have a piece of code that need to get the MediaSuccess (or Error) callback
after playing an audio file, and sometimes, it's juste isn't called.
I've dug into the Media Plugin, and i've find out that int the AudioPlayer.java
, the setState method is working just fine, and send this message to the
javascript part with the correct status. ( 4 == MEDIA_STOPPED )
cordova.require('org.apache.cordova.media.Media').onStatus('c5f1ec7b-9cdf-0a49-3f62-0def8bd2d9b2',
1, 4);
But, when i put a console.log in the Media.onStatus callback in the Media.js
file, i don't get anything, it seems that the message isn't catched.
So my question is : Do you see how that could be possible ?
Thanks, i can give you more information if needed.
Best regards,
Thibault
Media.onStatus method do not catch some message that are correctly send by
the AudioPlayer.java
---
Key: CB-5955
URL: https://issues.apache.org/jira/browse/CB-5955
Project: Apache Cordova
Issue Type: Bug
Components: CordovaJS
Affects Versions: 3.0.0, 3.1.0, 3.2.0, 3.3.0
Environment: Kindle Fire , Android 2.3
Reporter: Thibault Durand
Hi,
I have a really weird issue with my Kindle Fire (Android 2.3) , i'll try to
explain it the best i can (i don't fully understand the problem and it may be
not a problem on your side). First, i'm not able to do a sample app to
reproduce this bug. (it happens sometimes on my device, but when i do a test
app, i never get it)
I have a piece of code that need to get the MediaSuccess (or Error) callback
after playing an audio file, and sometimes, it's juste isn't called.
I've dug into the Media Plugin, and i've find out that int the
AudioPlayer.java , the setState method is working just fine, and send this
message to the javascript part with the correct status. ( 4 == MEDIA_STOPPED
)
cordova.require('org.apache.cordova.media.Media').onStatus('c5f1ec7b-9cdf-0a49-3f62-0def8bd2d9b2',
1, 4);
But, when i put a console.log in the Media.onStatus callback in the Media.js
file, i don't get anything, it seems that the message isn't caught.
So my question is : Do you see how that could be possible ?
Thanks, i can give you more information if needed.
Best regards,
Thibault
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Comment Edited] (CB-2912) Android 4.X SQLite issue ( maybe conflict using websql)
[ https://issues.apache.org/jira/browse/CB-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623945#comment-13623945 ] Thibault Durand edited comment on CB-2912 at 4/5/13 6:56 PM: - Did you have this switch for Android 4.x only since 2.6.0 ? Because i didn't have any issue before. And yes, normally i have the error with websql on creating table which exists, but it's not causing the app to crash. And yes i know i shouldn't use websql anymore, but indexed db is just pain in the ass. Seems websql will be supported on mobile device for a long time. was (Author: tdurand): Do you switch for Android 4.x only since 2.6.0 ? Because i didn't have any issue before. And yes, normally i have the error with websql on creating table which exists, but it's not causing the app to crash. And yes i know i shouldn't use websql anymore, but indexed db is just pain in the ass. Seems websql will be supported on mobile device for a long time. Android 4.X SQLite issue ( maybe conflict using websql) --- Key: CB-2912 URL: https://issues.apache.org/jira/browse/CB-2912 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 2.6.0 Environment: Android 4.0.3 , Android 4.2 Reporter: Thibault Durand Assignee: Joe Bowser Priority: Minor Hello, I have an issue with my app using the last version of cordova with cordova CLI (NPM , version @2.6.0) Cordova version is master : commit 47593b2bc1dba9bf46545b1da24577f937966e12 My app use websql, and it seems there are some conflict with SQLite on Android 4.X , android 2.X works just fine (i don't really know what websql api uses...) Here is the stacktrace, the database seems to be initialized but each request trigger a System error : 04-05 11:58:13.413: W/System.err(5739): android.database.sqlite.SQLiteException: table user_card already exists: , while compiling: CREATE TABLE user_card( id INTEGER NOT NULL PRIMARY KEY AUTOINCREMENT, card_stat_id INTEGER, es TEXT, fr TEXT, it TEXT, de TEXT, esperanto TEXT, en TEXT, txt_es TEXT, txt_fr TEXT, txt_en TEXT, txt_it TEXT, txt_de TEXT, txt_esperanto TEXT, typeCard TEXT, usage TEXT, genre TEXT, image TEXT, licence TEXT, sound TEXT, linked_card TEXT, tags TEXT, category TEXT, level INTEGER ); 04-05 11:58:13.413: W/System.err(5739): at android.database.sqlite.SQLiteCompiledSql.native_compile(Native Method) 04-05 11:58:13.413: W/System.err(5739): at android.database.sqlite.SQLiteCompiledSql.init(SQLiteCompiledSql.java:68) 04-05 11:58:13.413: W/System.err(5739): at android.database.sqlite.SQLiteProgram.compileSql(SQLiteProgram.java:134) 04-05 11:58:13.413: W/System.err(5739): at android.database.sqlite.SQLiteProgram.compileAndbindAllArgs(SQLiteProgram.java:361) 04-05 11:58:13.413: W/System.err(5739): at android.database.sqlite.SQLiteStatement.acquireAndLock(SQLiteStatement.java:260) 04-05 11:58:13.413: W/System.err(5739): at android.database.sqlite.SQLiteStatement.executeUpdateDelete(SQLiteStatement.java:84) 04-05 11:58:13.413: W/System.err(5739): at android.database.sqlite.SQLiteDatabase.executeSql(SQLiteDatabase.java:2034) 04-05 11:58:13.413: W/System.err(5739): at android.database.sqlite.SQLiteDatabase.execSQL(SQLiteDatabase.java:1974) 04-05 11:58:13.413: W/System.err(5739): at org.apache.cordova.Storage.executeSql(Storage.java:169) 04-05 11:58:13.413: W/System.err(5739): at org.apache.cordova.Storage.execute(Storage.java:83) 04-05 11:58:13.413: W/System.err(5739): at org.apache.cordova.api.CordovaPlugin.execute(CordovaPlugin.java:66) 04-05 11:58:13.413: W/System.err(5739): at org.apache.cordova.api.PluginManager.exec(PluginManager.java:222) 04-05 11:58:13.413: W/System.err(5739): at org.apache.cordova.ExposedJsApi.exec(ExposedJsApi.java:44) 04-05 11:58:13.413: W/System.err(5739): at android.webkit.JWebCoreJavaBridge.sharedTimerFired(Native Method) 04-05 11:58:13.413: W/System.err(5739): at android.webkit.JWebCoreJavaBridge.sharedTimerFired(Native Method) 04-05 11:58:13.413: W/System.err(5739): at android.webkit.JWebCoreJavaBridge.fireSharedTimer(JWebCoreJavaBridge.java:92) 04-05 11:58:13.413: W/System.err(5739): at android.webkit.JWebCoreJavaBridge.handleMessage(JWebCoreJavaBridge.java:108) 04-05 11:58:13.413: W/System.err(5739): at android.os.Handler.dispatchMessage(Handler.java:99) 04-05 11:58:13.413: W/System.err(5739): at android.os.Looper.loop(Looper.java:137) 04-05 11:58:13.413: W/System.err(5739): at android.webkit.WebViewCore$WebCoreThread.run(WebViewCore.java:823) 04-05 11:58:13.413: W/System.err(5739): at
[jira] [Comment Edited] (CB-2912) Android 4.X SQLite issue ( maybe conflict using websql)
[ https://issues.apache.org/jira/browse/CB-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623945#comment-13623945 ] Thibault Durand edited comment on CB-2912 at 4/5/13 6:56 PM: - Did you have this switch for Android 4.x only since 2.6.0 ? Because i didn't have any issue before. And yes, normally i have the error with websql on creating table which exists, but it's not causing the app to crash. And yes i know i shouldn't use websql anymore, but indexed db is just pain in the ass. Seems websql will be supported on android/ios device for a long time. was (Author: tdurand): Did you have this switch for Android 4.x only since 2.6.0 ? Because i didn't have any issue before. And yes, normally i have the error with websql on creating table which exists, but it's not causing the app to crash. And yes i know i shouldn't use websql anymore, but indexed db is just pain in the ass. Seems websql will be supported on mobile device for a long time. Android 4.X SQLite issue ( maybe conflict using websql) --- Key: CB-2912 URL: https://issues.apache.org/jira/browse/CB-2912 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 2.6.0 Environment: Android 4.0.3 , Android 4.2 Reporter: Thibault Durand Assignee: Joe Bowser Priority: Minor Hello, I have an issue with my app using the last version of cordova with cordova CLI (NPM , version @2.6.0) Cordova version is master : commit 47593b2bc1dba9bf46545b1da24577f937966e12 My app use websql, and it seems there are some conflict with SQLite on Android 4.X , android 2.X works just fine (i don't really know what websql api uses...) Here is the stacktrace, the database seems to be initialized but each request trigger a System error : 04-05 11:58:13.413: W/System.err(5739): android.database.sqlite.SQLiteException: table user_card already exists: , while compiling: CREATE TABLE user_card( id INTEGER NOT NULL PRIMARY KEY AUTOINCREMENT, card_stat_id INTEGER, es TEXT, fr TEXT, it TEXT, de TEXT, esperanto TEXT, en TEXT, txt_es TEXT, txt_fr TEXT, txt_en TEXT, txt_it TEXT, txt_de TEXT, txt_esperanto TEXT, typeCard TEXT, usage TEXT, genre TEXT, image TEXT, licence TEXT, sound TEXT, linked_card TEXT, tags TEXT, category TEXT, level INTEGER ); 04-05 11:58:13.413: W/System.err(5739): at android.database.sqlite.SQLiteCompiledSql.native_compile(Native Method) 04-05 11:58:13.413: W/System.err(5739): at android.database.sqlite.SQLiteCompiledSql.init(SQLiteCompiledSql.java:68) 04-05 11:58:13.413: W/System.err(5739): at android.database.sqlite.SQLiteProgram.compileSql(SQLiteProgram.java:134) 04-05 11:58:13.413: W/System.err(5739): at android.database.sqlite.SQLiteProgram.compileAndbindAllArgs(SQLiteProgram.java:361) 04-05 11:58:13.413: W/System.err(5739): at android.database.sqlite.SQLiteStatement.acquireAndLock(SQLiteStatement.java:260) 04-05 11:58:13.413: W/System.err(5739): at android.database.sqlite.SQLiteStatement.executeUpdateDelete(SQLiteStatement.java:84) 04-05 11:58:13.413: W/System.err(5739): at android.database.sqlite.SQLiteDatabase.executeSql(SQLiteDatabase.java:2034) 04-05 11:58:13.413: W/System.err(5739): at android.database.sqlite.SQLiteDatabase.execSQL(SQLiteDatabase.java:1974) 04-05 11:58:13.413: W/System.err(5739): at org.apache.cordova.Storage.executeSql(Storage.java:169) 04-05 11:58:13.413: W/System.err(5739): at org.apache.cordova.Storage.execute(Storage.java:83) 04-05 11:58:13.413: W/System.err(5739): at org.apache.cordova.api.CordovaPlugin.execute(CordovaPlugin.java:66) 04-05 11:58:13.413: W/System.err(5739): at org.apache.cordova.api.PluginManager.exec(PluginManager.java:222) 04-05 11:58:13.413: W/System.err(5739): at org.apache.cordova.ExposedJsApi.exec(ExposedJsApi.java:44) 04-05 11:58:13.413: W/System.err(5739): at android.webkit.JWebCoreJavaBridge.sharedTimerFired(Native Method) 04-05 11:58:13.413: W/System.err(5739): at android.webkit.JWebCoreJavaBridge.sharedTimerFired(Native Method) 04-05 11:58:13.413: W/System.err(5739): at android.webkit.JWebCoreJavaBridge.fireSharedTimer(JWebCoreJavaBridge.java:92) 04-05 11:58:13.413: W/System.err(5739): at android.webkit.JWebCoreJavaBridge.handleMessage(JWebCoreJavaBridge.java:108) 04-05 11:58:13.413: W/System.err(5739): at android.os.Handler.dispatchMessage(Handler.java:99) 04-05 11:58:13.413: W/System.err(5739): at android.os.Looper.loop(Looper.java:137) 04-05 11:58:13.413: W/System.err(5739): at android.webkit.WebViewCore$WebCoreThread.run(WebViewCore.java:823) 04-05 11:58:13.413: W/System.err(5739):
[jira] [Comment Edited] (CB-2912) Android 4.X SQLite issue ( maybe conflict using websql)
[ https://issues.apache.org/jira/browse/CB-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623945#comment-13623945 ] Thibault Durand edited comment on CB-2912 at 4/5/13 7:10 PM: - Did you have implemented this switch for Android 4.x only since 2.6.0 ? Because i didn't have any issue before. And yes, normally i have the error with websql on creating table which exists, but it's not causing the app to crash. And yes i know i shouldn't use websql anymore, but indexed db is just pain in the ass. Seems websql will be supported on android/ios device for a long time. was (Author: tdurand): Did you have this switch for Android 4.x only since 2.6.0 ? Because i didn't have any issue before. And yes, normally i have the error with websql on creating table which exists, but it's not causing the app to crash. And yes i know i shouldn't use websql anymore, but indexed db is just pain in the ass. Seems websql will be supported on android/ios device for a long time. Android 4.X SQLite issue ( maybe conflict using websql) --- Key: CB-2912 URL: https://issues.apache.org/jira/browse/CB-2912 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 2.6.0 Environment: Android 4.0.3 , Android 4.2 Reporter: Thibault Durand Assignee: Joe Bowser Priority: Minor Hello, I have an issue with my app using the last version of cordova with cordova CLI (NPM , version @2.6.0) Cordova version is master : commit 47593b2bc1dba9bf46545b1da24577f937966e12 My app use websql, and it seems there are some conflict with SQLite on Android 4.X , android 2.X works just fine (i don't really know what websql api uses...) Here is the stacktrace, the database seems to be initialized but each request trigger a System error : 04-05 11:58:13.413: W/System.err(5739): android.database.sqlite.SQLiteException: table user_card already exists: , while compiling: CREATE TABLE user_card( id INTEGER NOT NULL PRIMARY KEY AUTOINCREMENT, card_stat_id INTEGER, es TEXT, fr TEXT, it TEXT, de TEXT, esperanto TEXT, en TEXT, txt_es TEXT, txt_fr TEXT, txt_en TEXT, txt_it TEXT, txt_de TEXT, txt_esperanto TEXT, typeCard TEXT, usage TEXT, genre TEXT, image TEXT, licence TEXT, sound TEXT, linked_card TEXT, tags TEXT, category TEXT, level INTEGER ); 04-05 11:58:13.413: W/System.err(5739): at android.database.sqlite.SQLiteCompiledSql.native_compile(Native Method) 04-05 11:58:13.413: W/System.err(5739): at android.database.sqlite.SQLiteCompiledSql.init(SQLiteCompiledSql.java:68) 04-05 11:58:13.413: W/System.err(5739): at android.database.sqlite.SQLiteProgram.compileSql(SQLiteProgram.java:134) 04-05 11:58:13.413: W/System.err(5739): at android.database.sqlite.SQLiteProgram.compileAndbindAllArgs(SQLiteProgram.java:361) 04-05 11:58:13.413: W/System.err(5739): at android.database.sqlite.SQLiteStatement.acquireAndLock(SQLiteStatement.java:260) 04-05 11:58:13.413: W/System.err(5739): at android.database.sqlite.SQLiteStatement.executeUpdateDelete(SQLiteStatement.java:84) 04-05 11:58:13.413: W/System.err(5739): at android.database.sqlite.SQLiteDatabase.executeSql(SQLiteDatabase.java:2034) 04-05 11:58:13.413: W/System.err(5739): at android.database.sqlite.SQLiteDatabase.execSQL(SQLiteDatabase.java:1974) 04-05 11:58:13.413: W/System.err(5739): at org.apache.cordova.Storage.executeSql(Storage.java:169) 04-05 11:58:13.413: W/System.err(5739): at org.apache.cordova.Storage.execute(Storage.java:83) 04-05 11:58:13.413: W/System.err(5739): at org.apache.cordova.api.CordovaPlugin.execute(CordovaPlugin.java:66) 04-05 11:58:13.413: W/System.err(5739): at org.apache.cordova.api.PluginManager.exec(PluginManager.java:222) 04-05 11:58:13.413: W/System.err(5739): at org.apache.cordova.ExposedJsApi.exec(ExposedJsApi.java:44) 04-05 11:58:13.413: W/System.err(5739): at android.webkit.JWebCoreJavaBridge.sharedTimerFired(Native Method) 04-05 11:58:13.413: W/System.err(5739): at android.webkit.JWebCoreJavaBridge.sharedTimerFired(Native Method) 04-05 11:58:13.413: W/System.err(5739): at android.webkit.JWebCoreJavaBridge.fireSharedTimer(JWebCoreJavaBridge.java:92) 04-05 11:58:13.413: W/System.err(5739): at android.webkit.JWebCoreJavaBridge.handleMessage(JWebCoreJavaBridge.java:108) 04-05 11:58:13.413: W/System.err(5739): at android.os.Handler.dispatchMessage(Handler.java:99) 04-05 11:58:13.413: W/System.err(5739): at android.os.Looper.loop(Looper.java:137) 04-05 11:58:13.413: W/System.err(5739): at android.webkit.WebViewCore$WebCoreThread.run(WebViewCore.java:823) 04-05 11:58:13.413:
