[jira] [Commented] (CB-7999) Investigate serving assets from simple http server for cordova-browser
[ https://issues.apache.org/jira/browse/CB-7999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14212029#comment-14212029 ] Andrew Grieve commented on CB-7999: --- Use `cordova serve`? Investigate serving assets from simple http server for cordova-browser -- Key: CB-7999 URL: https://issues.apache.org/jira/browse/CB-7999 Project: Apache Cordova Issue Type: Bug Components: Browser Reporter: Michal Mocny Currently we load page from file:// using chrome explicitly, and get around some of the issue that entails by passing chrome special runtime flags. An alternative that has long been used by web devs is to just host a local server ala python -m SimpleHTTPServer (node equivalent: https://github.com/nodeapps/http-server). Primary goals: - Do not hardcode path to browser executable, let host open html page in whatever is set to default - Support browsers that are not Chrome - [stretch] Support livereload -- 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-7917) Tests file.spec.114 - 116 fails for windows platform
[ https://issues.apache.org/jira/browse/CB-7917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14212042#comment-14212042 ] ASF GitHub Bot commented on CB-7917: Github user MariaBukharina commented on the pull request: https://github.com/apache/cordova-plugin-file/pull/88#issuecomment-63028689 Thank you very much! Tests file.spec.114 - 116 fails for windows platform Key: CB-7917 URL: https://issues.apache.org/jira/browse/CB-7917 Project: Apache Cordova Issue Type: Test Components: mobile-spec, Plugin File, Windows Reporter: Maria Bukharina Repo steps: 1. create mobile-spec app 2. run Plugin auto test for plugin file Tests file.spec.114 - 116 fails -- 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-8015) improve readability of console output (LogCat)
Aaron Ruß created CB-8015:
-
Summary: improve readability of console output (LogCat)
Key: CB-8015
URL: https://issues.apache.org/jira/browse/CB-8015
Project: Apache Cordova
Issue Type: Improvement
Components: Android
Reporter: Aaron Ruß
Priority: Minor
Messages that are logged to the console via
{{CordovaChromeClient.onConsoleMessage(ConsoleMessage)}} always get written to
the JavaScript console with DEBUG level.
Since LogCat is capable of formatting messages according to their log-level, it
would improve readability of the LogCat output considerably, if
{{CordovaChromeClient.onConsoleMessage(ConsoleMessage)}} would print the
message with the actual log-level of the message, i.e.
{{ConsoleMessage.messageLevel()}}.
--
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-8015) improve readability of console output (LogCat)
[
https://issues.apache.org/jira/browse/CB-8015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Ruß updated CB-8015:
--
Description:
Messages that are logged to the console via
{{CordovaChromeClient.onConsoleMessage(ConsoleMessage)}} always get written to
the JavaScript console with DEBUG level.
Since LogCat is capable of formatting messages according to their log-level, it
would improve readability of the LogCat output considerably, if
{{CordovaChromeClient.onConsoleMessage(ConsoleMessage)}} would print the
message with the actual log-level of the message, i.e.
{{ConsoleMessage.messageLevel()}}.
see
https://github.com/mmig/cordova-android/commit/506ab013ba3c72e979176ff00a894ed38052009a
was:
Messages that are logged to the console via
{{CordovaChromeClient.onConsoleMessage(ConsoleMessage)}} always get written to
the JavaScript console with DEBUG level.
Since LogCat is capable of formatting messages according to their log-level, it
would improve readability of the LogCat output considerably, if
{{CordovaChromeClient.onConsoleMessage(ConsoleMessage)}} would print the
message with the actual log-level of the message, i.e.
{{ConsoleMessage.messageLevel()}}.
improve readability of console output (LogCat)
--
Key: CB-8015
URL: https://issues.apache.org/jira/browse/CB-8015
Project: Apache Cordova
Issue Type: Improvement
Components: Android
Reporter: Aaron Ruß
Priority: Minor
Original Estimate: 10m
Remaining Estimate: 10m
Messages that are logged to the console via
{{CordovaChromeClient.onConsoleMessage(ConsoleMessage)}} always get written
to the JavaScript console with DEBUG level.
Since LogCat is capable of formatting messages according to their log-level,
it would improve readability of the LogCat output considerably, if
{{CordovaChromeClient.onConsoleMessage(ConsoleMessage)}} would print the
message with the actual log-level of the message, i.e.
{{ConsoleMessage.messageLevel()}}.
see
https://github.com/mmig/cordova-android/commit/506ab013ba3c72e979176ff00a894ed38052009a
--
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-8016) Including UserInfo Details in Error Callback (iOS)
Balaji Rajendran created CB-8016: Summary: Including UserInfo Details in Error Callback (iOS) Key: CB-8016 URL: https://issues.apache.org/jira/browse/CB-8016 Project: Apache Cordova Issue Type: Wish Components: iOS, Plugin InAppBrowser Reporter: Balaji Rajendran Priority: Minor If the UIWebview failed to load a request, it provides additional information about the failure in the form of userInfo in the error object. Currently, the InAppBrowser plugin is not passing that userInfo details back to the callback function. It would be helpful, if it pass this userInfo along with other existing basic details. An example where we need userInfo object , Lets say We are loading a main HTML page which has many sub HTML page requests within the same and if anyone of the request gets failed, those failed sub-request URL request details will be available in userInfo object. -- 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-8016) [InAppBrowser] Including UserInfo Details in Error Callback (iOS)
[ https://issues.apache.org/jira/browse/CB-8016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balaji Rajendran updated CB-8016: - Summary: [InAppBrowser] Including UserInfo Details in Error Callback (iOS) (was: Including UserInfo Details in Error Callback (iOS)) [InAppBrowser] Including UserInfo Details in Error Callback (iOS) - Key: CB-8016 URL: https://issues.apache.org/jira/browse/CB-8016 Project: Apache Cordova Issue Type: Wish Components: iOS, Plugin InAppBrowser Reporter: Balaji Rajendran Priority: Minor Labels: inappbrowser, ios, webview If the UIWebview failed to load a request, it provides additional information about the failure in the form of userInfo in the error object. Currently, the InAppBrowser plugin is not passing that userInfo details back to the callback function. It would be helpful, if it pass this userInfo along with other existing basic details. An example where we need userInfo object , Lets say We are loading a main HTML page which has many sub HTML page requests within the same and if anyone of the request gets failed, those failed sub-request URL request details will be available in userInfo object. -- 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-7944) Some auto tests for plugin file-transfer are fails for windows
[ https://issues.apache.org/jira/browse/CB-7944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14212235#comment-14212235 ] ASF GitHub Bot commented on CB-7944: Github user MariaBukharina commented on the pull request: https://github.com/apache/cordova-plugin-file-transfer/pull/48#issuecomment-63062423 Thaks for you comments! I've fixed small formatting issues. Please review, if everything ok now? Some auto tests for plugin file-transfer are fails for windows -- Key: CB-7944 URL: https://issues.apache.org/jira/browse/CB-7944 Project: Apache Cordova Issue Type: Test Components: Plugin File Transfer, Windows Reporter: Maria Bukharina Repo steps: 1. create mobile-spec app 2. run Plugin auto test for file-transfer plugin Expected: if method doesn't siupport pending test Actual: filetransfer.spec.7 should be able to download a file using file:// (when hosted from file:// filetransfer.spec.18 should be able to upload a file filetransfer.spec.19 should be able to upload a file with http basic auth fails because no file:// access on windwos and onprogress method doesn't supported on WP -- 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-8017) Add proper support for input type=file for Android L
Andrew Grieve created CB-8017: - Summary: Add proper support for input type=file for Android L Key: CB-8017 URL: https://issues.apache.org/jira/browse/CB-8017 Project: Apache Cordova Issue Type: Bug Components: Android Reporter: Andrew Grieve Priority: Minor Android L includes a supported callback for showing the file chooser: http://developer.android.com/reference/android/webkit/WebChromeClient.html#onShowFileChooser(android.webkit.WebView, android.webkit.ValueCallbackandroid.net.Uri[], android.webkit.WebChromeClient.FileChooserParams) There's a good example implementation here: https://github.com/GoogleChrome/chromium-webview-samples/blob/master/input-file-example/app/src/main/java/inputfilesample/android/chrome/google/com/inputfilesample/MainFragment.java -- 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] [Resolved] (CB-5294) File input element not opening file picker in Android 4.4
[ https://issues.apache.org/jira/browse/CB-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Grieve resolved CB-5294. --- Resolution: Won't Fix Seems this is infeasible to fix :(. Closing. File input element not opening file picker in Android 4.4 - Key: CB-5294 URL: https://issues.apache.org/jira/browse/CB-5294 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 3.1.0 Environment: Android 4.4.2, partially fixed in Android 4.4.3 Reporter: Paul Kane The file input field doesn't respond when clicked/tapped in Android 4.4. Works fine in previous Android versions. This is regardless of whether the Target Level is set to 18 or 19. To reproduce, I created a fresh Cordova 3.1.0 project for Android. The only modification I made to the default (placeholder) index.html file was adding a form element with a single input type=file element inside. Clicking the Choose File button does nothing. No Logcat output or errors. Normally at this point a dialogue would open allowing me to select an image from the gallery or take a picture, which is what happens in older Android versions. -- 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] [Reopened] (CB-5294) File input element not opening file picker in Android 4.4
[ https://issues.apache.org/jira/browse/CB-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser reopened CB-5294: File input element not opening file picker in Android 4.4 - Key: CB-5294 URL: https://issues.apache.org/jira/browse/CB-5294 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 3.1.0 Environment: Android 4.4.2, partially fixed in Android 4.4.3 Reporter: Paul Kane The file input field doesn't respond when clicked/tapped in Android 4.4. Works fine in previous Android versions. This is regardless of whether the Target Level is set to 18 or 19. To reproduce, I created a fresh Cordova 3.1.0 project for Android. The only modification I made to the default (placeholder) index.html file was adding a form element with a single input type=file element inside. Clicking the Choose File button does nothing. No Logcat output or errors. Normally at this point a dialogue would open allowing me to select an image from the gallery or take a picture, which is what happens in older Android versions. -- 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] [Closed] (CB-5294) File input element not opening file picker in Android 4.4
[ https://issues.apache.org/jira/browse/CB-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser closed CB-5294. -- Resolution: Incomplete I think Incomplete is better as Won't Fix. We can always take another stab at this later, but this is too hard with not enough reward for anyone to want to take on at the moment. File input element not opening file picker in Android 4.4 - Key: CB-5294 URL: https://issues.apache.org/jira/browse/CB-5294 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 3.1.0 Environment: Android 4.4.2, partially fixed in Android 4.4.3 Reporter: Paul Kane The file input field doesn't respond when clicked/tapped in Android 4.4. Works fine in previous Android versions. This is regardless of whether the Target Level is set to 18 or 19. To reproduce, I created a fresh Cordova 3.1.0 project for Android. The only modification I made to the default (placeholder) index.html file was adding a form element with a single input type=file element inside. Clicking the Choose File button does nothing. No Logcat output or errors. Normally at this point a dialogue would open allowing me to select an image from the gallery or take a picture, which is what happens in older Android versions. -- 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-8018) Add vibrate(pattern) fallback on vibrate for Windows Phone 8
Sergey Shakhnazarov created CB-8018: --- Summary: Add vibrate(pattern) fallback on vibrate for Windows Phone 8 Key: CB-8018 URL: https://issues.apache.org/jira/browse/CB-8018 Project: Apache Cordova Issue Type: Improvement Components: Plugin Vibration Environment: Windows Phone 8 Reporter: Sergey Shakhnazarov -- 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-8019) Cordova CLI help for create/copy-from doesn't mention the option to copy a project
Raymond Camden created CB-8019: -- Summary: Cordova CLI help for create/copy-from doesn't mention the option to copy a project Key: CB-8019 URL: https://issues.apache.org/jira/browse/CB-8019 Project: Apache Cordova Issue Type: Bug Reporter: Raymond Camden Priority: Minor When you run cordova help create, it has this to say about copy-from: --copy-from|src=PATH ... use custom www assets instead of the stock Cordova hello-world. What this doesn't tell you is that if you point the path at a project, it will copy www, hooks, and config.xml. I had no idea this feature even existed until PhoneGap's CLI implemented it. I see two issues here - the help text should mention it - and the *result* is also incorrect when you use the project version. It says, Using custom www assets from /Users/ray/Desktop/trash/nov14/alpha when in reality, for this text anyway, it copied more than www. -- 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-8020) avoid error message in console for failed renaming of recording-file (if Media object was only used for playing)
[
https://issues.apache.org/jira/browse/CB-8020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Ruß updated CB-8020:
--
Description:
On Android, if a Media object is only used for playing a sound, i.e. not for
recording, then, on releasing the media object, an error is logged to the
LogCat console, complaining about a failed attempt to rename the temporary file
(that is used for recording audio).
Example LogCat output (after releasing the Media object):
{{11-14 13:57:14.138: V/MediaPlayer(29175): destructor}}
{{11-14 13:57:14.138: V/MediaPlayer(29175): disconnect}}
{{11-14 13:57:14.138: D/AudioPlayer(29175): renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3}}
{color:red}{{11-14 13:57:14.138: E/AudioPlayer(29175): FAILED renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3}}{color}
Solution:
in the AudioPlayer class, do not create the MediaRecorder (for audio recording)
on object creation (i.e. in the AudioPlayer's constructor), but instead create
is lazily, only if/when the AudioPlayer is used for recording audio (i.e. in
method {{startRecording(String)}}).
Example solution see:
https://github.com/mmig/cordova-plugin-media/commit/66ac88689cb092179cdc3eda3bd64b1d8616077e
NOTE:
I did run the unit tests from plugin {{org.apache.cordova.media.tests}}
successfully with the changes as linked above to the GitHub repository
(on a Samsung Note 10 device with Android 4.4.2)
was:
On Android, if a Media object is only used for playing a sound, i.e. not for
recording, then, on releasing the media object, an error is logged to the
LogCat console, complaining about a failed attempt to rename the temporary file
(that is used for recording audio).
Example LogCat output (after releasing the Media object):
{{11-14 13:57:14.138: V/MediaPlayer(29175): destructor}}
{{11-14 13:57:14.138: V/MediaPlayer(29175): disconnect}}
{{11-14 13:57:14.138: D/AudioPlayer(29175): renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3}}
{color:red}{{11-14 13:57:14.138: E/AudioPlayer(29175): FAILED renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3}}{color}
Solution:
in the AudioPlayer class, do not create the MediaRecorder (for audio recording)
on object creation (i.e. in the AudioPlayer's constructor), but instead create
is lazily, only if/when the AudioPlayer is used for recording audio (i.e. in
method {{startRecording(String)}}).
avoid error message in console for failed renaming of recording-file (if
Media object was only used for playing)
Key: CB-8020
URL: https://issues.apache.org/jira/browse/CB-8020
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin Media
Reporter: Aaron Ruß
Priority: Minor
Original Estimate: 10m
Remaining Estimate: 10m
On Android, if a Media object is only used for playing a sound, i.e. not for
recording, then, on releasing the media object, an error is logged to the
LogCat console, complaining about a failed attempt to rename the temporary
file (that is used for recording audio).
Example LogCat output (after releasing the Media object):
{{11-14 13:57:14.138: V/MediaPlayer(29175): destructor}}
{{11-14 13:57:14.138: V/MediaPlayer(29175): disconnect}}
{{11-14 13:57:14.138: D/AudioPlayer(29175): renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3}}
{color:red}{{11-14 13:57:14.138: E/AudioPlayer(29175): FAILED renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3}}{color}
Solution:
in the AudioPlayer class, do not create the MediaRecorder (for audio
recording) on object creation (i.e. in the AudioPlayer's constructor), but
instead create is lazily, only if/when the AudioPlayer is used for recording
audio (i.e. in method {{startRecording(String)}}).
Example solution see:
https://github.com/mmig/cordova-plugin-media/commit/66ac88689cb092179cdc3eda3bd64b1d8616077e
NOTE:
I did run the unit tests from plugin {{org.apache.cordova.media.tests}}
successfully with the changes as linked above to the GitHub repository
(on a Samsung Note 10 device with Android 4.4.2)
--
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-8020) avoid error message in console for failed renaming of recording-file (if Media object was only used for playing)
[
https://issues.apache.org/jira/browse/CB-8020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Ruß updated CB-8020:
--
Description:
On Android, if a Media object is only used for playing a sound, i.e. not for
recording, then, on releasing the media object, an error is logged to the
LogCat console, complaining about a failed attempt to rename the temporary file
(that is used for recording audio).
Example LogCat output (after releasing the Media object):
{{11-14 13:57:14.138: V/MediaPlayer(29175): destructor}}
{{11-14 13:57:14.138: V/MediaPlayer(29175): disconnect}}
{{11-14 13:57:14.138: D/AudioPlayer(29175): renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3}}
{color:red}{{11-14 13:57:14.138: E/AudioPlayer(29175): FAILED renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3}}{color}
Solution:
in the AudioPlayer class, do not create the MediaRecorder (for audio recording)
on object creation (i.e. in the AudioPlayer's constructor), but instead create
it lazily, only if/when the AudioPlayer is used for recording audio (i.e. in
method {{startRecording(String)}}).
Example solution see:
https://github.com/mmig/cordova-plugin-media/commit/66ac88689cb092179cdc3eda3bd64b1d8616077e
NOTE:
I did run the unit tests from plugin {{org.apache.cordova.media.tests}}
successfully with the changes as linked above to the GitHub repository
(on a Samsung Note 10 device with Android 4.4.2)
was:
On Android, if a Media object is only used for playing a sound, i.e. not for
recording, then, on releasing the media object, an error is logged to the
LogCat console, complaining about a failed attempt to rename the temporary file
(that is used for recording audio).
Example LogCat output (after releasing the Media object):
{{11-14 13:57:14.138: V/MediaPlayer(29175): destructor}}
{{11-14 13:57:14.138: V/MediaPlayer(29175): disconnect}}
{{11-14 13:57:14.138: D/AudioPlayer(29175): renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3}}
{color:red}{{11-14 13:57:14.138: E/AudioPlayer(29175): FAILED renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3}}{color}
Solution:
in the AudioPlayer class, do not create the MediaRecorder (for audio recording)
on object creation (i.e. in the AudioPlayer's constructor), but instead create
is lazily, only if/when the AudioPlayer is used for recording audio (i.e. in
method {{startRecording(String)}}).
Example solution see:
https://github.com/mmig/cordova-plugin-media/commit/66ac88689cb092179cdc3eda3bd64b1d8616077e
NOTE:
I did run the unit tests from plugin {{org.apache.cordova.media.tests}}
successfully with the changes as linked above to the GitHub repository
(on a Samsung Note 10 device with Android 4.4.2)
avoid error message in console for failed renaming of recording-file (if
Media object was only used for playing)
Key: CB-8020
URL: https://issues.apache.org/jira/browse/CB-8020
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin Media
Reporter: Aaron Ruß
Priority: Minor
Original Estimate: 10m
Remaining Estimate: 10m
On Android, if a Media object is only used for playing a sound, i.e. not for
recording, then, on releasing the media object, an error is logged to the
LogCat console, complaining about a failed attempt to rename the temporary
file (that is used for recording audio).
Example LogCat output (after releasing the Media object):
{{11-14 13:57:14.138: V/MediaPlayer(29175): destructor}}
{{11-14 13:57:14.138: V/MediaPlayer(29175): disconnect}}
{{11-14 13:57:14.138: D/AudioPlayer(29175): renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3}}
{color:red}{{11-14 13:57:14.138: E/AudioPlayer(29175): FAILED renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3}}{color}
Solution:
in the AudioPlayer class, do not create the MediaRecorder (for audio
recording) on object creation (i.e. in the AudioPlayer's constructor), but
instead create it lazily, only if/when the AudioPlayer is used for recording
audio (i.e. in method {{startRecording(String)}}).
Example solution see:
https://github.com/mmig/cordova-plugin-media/commit/66ac88689cb092179cdc3eda3bd64b1d8616077e
NOTE:
I did run the unit tests from plugin {{org.apache.cordova.media.tests}}
successfully with the changes as linked above to the GitHub repository
(on a Samsung Note 10 device with Android 4.4.2)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To
[jira] [Commented] (CB-7944) Some auto tests for plugin file-transfer are fails for windows
[ https://issues.apache.org/jira/browse/CB-7944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14212455#comment-14212455 ] ASF GitHub Bot commented on CB-7944: Github user asfgit closed the pull request at: https://github.com/apache/cordova-plugin-file-transfer/pull/48 Some auto tests for plugin file-transfer are fails for windows -- Key: CB-7944 URL: https://issues.apache.org/jira/browse/CB-7944 Project: Apache Cordova Issue Type: Test Components: Plugin File Transfer, Windows Reporter: Maria Bukharina Repo steps: 1. create mobile-spec app 2. run Plugin auto test for file-transfer plugin Expected: if method doesn't siupport pending test Actual: filetransfer.spec.7 should be able to download a file using file:// (when hosted from file:// filetransfer.spec.18 should be able to upload a file filetransfer.spec.19 should be able to upload a file with http basic auth fails because no file:// access on windwos and onprogress method doesn't supported on WP -- 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-8018) Add vibrate(pattern) fallback on vibrate for Windows Phone 8
[ https://issues.apache.org/jira/browse/CB-8018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14212457#comment-14212457 ] ASF GitHub Bot commented on CB-8018: GitHub user daserge opened a pull request: https://github.com/apache/cordova-plugin-vibration/pull/26 CB-8018 Add vibrate(pattern) fallback on vibrate for Windows Phone 8 Added vibrate(pattern) fallback on vibrate for Windows Phone 8 Added vibration cancelling support for Windows Phone 8 [JIRA issue](https://issues.apache.org/jira/browse/CB-8018) You can merge this pull request into a Git repository by running: $ git pull https://github.com/MSOpenTech/cordova-plugin-vibration CB-8018 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-plugin-vibration/pull/26.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #26 commit 621984529a2ecaa4879012aeef078413742d5797 Author: daserge dase...@yandex.ru Date: 2014-11-14T16:30:11Z CB-8018 Add vibrate(pattern) fallback on vibrate for Windows Phone 8 Added vibrate(pattern) fallback on vibrate for Windows Phone 8 Added vibration cancelling support for Windows Phone 8 Add vibrate(pattern) fallback on vibrate for Windows Phone 8 Key: CB-8018 URL: https://issues.apache.org/jira/browse/CB-8018 Project: Apache Cordova Issue Type: Improvement Components: Plugin Vibration Environment: Windows Phone 8 Reporter: Sergey Shakhnazarov -- 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-8020) avoid error message in console for failed renaming of recording-file (if Media object was only used for playing)
[
https://issues.apache.org/jira/browse/CB-8020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Ruß updated CB-8020:
--
Description:
On Android, if a Media object is only used for playing a sound, i.e. not for
recording, then, on releasing the media object, an error is logged to the
LogCat console, complaining about a failed attempt to rename the temporary file
(that is used for recording audio).
Example LogCat output (after releasing the Media object):
11-14 13:57:14.138: V/MediaPlayer(29175): destructor
11-14 13:57:14.138: V/MediaPlayer(29175): disconnect
11-14 13:57:14.138: D/AudioPlayer(29175): renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3
{color:red}11-14 13:57:14.138: E/AudioPlayer(29175): FAILED renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3{color}
Solution:
in the AudioPlayer class, do not create the MediaRecorder (for audio recording)
on object creation (i.e. in the AudioPlayer's constructor), but instead create
it lazily, only if/when the AudioPlayer is used for recording audio (i.e. in
method {{startRecording(String)}}).
Example solution see:
https://github.com/mmig/cordova-plugin-media/commit/66ac88689cb092179cdc3eda3bd64b1d8616077e
NOTE:
I did run the unit tests from plugin {{org.apache.cordova.media.tests}}
successfully with the changes as linked above to the GitHub repository
(on a Samsung Note 10 device with Android 4.4.2)
was:
On Android, if a Media object is only used for playing a sound, i.e. not for
recording, then, on releasing the media object, an error is logged to the
LogCat console, complaining about a failed attempt to rename the temporary file
(that is used for recording audio).
Example LogCat output (after releasing the Media object):
{{11-14 13:57:14.138: V/MediaPlayer(29175): destructor}}
{{11-14 13:57:14.138: V/MediaPlayer(29175): disconnect}}
{{11-14 13:57:14.138: D/AudioPlayer(29175): renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3}}
{color:red}{{11-14 13:57:14.138: E/AudioPlayer(29175): FAILED renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3}}{color}
Solution:
in the AudioPlayer class, do not create the MediaRecorder (for audio recording)
on object creation (i.e. in the AudioPlayer's constructor), but instead create
it lazily, only if/when the AudioPlayer is used for recording audio (i.e. in
method {{startRecording(String)}}).
Example solution see:
https://github.com/mmig/cordova-plugin-media/commit/66ac88689cb092179cdc3eda3bd64b1d8616077e
NOTE:
I did run the unit tests from plugin {{org.apache.cordova.media.tests}}
successfully with the changes as linked above to the GitHub repository
(on a Samsung Note 10 device with Android 4.4.2)
avoid error message in console for failed renaming of recording-file (if
Media object was only used for playing)
Key: CB-8020
URL: https://issues.apache.org/jira/browse/CB-8020
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin Media
Reporter: Aaron Ruß
Priority: Minor
Original Estimate: 10m
Remaining Estimate: 10m
On Android, if a Media object is only used for playing a sound, i.e. not for
recording, then, on releasing the media object, an error is logged to the
LogCat console, complaining about a failed attempt to rename the temporary
file (that is used for recording audio).
Example LogCat output (after releasing the Media object):
11-14 13:57:14.138: V/MediaPlayer(29175): destructor
11-14 13:57:14.138: V/MediaPlayer(29175): disconnect
11-14 13:57:14.138: D/AudioPlayer(29175): renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3
{color:red}11-14 13:57:14.138: E/AudioPlayer(29175): FAILED renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3{color}
Solution:
in the AudioPlayer class, do not create the MediaRecorder (for audio
recording) on object creation (i.e. in the AudioPlayer's constructor), but
instead create it lazily, only if/when the AudioPlayer is used for recording
audio (i.e. in method {{startRecording(String)}}).
Example solution see:
https://github.com/mmig/cordova-plugin-media/commit/66ac88689cb092179cdc3eda3bd64b1d8616077e
NOTE:
I did run the unit tests from plugin {{org.apache.cordova.media.tests}}
successfully with the changes as linked above to the GitHub repository
(on a Samsung Note 10 device with Android 4.4.2)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail:
[jira] [Updated] (CB-8020) avoid error message in console for failed renaming of recording-file (if Media object was only used for playing)
[
https://issues.apache.org/jira/browse/CB-8020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Ruß updated CB-8020:
--
Description:
On Android, if a Media object is only used for playing a sound, i.e. not for
recording, then, on releasing the media object, an error is logged to the
LogCat console, complaining about a failed attempt to rename the temporary file
(that is used for recording audio).
Example LogCat output (after releasing the Media object):
{panel}
11-14 13:57:14.138: V/MediaPlayer(29175): destructor
11-14 13:57:14.138: V/MediaPlayer(29175): disconnect
11-14 13:57:14.138: D/AudioPlayer(29175): renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3
{color:red}11-14 13:57:14.138: E/AudioPlayer(29175): FAILED renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3{color}
{panel}
Solution:
in the AudioPlayer class, do not create the MediaRecorder (for audio recording)
on object creation (i.e. in the AudioPlayer's constructor), but instead create
it lazily, only if/when the AudioPlayer is used for recording audio (i.e. in
method {{startRecording(String)}}).
Example solution see:
https://github.com/mmig/cordova-plugin-media/commit/66ac88689cb092179cdc3eda3bd64b1d8616077e
NOTE:
I did run the unit tests from plugin {{org.apache.cordova.media.tests}}
successfully with the changes as linked above to the GitHub repository
(on a Samsung Note 10 device with Android 4.4.2)
was:
On Android, if a Media object is only used for playing a sound, i.e. not for
recording, then, on releasing the media object, an error is logged to the
LogCat console, complaining about a failed attempt to rename the temporary file
(that is used for recording audio).
Example LogCat output (after releasing the Media object):
11-14 13:57:14.138: V/MediaPlayer(29175): destructor
11-14 13:57:14.138: V/MediaPlayer(29175): disconnect
11-14 13:57:14.138: D/AudioPlayer(29175): renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3
{color:red}11-14 13:57:14.138: E/AudioPlayer(29175): FAILED renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3{color}
Solution:
in the AudioPlayer class, do not create the MediaRecorder (for audio recording)
on object creation (i.e. in the AudioPlayer's constructor), but instead create
it lazily, only if/when the AudioPlayer is used for recording audio (i.e. in
method {{startRecording(String)}}).
Example solution see:
https://github.com/mmig/cordova-plugin-media/commit/66ac88689cb092179cdc3eda3bd64b1d8616077e
NOTE:
I did run the unit tests from plugin {{org.apache.cordova.media.tests}}
successfully with the changes as linked above to the GitHub repository
(on a Samsung Note 10 device with Android 4.4.2)
avoid error message in console for failed renaming of recording-file (if
Media object was only used for playing)
Key: CB-8020
URL: https://issues.apache.org/jira/browse/CB-8020
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin Media
Reporter: Aaron Ruß
Priority: Minor
Original Estimate: 10m
Remaining Estimate: 10m
On Android, if a Media object is only used for playing a sound, i.e. not for
recording, then, on releasing the media object, an error is logged to the
LogCat console, complaining about a failed attempt to rename the temporary
file (that is used for recording audio).
Example LogCat output (after releasing the Media object):
{panel}
11-14 13:57:14.138: V/MediaPlayer(29175): destructor
11-14 13:57:14.138: V/MediaPlayer(29175): disconnect
11-14 13:57:14.138: D/AudioPlayer(29175): renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3
{color:red}11-14 13:57:14.138: E/AudioPlayer(29175): FAILED renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3{color}
{panel}
Solution:
in the AudioPlayer class, do not create the MediaRecorder (for audio
recording) on object creation (i.e. in the AudioPlayer's constructor), but
instead create it lazily, only if/when the AudioPlayer is used for recording
audio (i.e. in method {{startRecording(String)}}).
Example solution see:
https://github.com/mmig/cordova-plugin-media/commit/66ac88689cb092179cdc3eda3bd64b1d8616077e
NOTE:
I did run the unit tests from plugin {{org.apache.cordova.media.tests}}
successfully with the changes as linked above to the GitHub repository
(on a Samsung Note 10 device with Android 4.4.2)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe,
[jira] [Updated] (CB-8020) avoid error message in console for failed renaming of recording-file (if Media object was only used for playing)
[
https://issues.apache.org/jira/browse/CB-8020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Ruß updated CB-8020:
--
Description:
On Android, if a Media object is only used for playing a sound, i.e. not for
recording, then, on releasing the media object, an error is logged to the
LogCat console, complaining about a failed attempt to rename the temporary file
(that is used for recording audio).
{panel:title=Example LogCat output (after releasing the Media object):}
11-14 13:57:14.138: V/MediaPlayer(29175): destructor
11-14 13:57:14.138: V/MediaPlayer(29175): disconnect
11-14 13:57:14.138: D/AudioPlayer(29175): renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3
{color:red}11-14 13:57:14.138: E/AudioPlayer(29175): FAILED renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3{color}
{panel}
Solution:
in the AudioPlayer class, do not create the MediaRecorder (for audio recording)
on object creation (i.e. in the AudioPlayer's constructor), but instead create
it lazily, only if/when the AudioPlayer is used for recording audio (i.e. in
method {{startRecording(String)}}).
Example solution see:
https://github.com/mmig/cordova-plugin-media/commit/66ac88689cb092179cdc3eda3bd64b1d8616077e
NOTE:
I did run the unit tests from plugin {{org.apache.cordova.media.tests}}
successfully with the changes as linked above to the GitHub repository
(on a Samsung Note 10 device with Android 4.4.2)
was:
On Android, if a Media object is only used for playing a sound, i.e. not for
recording, then, on releasing the media object, an error is logged to the
LogCat console, complaining about a failed attempt to rename the temporary file
(that is used for recording audio).
Example LogCat output (after releasing the Media object):
{panel}
11-14 13:57:14.138: V/MediaPlayer(29175): destructor
11-14 13:57:14.138: V/MediaPlayer(29175): disconnect
11-14 13:57:14.138: D/AudioPlayer(29175): renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3
{color:red}11-14 13:57:14.138: E/AudioPlayer(29175): FAILED renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3{color}
{panel}
Solution:
in the AudioPlayer class, do not create the MediaRecorder (for audio recording)
on object creation (i.e. in the AudioPlayer's constructor), but instead create
it lazily, only if/when the AudioPlayer is used for recording audio (i.e. in
method {{startRecording(String)}}).
Example solution see:
https://github.com/mmig/cordova-plugin-media/commit/66ac88689cb092179cdc3eda3bd64b1d8616077e
NOTE:
I did run the unit tests from plugin {{org.apache.cordova.media.tests}}
successfully with the changes as linked above to the GitHub repository
(on a Samsung Note 10 device with Android 4.4.2)
avoid error message in console for failed renaming of recording-file (if
Media object was only used for playing)
Key: CB-8020
URL: https://issues.apache.org/jira/browse/CB-8020
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin Media
Reporter: Aaron Ruß
Priority: Minor
Original Estimate: 10m
Remaining Estimate: 10m
On Android, if a Media object is only used for playing a sound, i.e. not for
recording, then, on releasing the media object, an error is logged to the
LogCat console, complaining about a failed attempt to rename the temporary
file (that is used for recording audio).
{panel:title=Example LogCat output (after releasing the Media object):}
11-14 13:57:14.138: V/MediaPlayer(29175): destructor
11-14 13:57:14.138: V/MediaPlayer(29175): disconnect
11-14 13:57:14.138: D/AudioPlayer(29175): renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3
{color:red}11-14 13:57:14.138: E/AudioPlayer(29175): FAILED renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3{color}
{panel}
Solution:
in the AudioPlayer class, do not create the MediaRecorder (for audio
recording) on object creation (i.e. in the AudioPlayer's constructor), but
instead create it lazily, only if/when the AudioPlayer is used for recording
audio (i.e. in method {{startRecording(String)}}).
Example solution see:
https://github.com/mmig/cordova-plugin-media/commit/66ac88689cb092179cdc3eda3bd64b1d8616077e
NOTE:
I did run the unit tests from plugin {{org.apache.cordova.media.tests}}
successfully with the changes as linked above to the GitHub repository
(on a Samsung Note 10 device with Android 4.4.2)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CB-8020) avoid error message in console for failed renaming of recording-file (if Media object was only used for playing)
[
https://issues.apache.org/jira/browse/CB-8020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Ruß updated CB-8020:
--
Description:
On Android, if a Media object is only used for playing a sound, i.e. not for
recording, then, on releasing the media object, an error is logged to the
LogCat console, complaining about a failed attempt to rename the temporary file
(that is used for recording audio).
{panel:title=Example LogCat output (after releasing the Media object):}
11-14 13:57:14.138: V/MediaPlayer(29175): destructor
11-14 13:57:14.138: V/MediaPlayer(29175): disconnect
11-14 13:57:14.138: D/AudioPlayer(29175): renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3
{color:red}11-14 13:57:14.138: E/AudioPlayer(29175): FAILED renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3{color}
{panel}
Solution:
in the AudioPlayer class, do not create the MediaRecorder (for audio recording)
on object creation (i.e. in the AudioPlayer's constructor), but instead create
it lazily, only if/when the AudioPlayer is used for recording audio (i.e. in
method {{startRecording(String)}}).
Example solution see:
https://github.com/mmig/cordova-plugin-media/commit/66ac88689cb092179cdc3eda3bd64b1d8616077e
NOTE:
I did run the unit tests from plugin {{org.apache.cordova.media.tests}}
successfully with the changes as linked above to the GitHub repository
(on a Samsung Note 10 device with Android 4.4.2)
NOTE 2:
was:
On Android, if a Media object is only used for playing a sound, i.e. not for
recording, then, on releasing the media object, an error is logged to the
LogCat console, complaining about a failed attempt to rename the temporary file
(that is used for recording audio).
{panel:title=Example LogCat output (after releasing the Media object):}
11-14 13:57:14.138: V/MediaPlayer(29175): destructor
11-14 13:57:14.138: V/MediaPlayer(29175): disconnect
11-14 13:57:14.138: D/AudioPlayer(29175): renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3
{color:red}11-14 13:57:14.138: E/AudioPlayer(29175): FAILED renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3{color}
{panel}
Solution:
in the AudioPlayer class, do not create the MediaRecorder (for audio recording)
on object creation (i.e. in the AudioPlayer's constructor), but instead create
it lazily, only if/when the AudioPlayer is used for recording audio (i.e. in
method {{startRecording(String)}}).
Example solution see:
https://github.com/mmig/cordova-plugin-media/commit/66ac88689cb092179cdc3eda3bd64b1d8616077e
NOTE:
I did run the unit tests from plugin {{org.apache.cordova.media.tests}}
successfully with the changes as linked above to the GitHub repository
(on a Samsung Note 10 device with Android 4.4.2)
avoid error message in console for failed renaming of recording-file (if
Media object was only used for playing)
Key: CB-8020
URL: https://issues.apache.org/jira/browse/CB-8020
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin Media
Reporter: Aaron Ruß
Priority: Minor
Original Estimate: 10m
Remaining Estimate: 10m
On Android, if a Media object is only used for playing a sound, i.e. not for
recording, then, on releasing the media object, an error is logged to the
LogCat console, complaining about a failed attempt to rename the temporary
file (that is used for recording audio).
{panel:title=Example LogCat output (after releasing the Media object):}
11-14 13:57:14.138: V/MediaPlayer(29175): destructor
11-14 13:57:14.138: V/MediaPlayer(29175): disconnect
11-14 13:57:14.138: D/AudioPlayer(29175): renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3
{color:red}11-14 13:57:14.138: E/AudioPlayer(29175): FAILED renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3{color}
{panel}
Solution:
in the AudioPlayer class, do not create the MediaRecorder (for audio
recording) on object creation (i.e. in the AudioPlayer's constructor), but
instead create it lazily, only if/when the AudioPlayer is used for recording
audio (i.e. in method {{startRecording(String)}}).
Example solution see:
https://github.com/mmig/cordova-plugin-media/commit/66ac88689cb092179cdc3eda3bd64b1d8616077e
NOTE:
I did run the unit tests from plugin {{org.apache.cordova.media.tests}}
successfully with the changes as linked above to the GitHub repository
(on a Samsung Note 10 device with Android 4.4.2)
NOTE 2:
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CB-8020) avoid error message in console for failed renaming of recording-file (if Media object was only used for playing)
[
https://issues.apache.org/jira/browse/CB-8020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Ruß updated CB-8020:
--
Description:
On Android, if a Media object is only used for playing a sound, i.e. not for
recording, then, on releasing the media object, an error is logged to the
LogCat console, complaining about a failed attempt to rename the temporary file
(that is used for recording audio).
{panel:title=Example LogCat output (after releasing the Media object):}
11-14 13:57:14.138: V/MediaPlayer(29175): destructor
11-14 13:57:14.138: V/MediaPlayer(29175): disconnect
11-14 13:57:14.138: D/AudioPlayer(29175): renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3
{color:red}11-14 13:57:14.138: E/AudioPlayer(29175): FAILED renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3{color}
{panel}
Solution:
in the AudioPlayer class, do not create the MediaRecorder (for audio recording)
on object creation (i.e. in the AudioPlayer's constructor), but instead create
it lazily, only if/when the AudioPlayer is used for recording audio (i.e. in
method {{startRecording(String)}}).
Example solution see:
https://github.com/mmig/cordova-plugin-media/commit/66ac88689cb092179cdc3eda3bd64b1d8616077e
NOTE:
I did run the unit tests from plugin {{org.apache.cordova.media.tests}}
successfully with the changes as linked above to the GitHub repository
(on a Samsung Note 10 device with Android 4.4.2)
NOTE 2:
this is the same issue as described in
[CB-3800|https://issues.apache.org/jira/browse/CB-3800]
was:
On Android, if a Media object is only used for playing a sound, i.e. not for
recording, then, on releasing the media object, an error is logged to the
LogCat console, complaining about a failed attempt to rename the temporary file
(that is used for recording audio).
{panel:title=Example LogCat output (after releasing the Media object):}
11-14 13:57:14.138: V/MediaPlayer(29175): destructor
11-14 13:57:14.138: V/MediaPlayer(29175): disconnect
11-14 13:57:14.138: D/AudioPlayer(29175): renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3
{color:red}11-14 13:57:14.138: E/AudioPlayer(29175): FAILED renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3{color}
{panel}
Solution:
in the AudioPlayer class, do not create the MediaRecorder (for audio recording)
on object creation (i.e. in the AudioPlayer's constructor), but instead create
it lazily, only if/when the AudioPlayer is used for recording audio (i.e. in
method {{startRecording(String)}}).
Example solution see:
https://github.com/mmig/cordova-plugin-media/commit/66ac88689cb092179cdc3eda3bd64b1d8616077e
NOTE:
I did run the unit tests from plugin {{org.apache.cordova.media.tests}}
successfully with the changes as linked above to the GitHub repository
(on a Samsung Note 10 device with Android 4.4.2)
NOTE 2:
avoid error message in console for failed renaming of recording-file (if
Media object was only used for playing)
Key: CB-8020
URL: https://issues.apache.org/jira/browse/CB-8020
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin Media
Reporter: Aaron Ruß
Priority: Minor
Original Estimate: 10m
Remaining Estimate: 10m
On Android, if a Media object is only used for playing a sound, i.e. not for
recording, then, on releasing the media object, an error is logged to the
LogCat console, complaining about a failed attempt to rename the temporary
file (that is used for recording audio).
{panel:title=Example LogCat output (after releasing the Media object):}
11-14 13:57:14.138: V/MediaPlayer(29175): destructor
11-14 13:57:14.138: V/MediaPlayer(29175): disconnect
11-14 13:57:14.138: D/AudioPlayer(29175): renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3
{color:red}11-14 13:57:14.138: E/AudioPlayer(29175): FAILED renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3{color}
{panel}
Solution:
in the AudioPlayer class, do not create the MediaRecorder (for audio
recording) on object creation (i.e. in the AudioPlayer's constructor), but
instead create it lazily, only if/when the AudioPlayer is used for recording
audio (i.e. in method {{startRecording(String)}}).
Example solution see:
https://github.com/mmig/cordova-plugin-media/commit/66ac88689cb092179cdc3eda3bd64b1d8616077e
NOTE:
I did run the unit tests from plugin {{org.apache.cordova.media.tests}}
successfully with the changes as linked above to the GitHub repository
(on a Samsung Note 10 device with Android 4.4.2)
[jira] [Created] (CB-8021) httpMethod option in FileUploadOptions is not indicated in the documentation.
Venkata Kiran created CB-8021: - Summary: httpMethod option in FileUploadOptions is not indicated in the documentation. Key: CB-8021 URL: https://issues.apache.org/jira/browse/CB-8021 Project: Apache Cordova Issue Type: Bug Components: Docs, Plugin File Transfer Affects Versions: 4.0.0 Environment: Android, ios Reporter: Venkata Kiran Priority: Trivial httpMethod option in FileUploadOptions is not indicated in the documentation, while it is referred to in javascript layer and also in the Android code. https://github.com/apache/cordova-plugin-file-transfer/blob/master/doc/index.md -- 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-8020) avoid error message in console for failed renaming of recording-file (if Media object was only used for playing)
[
https://issues.apache.org/jira/browse/CB-8020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Ruß updated CB-8020:
--
Description:
On Android, if a Media object is only used for playing a sound, i.e. not for
recording, then, on releasing the media object, an error is logged to the
LogCat console, complaining about a failed attempt to rename the temporary file
(that is used for recording audio).
{panel:title=Example LogCat output (after releasing the Media object):}
11-14 13:57:14.138: V/MediaPlayer(29175): destructor
11-14 13:57:14.138: V/MediaPlayer(29175): disconnect
11-14 13:57:14.138: D/AudioPlayer(29175): renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3
{color:red}11-14 13:57:14.138: E/AudioPlayer(29175): FAILED renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3{color}
{panel}
Solution:
in the AudioPlayer class, do not create the MediaRecorder (for audio recording)
on object creation (i.e. in the AudioPlayer's constructor), but instead create
it lazily, only if/when the AudioPlayer is used for recording audio (i.e. in
method {{startRecording(String)}}).
Example solution see:
https://github.com/mmig/cordova-plugin-media/commit/66ac88689cb092179cdc3eda3bd64b1d8616077e
NOTE:
I did run the unit tests from plugin {{org.apache.cordova.media.tests}}
successfully with the changes as linked above to the GitHub repository
(on a Samsung Note 10 device with Android 4.4.2)
NOTE 2:
this is the same issue as described in
[CB-3800|https://issues.apache.org/jira/browse/CB-3800] and
[CB-3835|https://issues.apache.org/jira/browse/CB-3835] (in CB-3835 David
Mihalcik already provided the solution ... but obviously it was not accepted
yet(?))
was:
On Android, if a Media object is only used for playing a sound, i.e. not for
recording, then, on releasing the media object, an error is logged to the
LogCat console, complaining about a failed attempt to rename the temporary file
(that is used for recording audio).
{panel:title=Example LogCat output (after releasing the Media object):}
11-14 13:57:14.138: V/MediaPlayer(29175): destructor
11-14 13:57:14.138: V/MediaPlayer(29175): disconnect
11-14 13:57:14.138: D/AudioPlayer(29175): renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3
{color:red}11-14 13:57:14.138: E/AudioPlayer(29175): FAILED renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3{color}
{panel}
Solution:
in the AudioPlayer class, do not create the MediaRecorder (for audio recording)
on object creation (i.e. in the AudioPlayer's constructor), but instead create
it lazily, only if/when the AudioPlayer is used for recording audio (i.e. in
method {{startRecording(String)}}).
Example solution see:
https://github.com/mmig/cordova-plugin-media/commit/66ac88689cb092179cdc3eda3bd64b1d8616077e
NOTE:
I did run the unit tests from plugin {{org.apache.cordova.media.tests}}
successfully with the changes as linked above to the GitHub repository
(on a Samsung Note 10 device with Android 4.4.2)
NOTE 2:
this is the same issue as described in
[CB-3800|https://issues.apache.org/jira/browse/CB-3800]
avoid error message in console for failed renaming of recording-file (if
Media object was only used for playing)
Key: CB-8020
URL: https://issues.apache.org/jira/browse/CB-8020
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin Media
Reporter: Aaron Ruß
Priority: Minor
Original Estimate: 10m
Remaining Estimate: 10m
On Android, if a Media object is only used for playing a sound, i.e. not for
recording, then, on releasing the media object, an error is logged to the
LogCat console, complaining about a failed attempt to rename the temporary
file (that is used for recording audio).
{panel:title=Example LogCat output (after releasing the Media object):}
11-14 13:57:14.138: V/MediaPlayer(29175): destructor
11-14 13:57:14.138: V/MediaPlayer(29175): disconnect
11-14 13:57:14.138: D/AudioPlayer(29175): renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3
{color:red}11-14 13:57:14.138: E/AudioPlayer(29175): FAILED renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3{color}
{panel}
Solution:
in the AudioPlayer class, do not create the MediaRecorder (for audio
recording) on object creation (i.e. in the AudioPlayer's constructor), but
instead create it lazily, only if/when the AudioPlayer is used for recording
audio (i.e. in method {{startRecording(String)}}).
Example solution see:
[jira] [Updated] (CB-8020) avoid error message in console for failed renaming of recording-file (if Media object was only used for playing)
[
https://issues.apache.org/jira/browse/CB-8020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Ruß updated CB-8020:
--
Description:
On Android, if a Media object is only used for playing a sound, i.e. not for
recording, then, on releasing the media object, an error is logged to the
LogCat console, complaining about a failed attempt to rename the temporary file
(that is used for recording audio).
{panel:title=Example LogCat output (after releasing the Media object):}
11-14 13:57:14.138: V/MediaPlayer(29175): destructor
11-14 13:57:14.138: V/MediaPlayer(29175): disconnect
11-14 13:57:14.138: D/AudioPlayer(29175): renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3
{color:red}11-14 13:57:14.138: E/AudioPlayer(29175): FAILED renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3{color}
{panel}
Solution:
in the AudioPlayer class, do not create the MediaRecorder (for audio recording)
on object creation (i.e. in the AudioPlayer's constructor), but instead create
it lazily, only if/when the AudioPlayer is used for recording audio (i.e. in
method {{startRecording(String)}}).
Example solution see:
https://github.com/mmig/cordova-plugin-media/commit/66ac88689cb092179cdc3eda3bd64b1d8616077e
NOTE:
I did run the unit tests from plugin {{org.apache.cordova.media.tests}}
successfully with the changes as linked above to the GitHub repository
(on a Samsung Note 10 device with Android 4.4.2)
NOTE 2:
this is the same issue as described in
[CB-3800|https://issues.apache.org/jira/browse/CB-3800] and
[CB-3835|https://issues.apache.org/jira/browse/CB-3835] (in CB-3835 David
Mihalcik already provided the solution ... but obviously it was not accepted
yet (??))
was:
On Android, if a Media object is only used for playing a sound, i.e. not for
recording, then, on releasing the media object, an error is logged to the
LogCat console, complaining about a failed attempt to rename the temporary file
(that is used for recording audio).
{panel:title=Example LogCat output (after releasing the Media object):}
11-14 13:57:14.138: V/MediaPlayer(29175): destructor
11-14 13:57:14.138: V/MediaPlayer(29175): disconnect
11-14 13:57:14.138: D/AudioPlayer(29175): renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3
{color:red}11-14 13:57:14.138: E/AudioPlayer(29175): FAILED renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3{color}
{panel}
Solution:
in the AudioPlayer class, do not create the MediaRecorder (for audio recording)
on object creation (i.e. in the AudioPlayer's constructor), but instead create
it lazily, only if/when the AudioPlayer is used for recording audio (i.e. in
method {{startRecording(String)}}).
Example solution see:
https://github.com/mmig/cordova-plugin-media/commit/66ac88689cb092179cdc3eda3bd64b1d8616077e
NOTE:
I did run the unit tests from plugin {{org.apache.cordova.media.tests}}
successfully with the changes as linked above to the GitHub repository
(on a Samsung Note 10 device with Android 4.4.2)
NOTE 2:
this is the same issue as described in
[CB-3800|https://issues.apache.org/jira/browse/CB-3800] and
[CB-3835|https://issues.apache.org/jira/browse/CB-3835] (in CB-3835 David
Mihalcik already provided the solution ... but obviously it was not accepted
yet(?))
avoid error message in console for failed renaming of recording-file (if
Media object was only used for playing)
Key: CB-8020
URL: https://issues.apache.org/jira/browse/CB-8020
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin Media
Reporter: Aaron Ruß
Priority: Minor
Original Estimate: 10m
Remaining Estimate: 10m
On Android, if a Media object is only used for playing a sound, i.e. not for
recording, then, on releasing the media object, an error is logged to the
LogCat console, complaining about a failed attempt to rename the temporary
file (that is used for recording audio).
{panel:title=Example LogCat output (after releasing the Media object):}
11-14 13:57:14.138: V/MediaPlayer(29175): destructor
11-14 13:57:14.138: V/MediaPlayer(29175): disconnect
11-14 13:57:14.138: D/AudioPlayer(29175): renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3
{color:red}11-14 13:57:14.138: E/AudioPlayer(29175): FAILED renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3{color}
{panel}
Solution:
in the AudioPlayer class, do not create the MediaRecorder (for audio
recording) on object creation (i.e. in the AudioPlayer's constructor), but
instead create it lazily,
[jira] [Updated] (CB-8020) avoid error message in console for failed renaming of recording-file (if Media object was only used for playing)
[
https://issues.apache.org/jira/browse/CB-8020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Ruß updated CB-8020:
--
Description:
On Android, if a Media object is only used for playing a sound, i.e. not for
recording, then, on releasing the media object, an error is logged to the
LogCat console, complaining about a failed attempt to rename the temporary file
(that is used for recording audio).
{panel:title=Example LogCat output (after releasing the Media object):}
11-14 13:57:14.138: V/MediaPlayer(29175): destructor
11-14 13:57:14.138: V/MediaPlayer(29175): disconnect
11-14 13:57:14.138: D/AudioPlayer(29175): renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3
{color:red}11-14 13:57:14.138: E/AudioPlayer(29175): FAILED renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3{color}
{panel}
Solution:
in the AudioPlayer class, do not create the MediaRecorder (for audio recording)
on object creation (i.e. in the AudioPlayer's constructor), but instead create
it lazily, only if/when the AudioPlayer is used for recording audio (i.e. in
method {{startRecording(String)}}).
Example solution see:
https://github.com/mmig/cordova-plugin-media/commit/66ac88689cb092179cdc3eda3bd64b1d8616077e
NOTE:
In addition to manually testing, that that the proposed changes (see GitHub
link above) did not brake recording, I also did run the unit tests from plugin
{{org.apache.cordova.media.tests}} successfully
(on a Samsung Note 10 device with Android 4.4.2)
NOTE 2:
this is the same issue as described in
[CB-3800|https://issues.apache.org/jira/browse/CB-3800] and
[CB-3835|https://issues.apache.org/jira/browse/CB-3835]
...in CB-3835 David Mihalcik already provided the solution ... but it was not
accepted ... yet (??)
was:
On Android, if a Media object is only used for playing a sound, i.e. not for
recording, then, on releasing the media object, an error is logged to the
LogCat console, complaining about a failed attempt to rename the temporary file
(that is used for recording audio).
{panel:title=Example LogCat output (after releasing the Media object):}
11-14 13:57:14.138: V/MediaPlayer(29175): destructor
11-14 13:57:14.138: V/MediaPlayer(29175): disconnect
11-14 13:57:14.138: D/AudioPlayer(29175): renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3
{color:red}11-14 13:57:14.138: E/AudioPlayer(29175): FAILED renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3{color}
{panel}
Solution:
in the AudioPlayer class, do not create the MediaRecorder (for audio recording)
on object creation (i.e. in the AudioPlayer's constructor), but instead create
it lazily, only if/when the AudioPlayer is used for recording audio (i.e. in
method {{startRecording(String)}}).
Example solution see:
https://github.com/mmig/cordova-plugin-media/commit/66ac88689cb092179cdc3eda3bd64b1d8616077e
NOTE:
I did run the unit tests from plugin {{org.apache.cordova.media.tests}}
successfully with the changes as linked above to the GitHub repository
(on a Samsung Note 10 device with Android 4.4.2)
NOTE 2:
this is the same issue as described in
[CB-3800|https://issues.apache.org/jira/browse/CB-3800] and
[CB-3835|https://issues.apache.org/jira/browse/CB-3835] (in CB-3835 David
Mihalcik already provided the solution ... but obviously it was not accepted
yet (??))
avoid error message in console for failed renaming of recording-file (if
Media object was only used for playing)
Key: CB-8020
URL: https://issues.apache.org/jira/browse/CB-8020
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin Media
Reporter: Aaron Ruß
Priority: Minor
Original Estimate: 10m
Remaining Estimate: 10m
On Android, if a Media object is only used for playing a sound, i.e. not for
recording, then, on releasing the media object, an error is logged to the
LogCat console, complaining about a failed attempt to rename the temporary
file (that is used for recording audio).
{panel:title=Example LogCat output (after releasing the Media object):}
11-14 13:57:14.138: V/MediaPlayer(29175): destructor
11-14 13:57:14.138: V/MediaPlayer(29175): disconnect
11-14 13:57:14.138: D/AudioPlayer(29175): renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3
{color:red}11-14 13:57:14.138: E/AudioPlayer(29175): FAILED renaming
/storage/emulated/0/tmprecording.3gp to
/android_asset/www/audio/beep-notification.mp3{color}
{panel}
Solution:
in the AudioPlayer class, do not create the MediaRecorder (for audio
recording) on object creation (i.e. in the
[jira] [Commented] (CB-8018) Add vibrate(pattern) fallback on vibrate for Windows Phone 8
[ https://issues.apache.org/jira/browse/CB-8018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14212594#comment-14212594 ] ASF subversion and git services commented on CB-8018: - Commit 621984529a2ecaa4879012aeef078413742d5797 in cordova-plugin-vibration's branch refs/heads/master from daserge [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-vibration.git;h=6219845 ] CB-8018 Add vibrate(pattern) fallback on vibrate for Windows Phone 8 Added vibrate(pattern) fallback on vibrate for Windows Phone 8 Added vibration cancelling support for Windows Phone 8 Add vibrate(pattern) fallback on vibrate for Windows Phone 8 Key: CB-8018 URL: https://issues.apache.org/jira/browse/CB-8018 Project: Apache Cordova Issue Type: Improvement Components: Plugin Vibration Environment: Windows Phone 8 Reporter: Sergey Shakhnazarov -- 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-8018) Add vibrate(pattern) fallback on vibrate for Windows Phone 8
[ https://issues.apache.org/jira/browse/CB-8018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14212612#comment-14212612 ] ASF GitHub Bot commented on CB-8018: Github user asfgit closed the pull request at: https://github.com/apache/cordova-plugin-vibration/pull/26 Add vibrate(pattern) fallback on vibrate for Windows Phone 8 Key: CB-8018 URL: https://issues.apache.org/jira/browse/CB-8018 Project: Apache Cordova Issue Type: Improvement Components: Plugin Vibration Environment: Windows Phone 8 Reporter: Sergey Shakhnazarov -- 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-7930) create coho toolsRelease command based off nightly
[ https://issues.apache.org/jira/browse/CB-7930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14212679#comment-14212679 ] ASF subversion and git services commented on CB-7930: - Commit e9f37cbe9b9e9617e62452873c987d67bab9eca5 in cordova-coho's branch refs/heads/master from [~stevegill] [ https://git-wip-us.apache.org/repos/asf?p=cordova-coho.git;h=e9f37cb ] CB-7930 added functions for automating tools release create coho toolsRelease command based off nightly -- Key: CB-7930 URL: https://issues.apache.org/jira/browse/CB-7930 Project: Apache Cordova Issue Type: Bug Components: Coho Reporter: Steve Gill Assignee: Steve Gill It will be based off coho nightly. Multi-step process. Proposal below. Still figuring out some details (what to pass in). Feel free to comment and provide feedback. Step 1) coho prepare-tools-release --jira ISSUENUMBER - Use latest tags in platform repos; use in platformsConfig.json - Include cordova-js plugman (nightlies don't)(cordova-js: only if changes exist) - Update package.json files + relevant dependencies - npm link relevant repos - run tests - generate release notes for tools repos - Ask user for manual curation for changes in release notes Step 2) coho publish-tools --rc --jira ISSUENUMBER - branch tools repos (no need to cherry-pick release log changes) - update versions on master with -dev - Commit changes - Build archive - publish archive to npm under rc tag - publish to dist/dev Step 3) (manual for now) - Start vote thread - close vote thread Step 4) coho publish-tools --final --jira ISSUENUMBER - Publish to dist delete dist/dev - Change npm latest tags to point to new versions Not including for now: - Generating issue on Jira (should be done manually pre step 1) - Pinning dependencies (should be done manually pre step 1) - license checks (should be done manually pre step 1) - audit-license-headers (should be done manually pre step 1) - Changes to docs.cordova.io - Creating blog post -- 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-8022) plugman info foo yields [Object] for the maintainers
Josh Soref created CB-8022:
--
Summary: plugman info foo yields [Object] for the maintainers
Key: CB-8022
URL: https://issues.apache.org/jira/browse/CB-8022
Project: Apache Cordova
Issue Type: Bug
Components: Plugman
Affects Versions: 3.5.0
Reporter: Josh Soref
{quote}
plugman info org.apache.cordova.file |grep -A1 maintain
{quote}
yields:
{quote}
maintainers:
[ \[Object],
{quote}
--
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-8022) plugman info foo yields [Object] for the maintainers and engines
[
https://issues.apache.org/jira/browse/CB-8022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Soref updated CB-8022:
---
Summary: plugman info foo yields [Object] for the maintainers and engines
(was: plugman info foo yields [Object] for the maintainers)
plugman info foo yields [Object] for the maintainers and engines
Key: CB-8022
URL: https://issues.apache.org/jira/browse/CB-8022
Project: Apache Cordova
Issue Type: Bug
Components: Plugman
Affects Versions: 3.5.0
Reporter: Josh Soref
{quote}
plugman info org.apache.cordova.file |grep -A1 maintain
{quote}
yields:
{quote}
maintainers:
[ \[Object],
{quote}
--
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-8022) plugman info foo yields [Object] for the maintainers and engines
[
https://issues.apache.org/jira/browse/CB-8022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Soref updated CB-8022:
---
Description:
{quote}
plugman info org.apache.cordova.file |grep -A1 maintain
{quote}
yields:
{quote}
maintainers:
[ \[Object],
{quote}
and
{quote}
info org.apache.cordova.statusbar |grep 'engines:'
{quote}
yields:
{quote}
engines: [ \[Object] ],
{quote}
was:
{quote}
plugman info org.apache.cordova.file |grep -A1 maintain
{quote}
yields:
{quote}
maintainers:
[ \[Object],
{quote}
plugman info foo yields [Object] for the maintainers and engines
Key: CB-8022
URL: https://issues.apache.org/jira/browse/CB-8022
Project: Apache Cordova
Issue Type: Bug
Components: Plugman
Affects Versions: 3.5.0
Reporter: Josh Soref
{quote}
plugman info org.apache.cordova.file |grep -A1 maintain
{quote}
yields:
{quote}
maintainers:
[ \[Object],
{quote}
and
{quote}
info org.apache.cordova.statusbar |grep 'engines:'
{quote}
yields:
{quote}
engines: [ \[Object] ],
{quote}
--
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-7734) navigator.notification.alert or navigator.notification.confirm seem have a many words issue
[ https://issues.apache.org/jira/browse/CB-7734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14212774#comment-14212774 ] ASF GitHub Bot commented on CB-7734: Github user shazron commented on the pull request: https://github.com/apache/cordova-plugin-dialogs/pull/39#issuecomment-63123720 Hi Julio, I'm sure you will have followed the dev@ discussion by now. Two changes are required, since you are using iOS 8 API code. 1. Change your use of `[UIAlertController class]` to `NSClassFromString(@UIAlertController)`. On iOS devices iOS 8 your code will crash. 2. Wrap the whole code block with iOS 8 code with `#ifdef __IPHONE_8_0`. This way people using the Xcode 5 (which is still allowed by Apple) will not have compilation errors. I would test the adjusted code out on an iOS 7 and iOS 8 device, and compile using Xcode 5 and 6. navigator.notification.alert or navigator.notification.confirm seem have a many words issue - Key: CB-7734 URL: https://issues.apache.org/jira/browse/CB-7734 Project: Apache Cordova Issue Type: Improvement Components: Plugin Dialogs Affects Versions: 3.6.3 Environment: PGB 3.6.3 with the all latest core plugin https://build.phonegap.com/plugins ios 8.02 environment Reporter: Colin Bau Assignee: jcesarmobile Labels: notification Original Estimate: 12h Remaining Estimate: 12h Improvement 1 according to this https://issues.apache.org/jira/browse/CB-6528 a same problem just like the WP，ios have this problem too when the words is greater than one page it can't slide up and down Improvement 2 all words center problem，I think maybe Left-aligned is more Beautiful (because when in Android，all words Left-aligned) http://www.littlebau.com/ios_1.png Improvement 3 all words looks like small and Vague (maybe in Chinese)，is there any way (maybe future) can let become more Clear ? http://www.littlebau.com/ios_1.png -- 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-7734) navigator.notification.alert or navigator.notification.confirm seem have a many words issue
[ https://issues.apache.org/jira/browse/CB-7734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14213050#comment-14213050 ] ASF GitHub Bot commented on CB-7734: Github user jcesarmobile commented on the pull request: https://github.com/apache/cordova-plugin-dialogs/pull/39#issuecomment-63144935 [UIAlertController class] doesn't crash on iOS 7 devices if you compile it on xcode 6 using iOS 8 SDK. I'm making the changes for Xcode 5 right now navigator.notification.alert or navigator.notification.confirm seem have a many words issue - Key: CB-7734 URL: https://issues.apache.org/jira/browse/CB-7734 Project: Apache Cordova Issue Type: Improvement Components: Plugin Dialogs Affects Versions: 3.6.3 Environment: PGB 3.6.3 with the all latest core plugin https://build.phonegap.com/plugins ios 8.02 environment Reporter: Colin Bau Assignee: jcesarmobile Labels: notification Original Estimate: 12h Remaining Estimate: 12h Improvement 1 according to this https://issues.apache.org/jira/browse/CB-6528 a same problem just like the WP，ios have this problem too when the words is greater than one page it can't slide up and down Improvement 2 all words center problem，I think maybe Left-aligned is more Beautiful (because when in Android，all words Left-aligned) http://www.littlebau.com/ios_1.png Improvement 3 all words looks like small and Vague (maybe in Chinese)，is there any way (maybe future) can let become more Clear ? http://www.littlebau.com/ios_1.png -- 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-7734) navigator.notification.alert or navigator.notification.confirm seem have a many words issue
[ https://issues.apache.org/jira/browse/CB-7734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14213057#comment-14213057 ] ASF GitHub Bot commented on CB-7734: Github user shazron commented on the pull request: https://github.com/apache/cordova-plugin-dialogs/pull/39#issuecomment-63145321 In any case, NSClassFromString is the safest thing you can do, and is the best practice for supporting iOS 8-6. navigator.notification.alert or navigator.notification.confirm seem have a many words issue - Key: CB-7734 URL: https://issues.apache.org/jira/browse/CB-7734 Project: Apache Cordova Issue Type: Improvement Components: Plugin Dialogs Affects Versions: 3.6.3 Environment: PGB 3.6.3 with the all latest core plugin https://build.phonegap.com/plugins ios 8.02 environment Reporter: Colin Bau Assignee: jcesarmobile Labels: notification Original Estimate: 12h Remaining Estimate: 12h Improvement 1 according to this https://issues.apache.org/jira/browse/CB-6528 a same problem just like the WP，ios have this problem too when the words is greater than one page it can't slide up and down Improvement 2 all words center problem，I think maybe Left-aligned is more Beautiful (because when in Android，all words Left-aligned) http://www.littlebau.com/ios_1.png Improvement 3 all words looks like small and Vague (maybe in Chinese)，is there any way (maybe future) can let become more Clear ? http://www.littlebau.com/ios_1.png -- 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-7734) navigator.notification.alert or navigator.notification.confirm seem have a many words issue
[ https://issues.apache.org/jira/browse/CB-7734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14213065#comment-14213065 ] ASF GitHub Bot commented on CB-7734: Github user jcesarmobile commented on the pull request: https://github.com/apache/cordova-plugin-dialogs/pull/39#issuecomment-63145889 done navigator.notification.alert or navigator.notification.confirm seem have a many words issue - Key: CB-7734 URL: https://issues.apache.org/jira/browse/CB-7734 Project: Apache Cordova Issue Type: Improvement Components: Plugin Dialogs Affects Versions: 3.6.3 Environment: PGB 3.6.3 with the all latest core plugin https://build.phonegap.com/plugins ios 8.02 environment Reporter: Colin Bau Assignee: jcesarmobile Labels: notification Original Estimate: 12h Remaining Estimate: 12h Improvement 1 according to this https://issues.apache.org/jira/browse/CB-6528 a same problem just like the WP，ios have this problem too when the words is greater than one page it can't slide up and down Improvement 2 all words center problem，I think maybe Left-aligned is more Beautiful (because when in Android，all words Left-aligned) http://www.littlebau.com/ios_1.png Improvement 3 all words looks like small and Vague (maybe in Chinese)，is there any way (maybe future) can let become more Clear ? http://www.littlebau.com/ios_1.png -- 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-8023) weinre console.log fails when given null value
Kevin Turner created CB-8023: Summary: weinre console.log fails when given null value Key: CB-8023 URL: https://issues.apache.org/jira/browse/CB-8023 Project: Apache Cordova Issue Type: Bug Components: weinre Reporter: Kevin Turner Assignee: Patrick Mueller weinre's Console._generic, through which all console.log messages go, contains this line: https://github.com/apache/cordova-weinre/blob/f8bcc48f84d9d08f04993328124a62b6bc5026c4/weinre.web/modules/weinre/target/Console.coffee#L78 message = messageParts[0].toString() When messageParts[0] is null, that fails with null is not an object (on cordova on iOS, other browsers may have different messages but also may not have a toString on null). It's a small mistake but terrifically annoying to track down such a crash introduced by this debugging tool. -- 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-7734) navigator.notification.alert or navigator.notification.confirm seem have a many words issue
[ https://issues.apache.org/jira/browse/CB-7734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14213337#comment-14213337 ] ASF GitHub Bot commented on CB-7734: Github user bau720123 commented on the pull request: https://github.com/apache/cordova-plugin-dialogs/pull/39#issuecomment-63158994 I am the original post https://issues.apache.org/jira/browse/CB-7734 well... really thanks for @jcesarmobile and @shazron help navigator.notification.alert or navigator.notification.confirm seem have a many words issue - Key: CB-7734 URL: https://issues.apache.org/jira/browse/CB-7734 Project: Apache Cordova Issue Type: Improvement Components: Plugin Dialogs Affects Versions: 3.6.3 Environment: PGB 3.6.3 with the all latest core plugin https://build.phonegap.com/plugins ios 8.02 environment Reporter: Colin Bau Assignee: jcesarmobile Labels: notification Original Estimate: 12h Remaining Estimate: 12h Improvement 1 according to this https://issues.apache.org/jira/browse/CB-6528 a same problem just like the WP，ios have this problem too when the words is greater than one page it can't slide up and down Improvement 2 all words center problem，I think maybe Left-aligned is more Beautiful (because when in Android，all words Left-aligned) http://www.littlebau.com/ios_1.png Improvement 3 all words looks like small and Vague (maybe in Chinese)，is there any way (maybe future) can let become more Clear ? http://www.littlebau.com/ios_1.png -- 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
