Damian Van de Kauter

> There is a pending PR to refactor the error messages. Maybe it helps to merge that first? I just looked into the open PR, but it doesn't seem to...

> * Instead of adding a new param objectId to the error we could simply mention the objectId in the error message; it wouldn't be automatically parsable but for manual...

> The other question is whether we should add object data to logs. That never sounds like a good idea, because an object ID is then exposed in the logs....

> A workaround could be to use `enableExpressErrorHander` with: > > ```js > app.use((err, req, res, next) => { > let httpStatus; > switch (err.code) { > case Parse.Error.INTERNAL_SERVER_ERROR: >...

Any news on this topic?

> Problem is, its currently missing a lot of features and because they renamed a bunch of methods new users may struggle to implement it until documentation is updated accordingly....

> This will fail because IIRC Parse-Swift doesn't use PFObject. I am not saying ParseSwift is difficult to implement, in fact its easier given SPM. However renaming methods etc make...

I'll need some time to invest this more, but I don't directly see what I could be doing wrong with my tasks.

@cbaker6 Is it possible it could have something to do with the fact that ParseSwift is not truly async, but still uses `completionBlocks`? I came across this issue: https://developer.apple.com/forums/thread/682446 where...

> How is ParseSwift not truly async? Cause the async code is all converted with `withCheckedThrowingContinuation` but I don't know how that works exactly. > If you need to look...