Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Errors in Firefox browser console when recording #397

Closed
Reginhar opened this issue Aug 2, 2017 · 3 comments
Closed

Errors in Firefox browser console when recording #397

Reginhar opened this issue Aug 2, 2017 · 3 comments

Comments

@Reginhar
Copy link
Contributor

Reginhar commented Aug 2, 2017

Browsers

  • Firefox 54.0.1 (64-bit)
  • Firefox 55.0b13 (64-bit)

Does NOT occur in Chrome 59.0.3071.115 (Official Build) (64-bit)

Operating systems

  • macOS 10.12.6

Description

While recording in Firefox, some errors pop up in the console. Everything on the pages seems to be working fine. In the Network tab of the developer tools, it looks like the recordings do get uploaded.

When navigating to https://voice.mozilla.org/record, I get the following error 3 times: (link points towards https://voice.mozilla.org/record)
Invalid URI. Load of media resource failed. record

When clicking 'submit' after recording three sentences: (links are: upload:1:1, record, demographic:1:1)

XML Parsing Error: syntax error
Location: https://voice.mozilla.org/upload/
Line Number 1, Column 1:  upload:1:1

Invalid URI. Load of media resource  failed. record

XML Parsing Error: syntax error
Location: https://voice.mozilla.org/upload/
Line Number 1, Column 1:  upload:1:1

Invalid URI. Load of media resource  failed.  record

XML Parsing Error: syntax error
Location: https://voice.mozilla.org/upload/
Line Number 1, Column 1:  upload:1:1

XML Parsing Error: syntax error
Location: https://voice.mozilla.org/upload/demographic/
Line Number 1, Column 1:  demographic:1:1

Is there any way for me to debug this without setting up an Amazon S3 account for testing? If not, how do I set up one? I noticed that they have some free plans, which one would I need? If setting up a local test server is all too much of a hassle then that's fine, I'll work on other issues.

@mikehenrty
Copy link
Member

I don't think you need an s3 account to test and debug this. The problem is not with s3, but the fact that the response is being interpreted by the browser as HTML, and instead we are sending text. I think we just need to set the right response header in nodejs (here for instance).

If you would like to set up s3 for local testing, I do believe you can use a free plan, and then add aws creds like this:
http://docs.aws.amazon.com/AWSImportExport/latest/DG/SaveCredentials.html

@Reginhar
Copy link
Contributor Author

Reginhar commented Aug 8, 2017

The XML errors are fixed by #411, but the Invalid URI errors still need to be fixed

@mikehenrty
Copy link
Member

Looks like @Omniscimus fixed everything here! Thank you!!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants