Скачать или смотреть How to Retrieve Firebase FCM Token Outside the Swift AppDelegate

Learn how to manage Firebase FCM tokens in your SwiftUI app without app restarts, ensuring seamless user experiences.
---
This video is based on the question https://stackoverflow.com/q/65918503/ asked by the user 'Nathan' ( https://stackoverflow.com/u/12647189/ ) and on the answer https://stackoverflow.com/a/65918723/ provided by the user 'Claudio' ( https://stackoverflow.com/u/2217859/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: How to get Firebase FCM token outside the Swift AppDelegate

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
How to Retrieve Firebase FCM Token Outside the Swift AppDelegate

If you are a developer using Firebase Cloud Messaging (FCM) in your SwiftUI application, you might have faced a common issue: the FCM token is only accessible after the app is restarted. This can lead to a frustrating experience for users who need their tokens to be uploaded immediately upon registration. In this guide, we will explore this issue and provide you with a straightforward solution to access the FCM token outside the AppDelegate.

The Problem

In a typical scenario, after a user registers with your app, you want to send their FCM token to your database. However, if this token is only available after the app has restarted, the users face a delay in functionality. This is what happens:

After registration, you attempt to access the FCM token using:

[[See Video to Reveal this Text or Code Snippet]]

But instead of receiving the token, you get an empty string.

Users have to restart the app for the AppDelegate's messaging function to run again, which is not an ideal situation. You want the FCM token to be sent to your database profile immediately after registration.

The Solution

To effectively solve this problem, you can store the FCM token as a static property in your AppDelegate. This allows you to access it anytime during the user session. Here’s a step-by-step breakdown of how to implement this solution:

Step 1: Modify Your AppDelegate

Add a Static Property: In your AppDelegate, add a static property to hold the FCM token.

[[See Video to Reveal this Text or Code Snippet]]

Store the Token: As soon as you receive the FCM token, assign it to the static property you created.

Step 2: Access the Token

Now, wherever you need to use the FCM token in your code, simply access it through the static property:

[[See Video to Reveal this Text or Code Snippet]]

Why This Works

By storing the FCM token in a static property of your AppDelegate, you ensure it persists for the life of your app session. Even if the user transitions to the main screen after registration, your app can still retrieve the stored token without requiring a restart.

This approach promotes a better user experience by allowing immediate functionality and engagement with your app’s features.

Conclusion

In summary, managing the Firebase FCM token effectively is crucial for a smooth user experience in your SwiftUI app. By following the solution outlined in this post, you can ensure that the FCM token is ready to be sent to your database immediately after user registration. No more app restarts, no more empty strings—just seamless communication with Firebase Cloud Messaging.

Now, with this straightforward approach, you can improve your app’s functionality and user satisfaction significantly. Happy coding!