Just to help me be sure that I 100% understand, could you cross-check the following ?
What you are telling me is that if I update the user with the built-in method, it will be sending the email back to the database, which will try to overwrite it and create an error. The workaround that you are describing is just creating an object with the changes to the user instead of sending back all the properties, and the server will only try to update those changes, and leave the other fields untouched. Am I correct ?
If my understanding is correct, then this should indeed work fine, that’s great. However, for the ease of use, and in order to avoid such pitfalls, shouldn’t the built-in “Update User” method deal with this situation for guest users ?
The workaround that you are describing is just creating an object with the changes to the user instead of sending back all the properties, and the server will only try to update those changes, and leave the other fields untouched. Am I correct ?
Yes, the server will update only fields that you send.
shouldn’t the built-in “Update User” method deal with this situation for guest users?
yes it should, and I have already created an internal ticket BKNDLSS-28835 to fix the issue