request.user on cloud code is undefined with iOS 10

[iamraafay]

We just updated our iOS codebase to iOS 10 as base SDK with Xcode 8 with Parse iOS SDK version '1.13.0' and Server version 2.2.17.

Is this issue with parse-server or iOS SDK needs an update with the iOS 10?

[idefen1]

Apple rejected my latest app, says not compatible with IPv6 wifi? Please help =*(

[joeyslack]

@idefen1 Just happened to me. Hosted on Heroku, and it might be an issue with them. Where are you hosted?

[hramos]

Hey, thanks for reporting this issue.

Can you please add all the info specified in the template? This is necessary for people to be able to understand and reproduce the issue being reported.

[iamraafay]

Issue Description

We just updated our iOS codebase to iOS 10 as base SDK with Xcode 8 with Parse iOS SDK version '1.14.2' and Server version 2.2.17. We observed that the cloud functions aren't having the user object in the request payload on the server which is being made by the iOS 10 compatible app.

Steps to reproduce

• Update your Mac with the latest Xcode 8.
• Then update iOS app codebase to Swift 2.3.
• If your Parse SDK isn't 1.14.2, then please update that as well.
• Now run the app and see your cloud functions on the server has user object missing.

Expected Results

These cloud functions should have the original payload with the user objects invoke in them.

Actual Outcome

There's no user object in the request payload.

Environment Setup

Server

parse-server version (Be specific! Don't say 'latest'.) : v2.2.17
Operating System: Heroku (cedar)
Hardware: Heroku
Localhost or remote server? (AWS, Heroku, Azure, Digital Ocean, etc): Heroic
Database

MongoDB version: 3.0.12 (MMAPv1)
Storage engine: MMAPv1
Hardware: mLab
Localhost or remote server? (AWS, mLab, ObjectRocket, Digital Ocean, etc): mLab

Logs/Trace

You can turn on additional logging by configuring VERBOSE=1 in your environment.

[hramos]

Are there any logs? e.g. an example of what the cloud function logs when it is called by an iOS 9 device vs an iOS 10 device? In any case, it sounds like this may be a SDK issue and not a Parse Server issue. You may want to open the issue against the iOS SDK's repo if you can reproduce this issue.