I searched and read google documentation about this subject,
but I don't see good text about FCM. This link have pricing about all module exception cloud messaging,
My question :
How many device can register to fire base in free plan?
How many can send message per day in free plan?
There are no documented limits on the number of devices nor on the number of messages that can be registered in Firebase Cloud Messaging. This no-limits applies equally to both projects on paid and on free plans.
Related
I am a newbie to FCM.
I have a plan to create an FCM topic that contains 100.000 subscriptions.
Then I send a notification to the topic.
My question is: will 100.000 notifications be sent out successfully?
My question is: will 100000 notifications be sent out successfully?
Yes, it will. According to the official documentation:
Firebase Cloud Messaging (FCM) provides a reliable and battery-efficient connection between your server and devices that allows you to deliver and receive messages and notifications on iOS, Android, and the web at no cost.
So first of is free of charge.
And according to the official documentation regarding topic messaging, it is said that:
Topic messaging supports unlimited subscriptions for each topic. However, FCM enforces limits in these areas:
One app instance can be subscribed to no more than 2000 topics.
If you are using batch import to subscribe app instances, each request is limited to 1000 app instances.
The frequency of new subscriptions is rate-limited per project. If you send too many subscription requests in a short period of time, FCM servers will respond with a 429 RESOURCE_EXHAUSTED ("quota exceeded") response. Retry with exponential backoff.
I'm developing an android app that relies on realtime notifications using Firebase FCM.
I know that there are many limitations for upstream messaging using FCM, but I don't know if some sort of limitations exists for downstream messages (e.g. the number of requests per day)
Thank's in advance for the replies.
The use of Firebase Cloud Messaging is free and unlimited. There is no documented limit to the number of messages you can send per day.
There are limits in place to prevent abuse of the service, but those are not documented. If you think you are hitting such a limit and have a valid use-case, reach out to Firebase support for personalized help in troubleshooting.
This question already has answers here:
Firebase Notification - send to user segment vs send to topic difference
(3 answers)
Closed 4 years ago.
The Firebase Admin documentation shows examples on how to send notifications to a specific user, or users subscribed to topics.
https://firebase.google.com/docs/cloud-messaging/admin/send-messages
In the Firebase Cloud Messaging Console though, it's possible to send a notification to all users of a specific app
That works regardless of the clients subscribing to topics.
How can I replicate that behaviour with the Firebase Admin libraries?
Based on my read of the documentation, it seems like you could automatically subscribe every new user to a topic such as "appWideAlerts" upon sign in. Then use this as your app wide notification system.
Send to a topic
Based on the publish/subscribe model, FCM topic messaging allows you
to send a message to multiple devices that have opted in to a
particular topic. You compose topic messages as needed, and FCM
handles routing and delivering the message reliably to the right
devices.
For example, users of a local weather forecasting app could opt in to
a "severe weather alerts" topic and receive notifications of storms
threatening specified areas. Users of a sports app could subscribe to
automatic updates in live game scores for their favorite teams.
Some things to keep in mind about topics:
Topic messaging supports unlimited topics and subscriptions for each app.
Topic messaging is best suited for content such as news, weather, or other publicly available information.
Topic messages are optimized for throughput rather than latency. For fast, secure delivery to single devices or small groups of
devices, target messages to registration tokens, not topics.
If you need to send messages to multiple devices per user, consider device group messaging for those use cases.
As mentioned in FCM documents, unlimited topic can be created for one Firebase application. But as the Firebase Admin SDK document: explains an error:
messaging/too-many-topics:- A registration token has been subscribed to the maximum number of topics and cannot be subscribed to any more.
I was not able to find this threshold value of maximum number of topics. Can anybody explain, what is the limit? How many topics an app instance can subscribe to in FCM?
I found the answer by running a subscription script for an app instance. After subscribing to 1999 topics, for the next subscription it started giving error: messaging/too-many-topics.
So the threshold value is 1999.
As much as the selected answer is correct, I'll like to post an absolute answer here.
Google Firebase Cloud Messaging
Some things to keep in mind about topics:
Topic messaging supports unlimited subscriptions for each topic.
However, FCM enforces limits in these areas:
One app instance can be subscribed to no more than 2000 topics.
If you are using batch import to subscribe app instances, each request is limited to 1000 app instances.
The frequency of new subscriptions is rate-limited per project. If you send too many subscription requests in a short period of time, FCM servers will respond with a 429 RESOURCE_EXHAUSTED ("quota exceeded") response. Retry with exponential backoff.
Firebase charges about $0.06 per verification. Does that mean they only charge AFTER the user successfully verifies his phone? Or do they charge everytime a user requests a code?
If you hover over the question mark, "?", in the pricing page it says
Prices are per successful verification.
On the Blaze plan, Phone Authentication provides a perpetual free
tier. The first 10K verifications are provided for free each month.
You are only charged on usage past this free allotment.
All other Firebase Auth features are free to use on all plans.