Unable to record in IE9 or FF

Description

On http://nightly2.sakaiproject.org:8082/portal, I tried to record an audio question, both on IE9 and FF9. IE9 will NOT allow me to record, but no errors pop up.

On FF9, I did receive an error and am wondering if this may be part of the problem in SAM-1779.

I'm uploading a screenshot of the error which displays on nightly2, (which does not appear when recording using FF on 2.9 b07).

To reproduce:
Create a test with an audio question and publish it

As the student, begin the test, click on 'Click to record your answer...'
Click the 'Record' button in the pop-up

Attachments

1

Activity

Show:

Steve Swinsburg October 4, 2012 at 4:45 PM

I have confirmed that this is due to the signing of the applet not being performed when Samigo is built from source. The issue is that the samigo-audio module is built from source, which creates an unsigned jar. Removing this module (and the corresponding artifacts from the local maven repo) forces a download from the Sakai maven repo where the built artifacts ARE signed.

All works well after that.

Andrea Schmidt September 6, 2012 at 4:37 AM

Karen - since this Jira was concerning the applet problem, I believe it has been resolved. The other problems are covered in and SAM-1216.

Not being able to play back the recording in FF is covered in SAM-1787.

Andrea Schmidt September 6, 2012 at 4:24 AM

http://nightly2.sakaiproject.org:8082, Sakai Revision: 112160 (Kernel 1.4.0-SNAPSHOT)-
I am able to record in FF now, but not in IE9. The problem in IE9 is the same as for SAM-1779.

For the recording in FF, I am unable to play it back in the web page. Downloading still gives the 500 error:

Yuki Yamada September 5, 2012 at 11:19 PM

As the above-mention by Chris, it has changed to be signed in http://nightly2.sakaiproject.org:8082/portal . It was not signed before the change.

Please take a look into the build log:
http://nightly2.sakaiproject.org/logs/sakai-nightly/build-2012-08-30-12:00:01.log.txt

Hui Tsao September 5, 2012 at 6:20 PM

I see. Then this is not a code bug. This is a problem during the build process. Maybe nightly builds always have this issue? It's possible the jar is not signed in nightly build. I will shoot Sam an email.

Thanks,
Karen

Incorporated

Details

Priority

Affects versions

Components

Assignee

Reporter

Environment

http://nightly2.sakaiproject.org:8082/portal sakai/trunk on Oracle - Built: 08/28/12 08:00 - Sakai Revision: 111885 (Kernel 1.4.0-SNAPSHOT)- Server sakai-nightly.uits.iupui.edu Win7: FF9 NIGHTLY server only

Created August 28, 2012 at 6:27 AM
Updated April 17, 2018 at 8:32 AM
Resolved September 13, 2012 at 7:46 AM