I think there is no way to match any user subscription associated because the "latest_receipt" and the "original_transaction_id" fields that we can use to identify the subscription are inside the "unified_receipt". I hope it can be solved soon.

I added more notification examples in other answer.

Yes, but what I am trying to say is that the problem with the notifications without 'unified_receipt' object is that we cannot access 'latest_receipt' or 'original_transaction_id' because they are inside the 'unified_receipt'. So we have no way to match this notification to any subscription in our database. I'll provide more notification examples affected by this bug into a separated answer.