parse-community / parse-community/parse-server

[PFUser currentUser].email returns nil

Open
#10,456 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
21.4k
Forks
4.8k
Avg merge
7h 45m
Merged PRs (30d)
11

Description

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with Parse Server 9.9.0, the iOS SDK, and MongoDB, then compare the result with Parse Server 9.6.1. Trace how the current user is returned and how its email and username fields are exposed; done means both fields match the valid _User database entries after the upgrade.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios, javascript, mongodb
Domain
api, backend, database
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.