AfterLogin Event Handler Populating oAuthIdentities Field Eventually Causing Request entity too large error

Server Code
1

Backendless Version 6.3 Online

Client SDK - JS

Application ID - 2A0EB9A5-1BF6-5C77-FF0C-566B648F7600

Expected Behavior

  1. AfterLogin event is called
  2. Update a field of the logged in user
  3. DONT update the oAuthIdentities field

Actual Behavior

  1. AfterLogin event is called
  2. Update a field of the logged in user
  3. oAuthIdentities field is updated to {"rawJsonString": null}
  4. On each log in the field is appended with more rawJsonString values, for example after 4 logins it looks like this: {"rawJsonString":"{\"rawJsonString\": \"{\\\"rawJsonString\\\": \\\"{\\\\\\\"rawJsonString\\\\\\\": null}\\\"}\"}"}
  5. This eventually causes the API to return a Request entity too large, status code 413 error.

Reproducible Test Case

Call Backendless.UserService.update(user) from inside an afterLogin JS server event.

1 Like
2

Hi @mudasar-javed !

I have created internal ticket BKNDLSS-25028 for this problem. We will provide fix as soon as possible. I or my colleague will contant you when fix will be released.

Sorry for inconvenience.

Regards, Andriy

2 Likes
3

We are seeing exactly the same issue with both of our apps - updating any field by the logged-in user causes the same cascade of {“rawJsonString”: null} values in oAuthIdentities field. In our case, it is with the iOS SDK.

Thanks in advance!

Regards,
Rick