G.2 Init FCM

Initialize Firebase FCM

firebaseMessaging.ane can be initialized similar to other Firebase child ANEs. simply by calling the FCM.init(); method. However, considering that FCM is highly dependent on Google Play Services, you need to check for Google Play Services APK on Android (the iOS side doesn't need this check) before you init the FCM ANE. You can do so, like below after you initialized the firebaseCore.ane of course.

if (Firebase.os == Firebase.ANDROID) Firebase.checkGoogleAvailability(onCheckResult);
else onCheckResult(Firebase.SUCCESS);

function onCheckResult($result:int):void
{
	switch($result)
	{
		case Firebase.SUCCESS:
			
			trace("checkGoogleAvailability result = SUCCESS");
			
			// now you can use FCM
			initFCM();
			
		break;
		case Firebase.SERVICE_MISSING:
			
			trace("checkGoogleAvailability result = SERVICE_MISSING");
			
		break;
		case Firebase.SERVICE_VERSION_UPDATE_REQUIRED:
			
			trace("checkGoogleAvailability result = SERVICE_VERSION_UPDATE_REQUIRED");
			
		break;
		case Firebase.SERVICE_UPDATING:
			
			trace("checkGoogleAvailability result = SERVICE_UPDATING");
			
		break;
		case Firebase.SERVICE_DISABLED:
			
			trace("checkGoogleAvailability result = SERVICE_DISABLED");
			
		break;
		case Firebase.SERVICE_INVALID:
			
			trace("checkGoogleAvailability result = SERVICE_INVALID");
			
		break;
	}
}

After you made sure that Google Services are available, simply call FCM.init(); and the FCM service will start in your app. As soon as this method is called for the first time on the iOS side, a dialog will be presented to you asking for user permissions to send push notifications.

Access the device registration token

On initial startup of your app, the FCM SDK generates a registration token for the client app instance. If you want to target single devices or create device groups, you'll need to access this token.

FCM.getInstanceId(onTokenReceived);

function onTokenReceived($token:String, $error:String):void
{
	if($error)
	{
		trace("onTokenReceived error: " + $error);
	}
				
	if($token)
	{
		trace("token: " + $token);
	}
}

The registration token may change when:

• The app deletes Instance ID
• The app is restored on a new device
• The user uninstalls/reinstall the app
• The user clears app data.

To monitor the token generation, you need to listen to FcmEvents.TOKEN_REFRESH event. This event fires whenever a new token is generated, so calling getToken in its context ensures that you are accessing a current, available registration token. Make sure you have added the required services/activities to your manifest.

FCM.listener.addEventListener(FcmEvents.TOKEN_REFRESH, onTokenRefresh);

function onTokenRefresh(e:FcmEvents):void
{
	// If you want to send messages to this application instance or
    // manage this apps subscriptions on the server side, send the
    // Instance ID token to your app server.
	trace("onTokenRefresh = " + e.token);
}

Revoke the token

Incase you need to revoke the token or generate a new one, you need to have access to the FirebaseInstanceId API. Please read the information on this page to know how you can manage the Firebase iid API.