SebC.

Here's what is in the DB for the last try ``` { "_id" : "YsXd23ED", "pushTime" : "2019-03-09T12:24:30.138Z", "query" : "{\"deviceToken\":{\"$exists\":true}}", "payload" : "{ \"alert-fr\":{\"title\":\"XXXX\",\"body\":\"XXXX\"}, \"alert\":{\"title\":\"XXXX\",\"body\":\"XXXX\"}, \"category\":\"update\", \"channel\":\"remote_notifications\", \"campaign\":\"marketing\" \"}",...

Thanks, I haven't noticed that one, I'll give it a try (direct access has failed me before for cloud functions, so I haven't try for push yet)

I'll try to investigate too. If I remember well, a lot of beforeFind or beforeSave were appearing in the log, and I think it was about _User class, but I'm...

After some tests, `PARSE_SERVER_ENABLE_EXPERIMENTAL_DIRECT_ACCESS` seems to decrease the load of the server. But: - with `content-available:1` and no payload, the push is sent quite fast (it is still marked as...

And with VERBOSE, I can clearly see: `MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 connect listeners added. Use emitter.setMaxListeners() to increase limit` I have the exact same error with batchSize...

I also noticed this weird error from node-apn: https://github.com/node-apn/node-apn/issues/653#issue-439213015

If it helps, I keep testing things: - it works much better with android devices than ios devices - removing the database maxTimeMS on parse server helps - removing invalid...

@davimacedo I tried with a simple "alert" payload (not localized) and I do have the exact same thing. - It's not 1. as I run my test on a standalone...

Same here, as reported here: https://developer.apple.com/forums/thread/693623 Due to lock on the realm file in the shared container Just as in the old #6671

We do have AppClips while using requestAlwaysAuthorization in the main App @mtrezza so I don’t think there’s any bug… Or at least we need more precision on the real bug.