iOS Push Notifications guide outdated and incomplete

[kevinfoley]

The documentation for setting up push notifications on iOS has several issues:

1. The example code uses a deprecated Unity API, UnityEngine.iOS.NotificationServices.RegisterForNotifications(). New projects should use the Mobile Notifications package
2. The tutorial cannot be followed in a cross-platform application that implements Push Notifications on Android. The PlayFab documentation for Android push notifications directs us to use Firebase Cloud Messaging (FCM). If the FCM plugin is installed, on iOS it hijacks the normal notification APIs via swizzling. When we attempt to request user authorization to display notifications, we get an error "Attempting to complete future before FCM initialized."

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: 456f36b2-0825-fe0e-9681-29b95bb6d050
• Version Independent ID: 8c38a5f4-b4f1-4d4c-bc4e-467d369c3fca
• Content: Push Notification for iOS - PlayFab
• Content Source: playfab-docs/features/engagement/push-notifications/push-notifications-for-ios.md
• Service: playfab
• GitHub Login: @joannaleecy
• Microsoft Alias: joanlee

[anjekan]

we are very emergency about this ios push deprecated in unity 2022.3.53f1
If there is any possible alternative, please let me know.

because of our request, publisher started using Playfab. While positive opinions about Playfab are coming out, iOS push problem makes publisher feel not good. I hope an alternative comes out as soon as possible. Thank you.

is req.DeviceToken at below codes can be used in RegisterForIOSPushNotificationRequest?

IEnumerator RequestAuthorization()
{
var authorizationOption = AuthorizationOption.Alert | AuthorizationOption.Badge;
using (var req = new AuthorizationRequest(authorizationOption, true))
{
while (!req.IsFinished)
{
yield return null;
};

    string res = "\n RequestAuthorization:";
    res += "\n finished: " + req.IsFinished;
    res += "\n granted :  " + req.Granted;
    res += "\n error:  " + req.Error;
    res += "\n deviceToken:  " + req.DeviceToken;
    Debug.Log(res);
}

}

[gwachnitz]

How is this not yet fixed? Is there a workaround we don't know off to be able to use firebase and playfab simultaneously?

[anjekan]

Thank you for concerning about this issue. This issue is cleared with AuthorizationRequest you suggested. Thanks a lot. Take care. 2025년 2월 18일 (화) 오전 7:51, gwachnitz ***@***.***>님이 작성:

…

How is this not yet fixed? Is there a workaround we don't know off to be able to use firebase and playfab simultaneously? — Reply to this email directly, view it on GitHub <#561 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANYQXTQSGZYNSLY7HRQIVF32QJRX7AVCNFSM6AAAAABJ6YGSRWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRUGE4TAMBYGM> . You are receiving this because you commented.Message ID: ***@***.***> [image: gwachnitz]*gwachnitz* left a comment (MicrosoftDocs/playfab-docs#561) <#561 (comment)> How is this not yet fixed? Is there a workaround we don't know off to be able to use firebase and playfab simultaneously? — Reply to this email directly, view it on GitHub <#561 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANYQXTQSGZYNSLY7HRQIVF32QJRX7AVCNFSM6AAAAABJ6YGSRWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRUGE4TAMBYGM> . You are receiving this because you commented.Message ID: ***@***.***>