[PFUser currentUser].email returns nil

[ovusense]

Issue Description

Since upgrading to parse-server 9.9.0 (from 9.6.1) a call to [PFUser currentUser].email returns nil. This seems like a breaking change, since the _User table still has a valid email entry.

Steps to reproduce

Run Parse Server 9.9.0, and an iOS app with a valid user account. Once signed in try and access the .email object for the [PFUser currentUser] object and also the .username object.

Actual Outcome

Since upgrading just the Parse Server to 9.9.0 from 9.6.1, (and making no changes to the iOS code), [PFUser currentUser].email returns nil.

Expected Outcome

[PFUser currentUser].email should return the entry in the database.

Environment

iOS 18.7
parse_sdk_ios_osx : 6.1.1
bolts-objc : 1.10.0

Server

• Parse Server version: 9.9.0
• Operating system: iOS 18.7
• Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): AWS

Database

• System (MongoDB or Postgres): MongoDB
• Database version: MongoDB 8.0
• Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): MongoDB Atlas

Client

• SDK (iOS, Android, JavaScript, PHP, Unity, etc): iOS
• SDK version: iOS 18.7

Logs

n/a

[parse-github-assistant]

🚀 Thanks for opening this issue!

[ovusense]

Having regressed my server through different versions, it seems this bug was introduced between 9.7.0, (which provides [PFUser currentUser].email), and 9.8.0, which does not. Further tests reveal the bug occurs between version 9.8.0-alpha8 and 9.8.0-alpha9

[SteffenKeller]

I see the same issue in version 9.9.0. A user cannot retrieve their own email with protectedFieldsOwnerExempt: false despite the email not being in protectedFields. It works with setting protectedFieldsOwnerExempt: true in the server config.

Looks like the same issue as described in the 9.6.1 release notes.