You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm setting all count clps to {} for all my classes since we don't need it. On the _Installation Class, are there any side effects on parse-server's side? Like for example notifications.
Are there any side effects on parse-server if I set all clp to {} on the _Session Class
The text was updated successfully, but these errors were encountered:
You may have side effects if you set CLP’s on sessions, while I’m not sure which, they are secured by ACL’s and additional checks.
On installations, you need clients to be able to write to installations for push to be working properly. Find operations are disabled. See the docs for more info, in the security sections.
Also, we can’t guarantee thAt your CLP’s won’t interfere with what you expect in the SDK’s, if you prevent installation / session creation, from CLP, there’s a high chance logins, signups and push’s won’t be functional.
I'm setting all count clps to {} for all my classes since we don't need it. On the _Installation Class, are there any side effects on parse-server's side? Like for example notifications.
Are there any side effects on parse-server if I set all clp to {} on the _Session Class
The text was updated successfully, but these errors were encountered: