The solution would he to open a PR and fix the bug I suppose. Or disable direct access. Or write your own Cloud Code function to do what you’re trying to achieve, but I believe that time would be better invested into fixing the bug.
I can try do a PR but i dont know much about the internals of Parse, can you give me a pointer as to what fixing the bug would look like
Would removing the canUseCurrentUser here fix it
linkWith(user: ParseUser, authData: AuthData, options: FullOptions) {
return user.save({ authData }, options).then(() => {
if (canUseCurrentUser) {
return DefaultController.setCurrentUser(user);
}
return user;
});
},
Should linkWith be ran only on client side to make it work then ?