Manuel

I was able to reproduce the issue. Would you want to open a PR with a failing test? I classified this as bug with severity S3 (normal): - Workaround is...

The issue may be related to the version of the push adapter. Did you compare the different versions of the adapter in both parse server versions?

Is the Push controller logic that different between Parse Server 4.x and 5.x? I can't remember there being any major changes.

Well investigated! Would you mind opening a PR with a filing test that reproduces this issue? > Do you have an easy way to see the changes in RestWrite.prototype.runBeforeSaveTrigger since...

You could just look at the existing tests and rewrite a test that already comes close to what you want to test. Take a look at the `/spec` folder and...

> ## ⚠️ Important change for merging PRs from Parse Server 5.0 onwards! > > We are planning to release the first beta version of Parse Server 5.0 in October...

@mstniy Do you think we could get this ready for merge?

@mstniy Could you rebase this on the alpha brach and resolve any conflicts?

@ardatan if a PR is in the works and not ready for review yet you can change its status to "draft"; I've started the CI

Do you want to test anything specific in this CI that you cannot test locally by running `npm test`?