Experiencing a Login Issue #59
-
|
This is my Parse initialisation code: let url = { … }; let appID = { … }; let clKey = { … }; let liveQueryURL = { … }
let credentials = ParseConfiguration(
applicationId: appID,
clientKey: clKey,
serverURL: url,
liveQueryServerURL: liveQueryURL
)
initialize(configuration: credentials)This is working and I’m able to connect to the database, query tables and save objects just fine. User.login(username: uName, password: pw) { result in
switch result {
case .failure(let error): print(error.localizedDescription)
case .success(let user): /* DO STUFF */ { … }
}
}I get the following error: ParseError code=-1 error=Error decoding parse-server response: <NSHTTPURLResponse: 0x280c2e4e0> { URL: <redactedURL>/login } { Status Code: 504, Headers {
"Cache-Control" = (
"no-cache"
);
Connection = (
close
);
"Content-Type" = (
"text/html"
);
} } with error: dataCorrupted(Swift.DecodingError.Context(codingPath: [], debugDescription: "The given data was not valid JSON.", underlyingError: Optional(Error Domain=NSCocoaErrorDomain Code=3840 "Invalid value around line 1, column 0." UserInfo={NSDebugDescription=Invalid value around line 1, column 0., NSJSONSerializationErrorIndex=0}))) Format: Optional("<html><body><h1>504 Gateway Time-out</h1>\nThe server didn\'t respond in time.\n</body></html>\n")I know the username/password credentials i’m using to log in are accurate. ParseServerI use a BaaS known as SashiDo, and am currently on ParseServer Version v2.3.3 (I have the option to go up to v3.6.0, but haven’t gotten around to it yet.) Questions
Thank you for any help you can provide! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Hi @Project-Academy, I discuss using older servers here: #29 (comment)
Yes, see here: https://community.parseplatform.org/t/parse-swift-minimum-parse-server-version/2419/4?u=cbaker6
See issues with GET: parse-community/Parse-SDK-JS#1283 (comment) I recommend using a service that allows you to take advantage of the latest servers (Which is currently on Parse Server 6) or self host. I have a self hosting example using Heroku here: https://github.com/netreconlab/parse-hipaa/tree/snapcat#deployment |
Beta Was this translation helpful? Give feedback.
-
|
Ah yep, I personally tested this on later versions (as low as v2.8.4) and there’s no issues with login. Using .POST to login was added in v2.6.4 according to the release logs. Unfortunately our organisation doesn't have the capacity/ability to self host but we’ll be looking to make sure the BaaS we go with offers up-to-date Parse Servers. Thank you for being patient with my adoption of ParseSwift! |
Beta Was this translation helpful? Give feedback.
Hi @Project-Academy, I discuss using older servers here: #29 (comment)
Yes, see here: https://community.parseplatform.org/t/parse-swift-minimum-parse-server-version/2419/4?u=cbaker6
See issues with GET: parse-community/Parse-SDK-JS#1283 (comment)
I recommend using a service that allows you to take advantage of the latest servers (Which is currently on Parse Server 6) or self host. I have a self hosting example using Heroku here: https://…