parse-server: Cloud code not working after migration

After migration we thought we had everything up and running but then realized that we were receiving erroneous responses from the server (AWS). We are sending latitude and longitude as params when we call PFCloud in iOS, like so:

NSDictionary *params = @{
                       @"latitude" : [NSNumber numberWithDouble:(double)self.location.coordinate.latitude],
                       @"longitude" : [NSNumber numberWithDouble:(double)self.location.coordinate.longitude]
                             };
[PFCloud callFunctionInBackground:@"myQuery" withParameters:params block:^(NSArray *response, NSError *error) {
...
}];

and then in cloud code we access it like so:

var latitude = request.params.latitude;
var longitude = request.params.longitude;

This worked perfectly on parse.com but since the move to AWS and parse server, it doesn’t work. I wrapped each request in parseFloat() thinking it might fix it but it didn’t.

It works again if I hardcode a latitude and longitude in the cloud code. So what is the issue with sending this a params to the cloud code with the hosted parse server?

Expected Results

The script should return a query limited by latitude and longitude.

Actual Outcome

The script disregards lat and long and returns everything

Environment Setup

• Server
  • parse-server version: latest as of last month
  • Localhost or remote server? (AWS, Heroku, Azure, Digital Ocean, etc): AWS
• Database
  • MongoDB version: latest as of last month
  • Localhost or remote server? (AWS, mLab, ObjectRocket, Digital Ocean, etc): mLab