[jira] [Commented] (CB-10160) Android - ConnectionType always returning Connection.UNKNOWN
[
https://issues.apache.org/jira/browse/CB-10160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15089272#comment-15089272
]
Mestre Muten commented on CB-10160:
---
It's already at github repo, master branch. What is missing is a tag for
version 1.1.1 so it appears at "Releases" tab.
> Android - ConnectionType always returning Connection.UNKNOWN
>
>
> Key: CB-10160
> URL: https://issues.apache.org/jira/browse/CB-10160
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Network Information
>Affects Versions: 1.1.0
> Environment: Apache Cordova project utilizing the Ionic Framework on
> Mac OSX. Building and deploying using Android Studio 1.5.
>Reporter: Binh Robles
>Assignee: Joe Bowser
> Labels: Android
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> In src/android/NetworkManager.java, all the static final String constants are
> written in all lowercase. When checking the type in GetType(), the code
> already makes this adjustment:
> {quote}private String getType(NetworkInfo info) {
> if (info != null) {
> String type =
> info.getTypeName().{color:red}toLowerCase{color}(Locale.US);{quote}
> However, if type == MOBILE or CELLULAR, the subType is not converted to all
> lowercase:
> {quote}
> else if (type.equals(MOBILE) || type.equals(CELLULAR)) {
> type = {color:red}info.getSubtypeName();{color}
> if (type.equals(GSM) ||
> type.equals(GPRS) ||
> {quote}
> For me, running on the Android emulator and pushing to a device, this was
> causing the app to always fail every subType comparison, and always return
> Connection.UNKNOWN, resulting in an app that was always 'offline'.
> After debugging the plugin, it looked like subTypes were coming in as 'GSM'
> and 'UMTS' in all-caps, and being compared to 'gsm' and 'umts', the
> lower-case pre-defined strings. I added a .toLowerCase() to the subType get,
> and everything seems to be working fine for me:
> else if (type.equals(MOBILE) || type.equals(CELLULAR)) {
> {color:green}type =
> info.getSubtypeName().toLowerCase();{color}
> if (type.equals(GSM) ||
> I'm not sure why this was an issue for me, but hasn't been in the past for
> other users. I can submit whatever environment info you might want if you let
> me know. Thanks!
--
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-10232) Media Plugin - IOS: Can't play files using file system URL (file:///var/modile/...)
Mestre Muten created CB-10232:
-
Summary: Media Plugin - IOS: Can't play files using file system
URL (file:///var/modile/...)
Key: CB-10232
URL: https://issues.apache.org/jira/browse/CB-10232
Project: Apache Cordova
Issue Type: Bug
Components: Plugin Media
Affects Versions: 2.0.0
Environment: iOS
Reporter: Mestre Muten
Can't play files using file system URL, same returned by FileEntry.toURL().
Plugin returns error:
{code}Cannot use audio file from resource file:///var/mobile/...{code}
Tested on iOS 7.1.2 and 9.0.2
{code}
Cordova iOS version: 3.9.2
Plugin versions:
cordova-plugin-file 3.0.0 "File"
cordova-plugin-media 1.0.1 "Media"
{code}
Plugin works well with full absolute path and cdvfile path btw.
--
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] [Updated] (CB-10232) Media Plugin - IOS: Can't play files using file system URL (file:///var/modile/...)
[
https://issues.apache.org/jira/browse/CB-10232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mestre Muten updated CB-10232:
--
Affects Version/s: 5.4.1
> Media Plugin - IOS: Can't play files using file system URL
> (file:///var/modile/...)
> ---
>
> Key: CB-10232
> URL: https://issues.apache.org/jira/browse/CB-10232
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Media
> Environment: iOS
>Reporter: Mestre Muten
> Labels: file, media, url
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Can't play files using file system URL, same returned by FileEntry.toURL().
> Plugin returns error:
> {code}Cannot use audio file from resource file:///var/mobile/...{code}
> Tested on iOS 7.1.2 and 9.0.2
> {code}
> Cordova iOS version: 3.9.2
> Plugin versions:
> cordova-plugin-file 3.0.0 "File"
> cordova-plugin-media 1.0.1 "Media"
> {code}
> Plugin works well with full absolute path and cdvfile path btw.
--
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] [Updated] (CB-10232) Media Plugin - IOS: Can't play files using file system URL (file:///var/modile/...)
[
https://issues.apache.org/jira/browse/CB-10232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mestre Muten updated CB-10232:
--
Affects Version/s: (was: 2.0.0)
> Media Plugin - IOS: Can't play files using file system URL
> (file:///var/modile/...)
> ---
>
> Key: CB-10232
> URL: https://issues.apache.org/jira/browse/CB-10232
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Media
> Environment: iOS
>Reporter: Mestre Muten
> Labels: file, media, url
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Can't play files using file system URL, same returned by FileEntry.toURL().
> Plugin returns error:
> {code}Cannot use audio file from resource file:///var/mobile/...{code}
> Tested on iOS 7.1.2 and 9.0.2
> {code}
> Cordova iOS version: 3.9.2
> Plugin versions:
> cordova-plugin-file 3.0.0 "File"
> cordova-plugin-media 1.0.1 "Media"
> {code}
> Plugin works well with full absolute path and cdvfile path btw.
--
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] [Updated] (CB-10232) Media Plugin - IOS: Can't play files using file system URL (file:///var/modile/...)
[
https://issues.apache.org/jira/browse/CB-10232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mestre Muten updated CB-10232:
--
Affects Version/s: (was: 5.4.1)
> Media Plugin - IOS: Can't play files using file system URL
> (file:///var/modile/...)
> ---
>
> Key: CB-10232
> URL: https://issues.apache.org/jira/browse/CB-10232
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Media
> Environment: iOS
>Reporter: Mestre Muten
> Labels: file, media, url
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Can't play files using file system URL, same returned by FileEntry.toURL().
> Plugin returns error:
> {code}Cannot use audio file from resource file:///var/mobile/...{code}
> Tested on iOS 7.1.2 and 9.0.2
> {code}
> Cordova iOS version: 3.9.2
> Plugin versions:
> cordova-plugin-file 3.0.0 "File"
> cordova-plugin-media 1.0.1 "Media"
> {code}
> Plugin works well with full absolute path and cdvfile path btw.
--
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-10160) Android - ConnectionType always returning Connection.UNKNOWN
[
https://issues.apache.org/jira/browse/CB-10160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15061731#comment-15061731
]
Mestre Muten commented on CB-10160:
---
This should be fixed as soon as possible!
File "src/android/NetworkManager.java" Line 247
>From this:
type = info.getSubtypeName();
> Android - ConnectionType always returning Connection.UNKNOWN
>
>
> Key: CB-10160
> URL: https://issues.apache.org/jira/browse/CB-10160
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Network Information
>Affects Versions: 1.1.0
> Environment: Apache Cordova project utilizing the Ionic Framework on
> Mac OSX. Building and deploying using Android Studio 1.5.
>Reporter: Binh Robles
> Labels: Android
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> In src/android/NetworkManager.java, all the static final String constants are
> written in all lowercase. When checking the type in GetType(), the code
> already makes this adjustment:
> {quote}private String getType(NetworkInfo info) {
> if (info != null) {
> String type =
> info.getTypeName().{color:red}toLowerCase{color}(Locale.US);{quote}
> However, if type == MOBILE or CELLULAR, the subType is not converted to all
> lowercase:
> {quote}
> else if (type.equals(MOBILE) || type.equals(CELLULAR)) {
> type = {color:red}info.getSubtypeName();{color}
> if (type.equals(GSM) ||
> type.equals(GPRS) ||
> {quote}
> For me, running on the Android emulator and pushing to a device, this was
> causing the app to always fail every subType comparison, and always return
> Connection.UNKNOWN, resulting in an app that was always 'offline'.
> After debugging the plugin, it looked like subTypes were coming in as 'GSM'
> and 'UMTS' in all-caps, and being compared to 'gsm' and 'umts', the
> lower-case pre-defined strings. I added a .toLowerCase() to the subType get,
> and everything seems to be working fine for me:
> else if (type.equals(MOBILE) || type.equals(CELLULAR)) {
> {color:green}type =
> info.getSubtypeName().toLowerCase();{color}
> if (type.equals(GSM) ||
> I'm not sure why this was an issue for me, but hasn't been in the past for
> other users. I can submit whatever environment info you might want if you let
> me know. Thanks!
--
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-10160) Android - ConnectionType always returning Connection.UNKNOWN
[
https://issues.apache.org/jira/browse/CB-10160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15061731#comment-15061731
]
Mestre Muten edited comment on CB-10160 at 12/17/15 8:51 AM:
-
This should be fixed as soon as possible!
File "src/android/NetworkManager.java" Line 247
>From this:
type = info.getSubtypeName();
To this:
type = info.getSubtypeName().toLowerCase(Locale.US);
was (Author: mestremuten):
This should be fixed as soon as possible!
File "src/android/NetworkManager.java" Line 247
>From this:
type = info.getSubtypeName();
> Android - ConnectionType always returning Connection.UNKNOWN
>
>
> Key: CB-10160
> URL: https://issues.apache.org/jira/browse/CB-10160
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Network Information
>Affects Versions: 1.1.0
> Environment: Apache Cordova project utilizing the Ionic Framework on
> Mac OSX. Building and deploying using Android Studio 1.5.
>Reporter: Binh Robles
> Labels: Android
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> In src/android/NetworkManager.java, all the static final String constants are
> written in all lowercase. When checking the type in GetType(), the code
> already makes this adjustment:
> {quote}private String getType(NetworkInfo info) {
> if (info != null) {
> String type =
> info.getTypeName().{color:red}toLowerCase{color}(Locale.US);{quote}
> However, if type == MOBILE or CELLULAR, the subType is not converted to all
> lowercase:
> {quote}
> else if (type.equals(MOBILE) || type.equals(CELLULAR)) {
> type = {color:red}info.getSubtypeName();{color}
> if (type.equals(GSM) ||
> type.equals(GPRS) ||
> {quote}
> For me, running on the Android emulator and pushing to a device, this was
> causing the app to always fail every subType comparison, and always return
> Connection.UNKNOWN, resulting in an app that was always 'offline'.
> After debugging the plugin, it looked like subTypes were coming in as 'GSM'
> and 'UMTS' in all-caps, and being compared to 'gsm' and 'umts', the
> lower-case pre-defined strings. I added a .toLowerCase() to the subType get,
> and everything seems to be working fine for me:
> else if (type.equals(MOBILE) || type.equals(CELLULAR)) {
> {color:green}type =
> info.getSubtypeName().toLowerCase();{color}
> if (type.equals(GSM) ||
> I'm not sure why this was an issue for me, but hasn't been in the past for
> other users. I can submit whatever environment info you might want if you let
> me know. Thanks!
--
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-10160) Android - ConnectionType always returning Connection.UNKNOWN
[
https://issues.apache.org/jira/browse/CB-10160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15061731#comment-15061731
]
Mestre Muten edited comment on CB-10160 at 12/17/15 8:55 AM:
-
This should be fixed as soon as possible!
File [src/android/NetworkManager.java Line
247|https://github.com/apache/cordova-plugin-network-information/blob/f6d2782780a889cc730c25e7b183dc93158a6f5b/src/android/NetworkManager.java#L247]
>From this:
{code:java}type = info.getSubtypeName();{code}
To this:
{code:java}type = info.getSubtypeName().toLowerCase(Locale.US);{code}
was (Author: mestremuten):
This should be fixed as soon as possible!
File "src/android/NetworkManager.java" Line 247
>From this:
type = info.getSubtypeName();
To this:
type = info.getSubtypeName().toLowerCase(Locale.US);
> Android - ConnectionType always returning Connection.UNKNOWN
>
>
> Key: CB-10160
> URL: https://issues.apache.org/jira/browse/CB-10160
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Network Information
>Affects Versions: 1.1.0
> Environment: Apache Cordova project utilizing the Ionic Framework on
> Mac OSX. Building and deploying using Android Studio 1.5.
>Reporter: Binh Robles
> Labels: Android
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> In src/android/NetworkManager.java, all the static final String constants are
> written in all lowercase. When checking the type in GetType(), the code
> already makes this adjustment:
> {quote}private String getType(NetworkInfo info) {
> if (info != null) {
> String type =
> info.getTypeName().{color:red}toLowerCase{color}(Locale.US);{quote}
> However, if type == MOBILE or CELLULAR, the subType is not converted to all
> lowercase:
> {quote}
> else if (type.equals(MOBILE) || type.equals(CELLULAR)) {
> type = {color:red}info.getSubtypeName();{color}
> if (type.equals(GSM) ||
> type.equals(GPRS) ||
> {quote}
> For me, running on the Android emulator and pushing to a device, this was
> causing the app to always fail every subType comparison, and always return
> Connection.UNKNOWN, resulting in an app that was always 'offline'.
> After debugging the plugin, it looked like subTypes were coming in as 'GSM'
> and 'UMTS' in all-caps, and being compared to 'gsm' and 'umts', the
> lower-case pre-defined strings. I added a .toLowerCase() to the subType get,
> and everything seems to be working fine for me:
> else if (type.equals(MOBILE) || type.equals(CELLULAR)) {
> {color:green}type =
> info.getSubtypeName().toLowerCase();{color}
> if (type.equals(GSM) ||
> I'm not sure why this was an issue for me, but hasn't been in the past for
> other users. I can submit whatever environment info you might want if you let
> me know. Thanks!
--
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-6935) [Android][cordova-plugin-file] window.resolveLocalFileSystemURL can't resolve cordova.file.applicationDirectory URL
[
https://issues.apache.org/jira/browse/CB-6935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14038563#comment-14038563
]
Mestre Muten commented on CB-6935:
--
That was exactly what happened, I was redirecting using toInternalURL() method.
Switched to toURL() and now all it's running prefectly.
Thatk you! My appologies for the waste of time.
[Android][cordova-plugin-file] window.resolveLocalFileSystemURL can't resolve
cordova.file.applicationDirectory URL
---
Key: CB-6935
URL: https://issues.apache.org/jira/browse/CB-6935
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin File
Affects Versions: 1.2.0
Environment: - Samsung I-9100 Intl (Cyanogenmod 10.2, android 4.3.1)
- Samgsung GT-P5110 (Cyanogenmod 11, android 4.4.2)
Reporter: Mestre Muten
Labels: easyfix, patch
Original Estimate: 2h
Remaining Estimate: 2h
As of version 1.2.0 of this plugin, some special directory paths were added
under cordova.file.*Directory.
All of them seem to work, but applicationDirectory on Android platform
doesn't.
This special directory equals file:///android_asset/.
It calls fail callback with error code = 1 (NOT_FOUND_ERR).
For a simple test just call this on deviceready:
window.resolveLocalFileSystemURL(cordova.file.applicationDirectory,
function(dirEntry){console.log('SUCCESS');},function(error){console.log('ERROR:
'+JSON.stringify(error));});
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Comment Edited] (CB-6935) [Android][cordova-plugin-file] window.resolveLocalFileSystemURL can't resolve cordova.file.applicationDirectory URL
[
https://issues.apache.org/jira/browse/CB-6935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14038563#comment-14038563
]
Mestre Muten edited comment on CB-6935 at 6/20/14 7:39 AM:
---
That was exactly what happened, I was redirecting using toInternalURL() method.
Switched to toURL() and now all it's running prefectly.
Thank you! My appologies for the waste of time.
was (Author: mestremuten):
That was exactly what happened, I was redirecting using toInternalURL() method.
Switched to toURL() and now all it's running prefectly.
Thatk you! My appologies for the waste of time.
[Android][cordova-plugin-file] window.resolveLocalFileSystemURL can't resolve
cordova.file.applicationDirectory URL
---
Key: CB-6935
URL: https://issues.apache.org/jira/browse/CB-6935
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin File
Affects Versions: 1.2.0
Environment: - Samsung I-9100 Intl (Cyanogenmod 10.2, android 4.3.1)
- Samgsung GT-P5110 (Cyanogenmod 11, android 4.4.2)
Reporter: Mestre Muten
Labels: easyfix, patch
Original Estimate: 2h
Remaining Estimate: 2h
As of version 1.2.0 of this plugin, some special directory paths were added
under cordova.file.*Directory.
All of them seem to work, but applicationDirectory on Android platform
doesn't.
This special directory equals file:///android_asset/.
It calls fail callback with error code = 1 (NOT_FOUND_ERR).
For a simple test just call this on deviceready:
window.resolveLocalFileSystemURL(cordova.file.applicationDirectory,
function(dirEntry){console.log('SUCCESS');},function(error){console.log('ERROR:
'+JSON.stringify(error));});
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6935) [Android][cordova-plugin-file] window.resolveLocalFileSystemURL can't resolve cordova.file.applicationDirectory URL
[
https://issues.apache.org/jira/browse/CB-6935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14037432#comment-14037432
]
Mestre Muten commented on CB-6935:
--
Hi again,
I'm sorry if it's not the correct place, but I think it's related to the main
post.
You know I said I use a kind of loader, ok that loader does this steps:
1- Connect to server and get last version available
2- Download all needed files to file system (dataDirectory) using file-transfer
3- Redirect to downloaded index.html
4- Load some stock APK resources
When I try to access some resources from assets directory, I find two issues
that worked before, but not now:
1- can't acces localStorage data I saved in the loader from the new index.html
2- can't load cordova.js (and plugins) from file:///android_assets/www, I get
this error: 06-19 17:08:33.089: I/chromium(7912): [INFO:CONSOLE(0)] Not
allowed to load local resource:
file:///android_asset/www/cordova.js?_=1403190512614, source:
cdvfile://localhost/files/www/index.html (0)
That's really bad for me cause I can't load cordova, and thus, I can't access
any cordova features. The other approach is to download cordova along with
html/css/js, I'll try it now.
I'm on cordova 3.5, and I think this worked fine on cordova 3.3
PD: It would be really great to get read-only access to assets directory on
android.
[Android][cordova-plugin-file] window.resolveLocalFileSystemURL can't resolve
cordova.file.applicationDirectory URL
---
Key: CB-6935
URL: https://issues.apache.org/jira/browse/CB-6935
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin File
Affects Versions: 1.2.0
Environment: - Samsung I-9100 Intl (Cyanogenmod 10.2, android 4.3.1)
- Samgsung GT-P5110 (Cyanogenmod 11, android 4.4.2)
Reporter: Mestre Muten
Labels: easyfix, patch
Original Estimate: 2h
Remaining Estimate: 2h
As of version 1.2.0 of this plugin, some special directory paths were added
under cordova.file.*Directory.
All of them seem to work, but applicationDirectory on Android platform
doesn't.
This special directory equals file:///android_asset/.
It calls fail callback with error code = 1 (NOT_FOUND_ERR).
For a simple test just call this on deviceready:
window.resolveLocalFileSystemURL(cordova.file.applicationDirectory,
function(dirEntry){console.log('SUCCESS');},function(error){console.log('ERROR:
'+JSON.stringify(error));});
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (CB-6935) [Android][cordova-plugin-file] window.resolveLocalFileSystemURL can't resolve cordova.file.applicationDirectory URL
[
https://issues.apache.org/jira/browse/CB-6935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mestre Muten updated CB-6935:
-
Affects Version/s: (was: 3.5.0)
1.2.0
[Android][cordova-plugin-file] window.resolveLocalFileSystemURL can't resolve
cordova.file.applicationDirectory URL
---
Key: CB-6935
URL: https://issues.apache.org/jira/browse/CB-6935
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin File
Affects Versions: 1.2.0
Environment: - Samsung I-9100 Intl (Cyanogenmod 10.2, android 4.3.1)
- Samgsung GT-P5110 (Cyanogenmod 11, android 4.4.2)
Reporter: Mestre Muten
Labels: easyfix, patch
Original Estimate: 2h
Remaining Estimate: 2h
As of version 1.2.0 of this plugin, some special directory paths were added
under cordova.file.*Directory.
All of them seem to work, but applicationDirectory on Android platform
doesn't.
This special directory equals file:///android_asset/.
It calls fail callback with error code = 1 (NOT_FOUND_ERR).
For a simple test just call this on deviceready event callback:
window.resolveLocalFileSystemURL(cordova.file.applicationDirectory,
function(dirEntry){
console.log('SUCCESS');
}, function(error){
console.log('ERROR: '+JSON.stringify(error));
});
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (CB-6935) [Android][cordova-plugin-file] window.resolveLocalFileSystemURL can't resolve cordova.file.applicationDirectory URL
[
https://issues.apache.org/jira/browse/CB-6935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mestre Muten updated CB-6935:
-
Fix Version/s: (was: 3.5.0)
[Android][cordova-plugin-file] window.resolveLocalFileSystemURL can't resolve
cordova.file.applicationDirectory URL
---
Key: CB-6935
URL: https://issues.apache.org/jira/browse/CB-6935
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin File
Affects Versions: 1.2.0
Environment: - Samsung I-9100 Intl (Cyanogenmod 10.2, android 4.3.1)
- Samgsung GT-P5110 (Cyanogenmod 11, android 4.4.2)
Reporter: Mestre Muten
Labels: easyfix, patch
Original Estimate: 2h
Remaining Estimate: 2h
As of version 1.2.0 of this plugin, some special directory paths were added
under cordova.file.*Directory.
All of them seem to work, but applicationDirectory on Android platform
doesn't.
This special directory equals file:///android_asset/.
It calls fail callback with error code = 1 (NOT_FOUND_ERR).
For a simple test just call this on deviceready event callback:
window.resolveLocalFileSystemURL(cordova.file.applicationDirectory,
function(dirEntry){
console.log('SUCCESS');
}, function(error){
console.log('ERROR: '+JSON.stringify(error));
});
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (CB-6935) [Android][cordova-plugin-file] window.resolveLocalFileSystemURL can't resolve cordova.file.applicationDirectory URL
Mestre Muten created CB-6935:
Summary: [Android][cordova-plugin-file]
window.resolveLocalFileSystemURL can't resolve
cordova.file.applicationDirectory URL
Key: CB-6935
URL: https://issues.apache.org/jira/browse/CB-6935
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin File
Affects Versions: 3.5.0
Environment: - Samsung I-9100 Intl (Cyanogenmod 10.2, android 4.3.1)
- Samgsung GT-P5110 (Cyanogenmod 11, android 4.4.2)
Reporter: Mestre Muten
Fix For: 3.5.0
As of version 1.2.0 of this plugin, some special directory paths were added
under cordova.file.*Directory.
All of them seem to work, but applicationDirectory on Android platform
doesn't.
This special directory equals file:///android_asset/.
It calls fail callback with error code = 1 (NOT_FOUND_ERR).
For a simple test just call this on deviceready event callback:
window.resolveLocalFileSystemURL(cordova.file.applicationDirectory,
function(dirEntry){
console.log('SUCCESS');
}, function(error){
console.log('ERROR: '+JSON.stringify(error));
});
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (CB-6935) [Android][cordova-plugin-file] window.resolveLocalFileSystemURL can't resolve cordova.file.applicationDirectory URL
[
https://issues.apache.org/jira/browse/CB-6935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mestre Muten updated CB-6935:
-
Description:
As of version 1.2.0 of this plugin, some special directory paths were added
under cordova.file.*Directory.
All of them seem to work, but applicationDirectory on Android platform
doesn't.
This special directory equals file:///android_asset/.
It calls fail callback with error code = 1 (NOT_FOUND_ERR).
For a simple test just call this on deviceready:
window.resolveLocalFileSystemURL(cordova.file.applicationDirectory,
function(dirEntry){
console.log('SUCCESS');
}, function(error){
console.log('ERROR: '+JSON.stringify(error));
});
was:
As of version 1.2.0 of this plugin, some special directory paths were added
under cordova.file.*Directory.
All of them seem to work, but applicationDirectory on Android platform
doesn't.
This special directory equals file:///android_asset/.
It calls fail callback with error code = 1 (NOT_FOUND_ERR).
For a simple test just call this on deviceready event callback:
window.resolveLocalFileSystemURL(cordova.file.applicationDirectory,
function(dirEntry){
console.log('SUCCESS');
}, function(error){
console.log('ERROR: '+JSON.stringify(error));
});
[Android][cordova-plugin-file] window.resolveLocalFileSystemURL can't resolve
cordova.file.applicationDirectory URL
---
Key: CB-6935
URL: https://issues.apache.org/jira/browse/CB-6935
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin File
Affects Versions: 1.2.0
Environment: - Samsung I-9100 Intl (Cyanogenmod 10.2, android 4.3.1)
- Samgsung GT-P5110 (Cyanogenmod 11, android 4.4.2)
Reporter: Mestre Muten
Labels: easyfix, patch
Original Estimate: 2h
Remaining Estimate: 2h
As of version 1.2.0 of this plugin, some special directory paths were added
under cordova.file.*Directory.
All of them seem to work, but applicationDirectory on Android platform
doesn't.
This special directory equals file:///android_asset/.
It calls fail callback with error code = 1 (NOT_FOUND_ERR).
For a simple test just call this on deviceready:
window.resolveLocalFileSystemURL(cordova.file.applicationDirectory,
function(dirEntry){
console.log('SUCCESS');
}, function(error){
console.log('ERROR: '+JSON.stringify(error));
});
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (CB-6935) [Android][cordova-plugin-file] window.resolveLocalFileSystemURL can't resolve cordova.file.applicationDirectory URL
[
https://issues.apache.org/jira/browse/CB-6935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mestre Muten updated CB-6935:
-
Description:
As of version 1.2.0 of this plugin, some special directory paths were added
under cordova.file.*Directory.
All of them seem to work, but applicationDirectory on Android platform
doesn't.
This special directory equals file:///android_asset/.
It calls fail callback with error code = 1 (NOT_FOUND_ERR).
For a simple test just call this on deviceready:
window.resolveLocalFileSystemURL(
cordova.file.applicationDirectory,
function(dirEntry){
console.log('SUCCESS');
},
function(error){
console.log('ERROR: '+JSON.stringify(error));
}
);
was:
As of version 1.2.0 of this plugin, some special directory paths were added
under cordova.file.*Directory.
All of them seem to work, but applicationDirectory on Android platform
doesn't.
This special directory equals file:///android_asset/.
It calls fail callback with error code = 1 (NOT_FOUND_ERR).
For a simple test just call this on deviceready:
window.resolveLocalFileSystemURL(cordova.file.applicationDirectory,
function(dirEntry){
console.log('SUCCESS');
}, function(error){
console.log('ERROR: '+JSON.stringify(error));
});
[Android][cordova-plugin-file] window.resolveLocalFileSystemURL can't resolve
cordova.file.applicationDirectory URL
---
Key: CB-6935
URL: https://issues.apache.org/jira/browse/CB-6935
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin File
Affects Versions: 1.2.0
Environment: - Samsung I-9100 Intl (Cyanogenmod 10.2, android 4.3.1)
- Samgsung GT-P5110 (Cyanogenmod 11, android 4.4.2)
Reporter: Mestre Muten
Labels: easyfix, patch
Original Estimate: 2h
Remaining Estimate: 2h
As of version 1.2.0 of this plugin, some special directory paths were added
under cordova.file.*Directory.
All of them seem to work, but applicationDirectory on Android platform
doesn't.
This special directory equals file:///android_asset/.
It calls fail callback with error code = 1 (NOT_FOUND_ERR).
For a simple test just call this on deviceready:
window.resolveLocalFileSystemURL(
cordova.file.applicationDirectory,
function(dirEntry){
console.log('SUCCESS');
},
function(error){
console.log('ERROR: '+JSON.stringify(error));
}
);
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (CB-6935) [Android][cordova-plugin-file] window.resolveLocalFileSystemURL can't resolve cordova.file.applicationDirectory URL
[
https://issues.apache.org/jira/browse/CB-6935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mestre Muten updated CB-6935:
-
Description:
As of version 1.2.0 of this plugin, some special directory paths were added
under cordova.file.*Directory.
All of them seem to work, but applicationDirectory on Android platform
doesn't.
This special directory equals file:///android_asset/.
It calls fail callback with error code = 1 (NOT_FOUND_ERR).
For a simple test just call this on deviceready:
window.resolveLocalFileSystemURL(cordova.file.applicationDirectory,
function(dirEntry){console.log('SUCCESS');},function(error){console.log('ERROR:
'+JSON.stringify(error));});
was:
As of version 1.2.0 of this plugin, some special directory paths were added
under cordova.file.*Directory.
All of them seem to work, but applicationDirectory on Android platform
doesn't.
This special directory equals file:///android_asset/.
It calls fail callback with error code = 1 (NOT_FOUND_ERR).
For a simple test just call this on deviceready:
window.resolveLocalFileSystemURL(
cordova.file.applicationDirectory,
function(dirEntry){
console.log('SUCCESS');
},
function(error){
console.log('ERROR: '+JSON.stringify(error));
}
);
[Android][cordova-plugin-file] window.resolveLocalFileSystemURL can't resolve
cordova.file.applicationDirectory URL
---
Key: CB-6935
URL: https://issues.apache.org/jira/browse/CB-6935
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin File
Affects Versions: 1.2.0
Environment: - Samsung I-9100 Intl (Cyanogenmod 10.2, android 4.3.1)
- Samgsung GT-P5110 (Cyanogenmod 11, android 4.4.2)
Reporter: Mestre Muten
Labels: easyfix, patch
Original Estimate: 2h
Remaining Estimate: 2h
As of version 1.2.0 of this plugin, some special directory paths were added
under cordova.file.*Directory.
All of them seem to work, but applicationDirectory on Android platform
doesn't.
This special directory equals file:///android_asset/.
It calls fail callback with error code = 1 (NOT_FOUND_ERR).
For a simple test just call this on deviceready:
window.resolveLocalFileSystemURL(cordova.file.applicationDirectory,
function(dirEntry){console.log('SUCCESS');},function(error){console.log('ERROR:
'+JSON.stringify(error));});
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (CB-6935) [Android][cordova-plugin-file] window.resolveLocalFileSystemURL can't resolve cordova.file.applicationDirectory URL
[
https://issues.apache.org/jira/browse/CB-6935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mestre Muten updated CB-6935:
-
Description:
As of version 1.2.0 of this plugin, some special directory paths were added
under cordova.file.*Directory.
All of them seem to work, but applicationDirectory on Android platform
doesn't.
This special directory equals file:///android_asset/.
It calls fail callback with error code = 1 (NOT_FOUND_ERR).
For a simple test just call this on deviceready:
window.resolveLocalFileSystemURL(
cordova.file.applicationDirectory,
function(dirEntry){
console.log('SUCCESS');
},
function(error){
console.log('ERROR: '+JSON.stringify(error));
}
);
was:
As of version 1.2.0 of this plugin, some special directory paths were added
under cordova.file.*Directory.
All of them seem to work, but applicationDirectory on Android platform
doesn't.
This special directory equals file:///android_asset/.
It calls fail callback with error code = 1 (NOT_FOUND_ERR).
For a simple test just call this on deviceready:
window.resolveLocalFileSystemURL(
cordova.file.applicationDirectory,
function(dirEntry){
console.log('SUCCESS');
},
function(error){
console.log('ERROR: '+JSON.stringify(error));
}
);
[Android][cordova-plugin-file] window.resolveLocalFileSystemURL can't resolve
cordova.file.applicationDirectory URL
---
Key: CB-6935
URL: https://issues.apache.org/jira/browse/CB-6935
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin File
Affects Versions: 1.2.0
Environment: - Samsung I-9100 Intl (Cyanogenmod 10.2, android 4.3.1)
- Samgsung GT-P5110 (Cyanogenmod 11, android 4.4.2)
Reporter: Mestre Muten
Labels: easyfix, patch
Original Estimate: 2h
Remaining Estimate: 2h
As of version 1.2.0 of this plugin, some special directory paths were added
under cordova.file.*Directory.
All of them seem to work, but applicationDirectory on Android platform
doesn't.
This special directory equals file:///android_asset/.
It calls fail callback with error code = 1 (NOT_FOUND_ERR).
For a simple test just call this on deviceready:
window.resolveLocalFileSystemURL(
cordova.file.applicationDirectory,
function(dirEntry){
console.log('SUCCESS');
},
function(error){
console.log('ERROR: '+JSON.stringify(error));
}
);
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6935) [Android][cordova-plugin-file] window.resolveLocalFileSystemURL can't resolve cordova.file.applicationDirectory URL
[
https://issues.apache.org/jira/browse/CB-6935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14030795#comment-14030795
]
Mestre Muten commented on CB-6935:
--
Sorry for duplicate issue, I thought it was supported as
https://issues.apache.org/jira/browse/CB-285 is marked as resolved.
This is not a major problem for me. I would use it cause I often just include a
simple loader in my APKs, which just downloads Apps newest source files and
then redirects to last index.html, but then I have to include the original
cordova.js, which is in assets/www directory (downloading every time cordova JS
libraries is not an option for me).
For now I can manage to get assets directory path saving location.href in
localStorage (when loader starts up), but of course retrieving it from
FileSystem directly would be a better way.
Are you planning to include it in near future versions of the plugin?
Regards.
[Android][cordova-plugin-file] window.resolveLocalFileSystemURL can't resolve
cordova.file.applicationDirectory URL
---
Key: CB-6935
URL: https://issues.apache.org/jira/browse/CB-6935
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin File
Affects Versions: 1.2.0
Environment: - Samsung I-9100 Intl (Cyanogenmod 10.2, android 4.3.1)
- Samgsung GT-P5110 (Cyanogenmod 11, android 4.4.2)
Reporter: Mestre Muten
Labels: easyfix, patch
Original Estimate: 2h
Remaining Estimate: 2h
As of version 1.2.0 of this plugin, some special directory paths were added
under cordova.file.*Directory.
All of them seem to work, but applicationDirectory on Android platform
doesn't.
This special directory equals file:///android_asset/.
It calls fail callback with error code = 1 (NOT_FOUND_ERR).
For a simple test just call this on deviceready:
window.resolveLocalFileSystemURL(cordova.file.applicationDirectory,
function(dirEntry){console.log('SUCCESS');},function(error){console.log('ERROR:
'+JSON.stringify(error));});
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6935) [Android][cordova-plugin-file] window.resolveLocalFileSystemURL can't resolve cordova.file.applicationDirectory URL
[
https://issues.apache.org/jira/browse/CB-6935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14030918#comment-14030918
]
Mestre Muten commented on CB-6935:
--
Indeed it's very good concept, especially when you have to do small/medium
changes to an App that do not require new APK/IPA (new cordova version, new
features, ...).
But I think my work it's too much specific for our needs (I've done it at my
job), and, you know, companies... always wanting the work done for yesterday,
and that means the quality of code is far from acceptable.
Anyway, if I ever do it well, in a general point of view, I'll submit it as
plugin, sure.
[Android][cordova-plugin-file] window.resolveLocalFileSystemURL can't resolve
cordova.file.applicationDirectory URL
---
Key: CB-6935
URL: https://issues.apache.org/jira/browse/CB-6935
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin File
Affects Versions: 1.2.0
Environment: - Samsung I-9100 Intl (Cyanogenmod 10.2, android 4.3.1)
- Samgsung GT-P5110 (Cyanogenmod 11, android 4.4.2)
Reporter: Mestre Muten
Labels: easyfix, patch
Original Estimate: 2h
Remaining Estimate: 2h
As of version 1.2.0 of this plugin, some special directory paths were added
under cordova.file.*Directory.
All of them seem to work, but applicationDirectory on Android platform
doesn't.
This special directory equals file:///android_asset/.
It calls fail callback with error code = 1 (NOT_FOUND_ERR).
For a simple test just call this on deviceready:
window.resolveLocalFileSystemURL(cordova.file.applicationDirectory,
function(dirEntry){console.log('SUCCESS');},function(error){console.log('ERROR:
'+JSON.stringify(error));});
--
This message was sent by Atlassian JIRA
(v6.2#6252)
