Skip to content
This repository has been archived by the owner on Jan 17, 2023. It is now read-only.

"Error: response fail" error appears after trying to save a shot #2391

Closed
SoftVision-CosminMuntean opened this issue Mar 15, 2017 · 4 comments
Milestone

Comments

@SoftVision-CosminMuntean

[Affected versions]:

  • Nightly 55.0a1 (Build ID: 20170314030215)
  • Page Shot 5.2.3372

[Affected Platforms]:

  • All Windows
  • All Mac
  • All Linux

[Prerequisites]:

  • The "xpinstall.signatures.required" is set to "false" and latest Page Shot (5.2.3372) custom build is installed on a new clean profile.

[Steps to reproduce]:

  1. Open Firefox with the profile from prerequisites and navigate to any website.
  2. Click on the "Page Shot" button from the main toolbar
  3. Perform a selection on the website an save it.
  4. Observe the browser behavior.

[Expected result]:

  • The selection is successfully saved and you are redirected to the saved shot preview page.

[Actual result]:

  • "Error: Error: response fail" error is displayed and you are redirected to the preview page but the shot is not saved.

[Notes:]

  • Here is a screen shot with browser console errors:
    page shot error error

  • Here is a screen recording with the issue:
    page shot error

@ianb ianb added this to the Sprint 54.2 milestone Mar 15, 2017
@ianb
Copy link
Contributor

ianb commented Mar 15, 2017

This might just be a problem with the pageshot.dev server, we should confirm that first before looking locally.

@ghost ghost modified the milestones: Sprint 54.2, Sprint 54.3 Mar 20, 2017
@jaredhirsch
Copy link
Member

I can reproduce on dev and stage, but not locally. @relud any idea what might be going on here? Looks like 400 errors, maybe the auth header name change from x-pageshot-auth to x-screenshots-auth requires some config update on your side?

@ianb
Copy link
Contributor

ianb commented Mar 21, 2017

The server has fallen behind. deviceId removal in particular (from what I see in Sentry). I should do another update of the server, but #2436 to land.

@ianb
Copy link
Contributor

ianb commented Mar 21, 2017

I updated the dev server and it's working again

@ianb ianb closed this as completed Mar 21, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants