LinkedIn
Twitter
AppSheet uses Firebase Cloud Messaging (FCM) to send notifications to branded mobile apps. FCM is migrating to a new protocol that will take effect on June 21, 2024. For more information, see the Firebase FAQ.
As announced previously, app creators who send notifications through a branded mobile app need to make the configuration changes described below. Unbranded apps (apps accessed through the Appsheet general app on Play/iOS) donโt need to take any action.
Configuration changes can be made starting May 1st and must be completed before the June 21st deadline.
To support mobile notification sending functionality for branded apps, do one of the following:
If you've already branded your app, there is no need to rebrand your app and you can follow the steps described in the following article:
If you are branding your app for the first time, follow the steps described in the following articles:
Important Deadlines:
June 21, 2024: Final deadline for these action items. Notifications on branded apps that did not follow the above instructions will no longer work due to Firebase Cloud Messaging (FCM) updates.
If you are unable to complete the action items by June 21, you can request an extension of up to 3 months by filling out the form here.
If granted, you will be able to continue sending notifications through the legacy Cloud Messaging HTTP protocol for the approved extension of time. However, extensions cannot be guaranteed, so we recommended taking action as early as possible.
For โProject number you want extension for (use 0 for batch request)โ, enter the Project number for the Firebase project you originally used to brand your app. To access the Firebase project number, in the Firebase Console, navigate to the Project settings and click Manage service account permission, as shown below:
This opens the Google Cloud console where you can copy the Project number:
For โAPI/SDK that you want extension forโ, choose โlegacy http protocolโ.
