Are you using any methods to mitigate the issue of the users no longer using the app, or somehow the token has changed, either due to a device event, or a new device, etc.? No. We are not using any specific methods as described above.

I am a developer and this error is coming for my Application in Testfligh which we have submitted on Feb 21, 2022. In some devices only this error is coming and if we install an older version and try the new version as an update it will work. Also, post this step, fresh installation will also work in the same device. So the question is if I release the same version to Customers, whether they will be affected? Thanks, Abin

Any fixes to this Crash?