cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Becky Gibson (JIRA)" <>
Subject [jira] [Commented] (CB-571) Check that audio file recording to using Media.startRecord is of type .wav
Date Tue, 05 Feb 2013 22:09:13 GMT


Becky Gibson commented on CB-571:

I'm looking at how to fix this but it is going to be difficult to unify with Android so I
could use some help.  

For recording via the media object you could pass in documents://filename to store a recording
in the application documents directory.  Andrew suggested requiring a full path name (or documents://)
for the file name of the recording.  However, one of the biggest complaints in this ticket
is the difference between iOS and Android.  Currently iOS requires that the file exist (which
is what I am changing) and Android does not. Android accepts just a filename and then stores
it in: new File("/data/data/" + handler.cordova.getActivity().getPackageName() + "/cache/"
+ file).  Thus, the reason CB-571 has been open so long - how to unify these apis with the
least changes.  Suggestions welcome!
> Check that audio file recording to using Media.startRecord is of type .wav
> --------------------------------------------------------------------------
>                 Key: CB-571
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Improvement
>          Components: iOS
>    Affects Versions: 1.6.1
>         Environment: iOS
>            Reporter: Ram Kulkarni
>            Assignee: Becky Gibson
>            Priority: Minor
>              Labels: ios, media
>             Fix For: 2.5.0
> As we document in {{startRecord}} on our [docs page|],
when recording audio in iOS, you need to make sure the file exists and that it is of type
> It would be nice if the {{startRecordingAudio}} method in CDVSound.m checked that the
requested file to record to is of the right type, and throw an error if it is not.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message