1. Add DEV/PROD info when registering to push the server
Add information if the app is built with production or development APNS configuration. This will enable our push server to send the push to the right APNS server. This also removed friction when testing the app in development and test flight against the same environment
Push improvements
1. Add DEV/PROD info when registering to push the server
Add information if the app is built with production or development APNS configuration. This will enable our push server to send the push to the right APNS server. This also removed friction when testing the app in development and test flight against the same environment
Related backend issues: https://github.com/wultra/enrollment-server/issues/1136 https://github.com/wultra/powerauth-push-server/issues/906
2. Change the iOS platform to APNS + enable FCM (Firebase Cloud Messaging) notifications
This is a broader change on our backend when we move from targeting the OS to targeting the push platform.
Also, we should support FCM on iOS as it is a platform that is often used in modern iOS applications.
Related backend PRs: https://github.com/wultra/powerauth-push-server/issues/904 https://github.com/wultra/powerauth-cloud/issues/986 https://github.com/wultra/enrollment-server/issues/1134
Possible routes: