Skip to content

[PFFile loadInBackground] leads to Parse Error Code 1 #536

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

Closed
dtaitz opened this issue Nov 10, 2015 · 5 comments
Closed

[PFFile loadInBackground] leads to Parse Error Code 1 #536

dtaitz opened this issue Nov 10, 2015 · 5 comments

Comments

@dtaitz
Copy link

dtaitz commented Nov 10, 2015

Hello,

I use PFFile throughout my app. Starting this morning, I started to receive the following error each and every time I called [PFFile loadInBackground];

Response status code was unacceptable: 400 (Code: 1, Version: 1.9.1)

This happens regardless of what iOS version I test. I am currently using Parse 1.9.1.

Please let me know what I can do to help resolve this issue.

Best,

David

@nlutsenko
Copy link
Contributor

This sounds very weird, since 400 probably would come from S3/CloudFront, not Parse API server.
Could you extract the url from the file and trying to access it in your browser?

@parse-github-bot
Copy link

Thank you for your feedback. We prioritize issues that have clear and concise repro steps. Please see our Bug Reporting Guidelines about what information should be added to this issue.

Please try the latest SDK. Our release notes have details about what issues were fixed in each release.

In addition, you might find the following resources helpful:

@dtaitz
Copy link
Author

dtaitz commented Nov 12, 2015

@nlutsenko here is the response I get with the file path:

<NSHTTPURLResponse: 0x12d847aa0> { URL: https://files.parsetfss.com/7eed937a-5c08-4bab-be98-c6208873fd24/tfss-e62126df-9023-4b2d-bc2b-88f341564f0c-hjcuGN7p6W-profile.png } { status code: 400, headers {

    Connection = close;

    "Content-Length" = 551;

    "Content-Type" = "text/html";

    Date = "Tue, 10 Nov 2015 22:20:03 GMT";

    Server = CloudFront;

    Via = "1.1 86ecaaad1bf09697690720df2c709cb6.cloudfront.net (CloudFront)";

    "X-Amz-Cf-Id" = "k8NYzMpkTAvDxkTYIfX2ZEmI8-GfwipM3rAJdsw9v3qU4f-mLTkxRw==";

    "X-Cache" = "Error from cloudfront";

} }

On Wed, Nov 11, 2015 at 8:29 PM, Parse Community Bot
[email protected] wrote:

Thank you for your feedback. We prioritize issues that have clear and concise repro steps. Please see our Bug Reporting Guidelines about what information should be added to this issue.

Please try the latest SDK. Our release notes have details about what issues were fixed in each release.

In addition, you might find the following resources helpful:

Reply to this email directly or view it on GitHub:
#536 (comment)

@nlutsenko
Copy link
Contributor

Since this error comes from CloudFront - this is outside of the client code.
Can you file a backend issue at https://parse.com/help, as we are still using FB Bug Tool for tracking those.

@parse-github-bot
Copy link

Thank you for your feedback. This repository only contains code for the SDK, so we only handle SDK issues here.

Your issue seems to be a backend issue. Our backend issues are tracked through https://www.parse.com/help, where you can provide more information about the exact app where this is happening and attach confidential data for reproducing the issue. Could you please file a bug there?

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

3 participants