Repository navigation
request.user.id fails in User afterSave #384
Copy link
Copy link
Closed
Labels
state:releasedReleased as stable versionReleased as stable versionstate:released-alphaReleased as alpha versionReleased as alpha versionstate:released-betaReleased as beta versionReleased as beta version
Description
Activity
Hi @jiawenzhang, this is a known bug, see #373
By the way, you mustn't use Parse.Cloud.useMasterKey() anymore on parse-server, but {useMasterKey : true} along with each request you want to use it one, as specified hereThat is correct. Thanks for helping with the issues!
this is not entirely fixed. if I am creating a new user, request.user.id still fails in afterSave, if it is an existing user, it works.
You could use request.object.id in _User afterSave hook meanwhile
@Tibabal that works, thanks;
🎉 This change has been released in version 7.0.0-alpha.20
- addedstate:released-alphaReleased as alpha versionReleased as alpha version
on Mar 1, 2024 🎉 This change has been released in version 6.5.0
🎉 This change has been released in version 7.0.0-beta.1
- addedstate:released-betaReleased as beta versionReleased as beta version
on Mar 19, 2024 🎉 This change has been released in version 7.0.0
- addedstate:releasedReleased as stable versionReleased as stable version
on Mar 19, 2024
Metadata
Metadata
Assignees
Labels
state:releasedReleased as stable versionReleased as stable versionstate:released-alphaReleased as alpha versionReleased as alpha versionstate:released-betaReleased as beta versionReleased as beta version
Parse.Cloud.afterSave(Parse.User, function(request) {
Parse.Cloud.useMasterKey();
var userId = request.user.id // this fails
...
})