Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of libby.baldwin@gmail.com
 designates 209.85.214.175 as permitted sender)
Received-SPF: pass (google.com: domain of libby.baldwin@gmail.com designates
 10.182.160.33 as permitted sender) client-ip=10.182.160.33;
MIME-Version: 1.0
In-Reply-To: 
 <1266942189.5659.1330563958833.JavaMail.tomcat@hel.zones.apache.org>
References: 
 <1634302289.5525.1330561918875.JavaMail.tomcat@hel.zones.apache.org>
	<1266942189.5659.1330563958833.JavaMail.tomcat@hel.zones.apache.org>
Date: Thu, 1 Mar 2012 09:47:05 -0800
Message-ID: 
 <CA+YNw4OFJP5w62qZOXq7Z_0sz5rEs9Wf734HVOx=h6J6pGraEg@mail.gmail.com>
Subject: Re: [jira] [Resolved] (CB-290) Capture API callbacks are failing
From: Elizabeth Baldwin <libby.baldwin@gmail.com>
To: callback-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=f46d0447f2665d7e8204ba320c2a

--f46d0447f2665d7e8204ba320c2a
Content-Type: text/plain; charset=ISO-8859-1

Testing with:
https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-android.git;a=summary
master at macdonst's latest checkin today

Test: my api demo app, does not replay or upload capture results, but
calls .getFormatData() on each success result.

Capture/Audio: Get results file back, duration now reported in seconds
(docs say duration in seconds, in 1.4.1 was in milliseconds, so I guess
the difference in units is a FIX in 1.5.0 not a BUG)
Capture/Image: Ok
Capture/Video: Same issue with units as Audio.

Result: As of 1.5.0, processing of captured data, duration, should expect
seconds
not msecs.

On Wed, Feb 29, 2012 at 5:05 PM, Joe Bowser (Resolved) (JIRA) <
jira@apache.org> wrote:

>
>     [
> https://issues.apache.org/jira/browse/CB-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>
> Joe Bowser resolved CB-290.
> ---------------------------
>
>    Resolution: Fixed
>      Assignee: Joe Bowser  (was: Filip Maj)
>
> This was a Callback-JS bug where we weren't handling what was being passed
> back correctly.  We may need to figure out this API again.
>
> > Capture API callbacks are failing
> > ---------------------------------
> >
> >                 Key: CB-290
> >                 URL: https://issues.apache.org/jira/browse/CB-290
> >             Project: Apache Callback
> >          Issue Type: Bug
> >          Components: Android
> >    Affects Versions: Master
> >            Reporter: Joe Bowser
> >            Assignee: Joe Bowser
> >            Priority: Blocker
> >             Fix For: 1.5.0
> >
> >
> > The Capture API is broken on Android, even though it starts the
> activities properly, the results aren't making their way back to the JS.
>  This appears to have started with the refactor.  Test with the PhoneGap
> docs.
> > D/CordovaLog(18020): Error in success callback: Capture2 =
> ReferenceError: pluginResult is not defined
> > D/CordovaLog(18020): file:///android_asset/www/cordova-1.5.0rc1.js: Line
> 544 : Error in success callback: Capture2 = ReferenceError: pluginResult is
> not defined
> > I/Web Console(18020): Error in success callback: Capture2 =
> ReferenceError: pluginResult is not defined at
> file:///android_asset/www/cordova-1.5.0rc1.js:544
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA
> administrators:
> https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>

--f46d0447f2665d7e8204ba320c2a--