[PAID] Firebase Cloud Messaging FCM - An Extension for Sending Push Notifications with Firebase Cloud Messaging

[ombhat327 (omkar)]

yes it works perfectly for me also… contact personally to the extension developer

[Connectappcreator (Connect App)]

I get these messages from google play now. @iamwsumit

The app has an implicit PendingIntent vulnerability. See this Google Help Center article for details.

com.sumit1334.firebasemessaging.repack.z.a

Remediation for Implicit PendingIntent Vulnerability - Google Help

[iamwsumit (Sumit Kumar)]

I am already aware about this issue. I need some time to fix it. However, you can still publish your app to play store since this issue is not mandatory to be fixed.

[Connectappcreator (Connect App)]

wonderfull, you are the best

[Connectappcreator (Connect App)]

hello, lately some users are receiving this message. extension not purchased, could you find out what could be happening?

[TrickyLabX]

i am also facing same error… even my app is live on playstore, there are too many complain about this message…

[Connectappcreator (Connect App)]

Thanks , the restriction no longer appears on google play. As for the message in the application is in testing.

[Connectappcreator (Connect App)]

it is possible to unify the two extensions, because of the kodular restrictions. I don’t intend to be premium until I think some tweaks have been fixed. @iamwsumit

[iamwsumit (Sumit Kumar)]

@Connectappcreator

it is possible to unify the two extensions,

Done. I have sent the extension on Telegram. You can delete the FCMHelper extension from your projects now but you would still need Onesignal Push Notification component in your project.

Thank You

[Connectappcreator (Connect App)]

Thank you, congratulations for extension

[TrickyLabX]

what about another platform…

[leonardo_guerrero_johh (leonardo guerrero)]

when uploading the application I get this alert

[iamwsumit (Sumit Kumar)]

Hello,
You can not use the FCM server key in your apps due to security purposes. Play store does not allow that. However, if you still want to use the server key then you have to put it as the encoded value of the key in your apps.

Like this:

The first thing you have to do is base64 encode your key here: https://www.base64encode.org/ then put the encoded key in your app to prevent detecting it from the play store.

You can decode it whenever you want to use it with this block :

This would not make your sever key protected from hackers but it would help you to publish your apps.

[leonardo_guerrero_johh (leonardo guerrero)]

1# How can I make a notification that shows all the text and not just half, since entering more than 45 characters does not show the rest

2#How can I make clicking on the notification do an action since I have tried everything and nothing

[Connectappcreator (Connect App)]

Hi, is this extension out of order? I ask because onesignal is outdated and causing problem with “android:exported” .
What would be the new option for this extension?

[Taifun]

@Connectappcreator

onesignal is outdated and causing problem with “android:exported” .

try

Onesignal Push : Onesignal works with Android 12 & 13

Onesignal Push Hello everyone, This is new version of OnesignalFix that allow you to receive notifications in android 12 and 13 without any crash and with full onesignal report. After the publication of this extension, older Onesignal Fix will be discontinued and the sponsor amount also be removed from there. You can buy this extension directly now and you would not need the older Onesignal Fix. You can remove that from your project and use this one. This extension offers you following things …

Taifun

[iamwsumit (Sumit Kumar)]

Firebase Cloud Messaging v1.5.0 [Most Stable]

This is the most stable version of the FCM for the latest android devices and target SDK 32.

Added

• Vibration property has been added to make enable vibration when the device is in vibrate mode.

  

• Webhook events have been added to send HTTP post requests to your API in the background.

• Added a block for asking notification permission for showing notifications in android 13.

  

Changes

• Firebase SDKs changes, the extension uses the latest (23.1.0) FCM’s SDK to gain more stability.
• Push Notification component is not required anymore, extension works independently.
• FCM helper extension is added again due to some library compilation conditions.
• Same files work for all distros now, no confusion about which file to use in the specific builder.
• Reduction in the APK’s size now, since the push notification component will be removed.

Bug Fixed

• Small Icon property has been fixed.
• Custom sound not playing has been fixed.
• Notification priority bug has been fixed.
• Notification from the console crashing the APK is now fixed.

Webhooks

This is a little guide about enabling webhooks.

You can use RegisterWebhook for enabling the webhook on events. You can pass user info that will be sent along with notification data (if the includeNotificationData is true) to the given URL. The above block will send a POST request to the given URL with the userParam along with notification data (received from notification) whenever the user dismisses the notification.

Currently, there are two events available in the extension,

To unregister or remove the webhook, you can use this block

Screenshot

Notification now works in all distros (tested in AI2, Kodular and Niotron).

Note:- If you send a message from the console while the app is in the background then a small icon, custom sounds, and notification events with webhooks would not work. You can always send messages with API including notifications in data tags.

Downloads

I will be releasing this version soon once I finish my testing on this extension.

If you have installed the AI2 Store , then you will be notified whenever the update will be released.

---

Thank you
Sumit

[Silvio_Tadeu]

Hi, I installed the extension including the FCMHelper, set the proper ids settings for the Firebase ids and when compiling for testing in apk format, the application starts the Splash screen of screen1 and when it goes to start screen2, the application closes app… My blocks look like this: Screenshot by Lightshot. How should I go about solving this problem?
Thanks.

Warning: The email used for the Firebase account is not the same email used for the purchase. I don’t know if this has any effect.

[iamwsumit (Sumit Kumar)]

Hello,
In your blocks, you have used the initialize block before setting the firebase details so kindly move the initialize block to the bottom or set the firebase details in designer properties.

@Silvio_Tadeu

when it goes to start screen2, the application closes app

There could be any other reasons for the crash, please PM me with more details about this.

Thanks

[Silvio_Tadeu]

Hi Sumit1334, thanks for your answer, I put Firebase data in Designer and extension initialization block in Screen2. The behavior of the application is to start at the splash screen of Screen1 and then close the application. Unfortunately I can’t give you more details, as there is no error message. Just pointing out that the app opens normally without the extension.
Sumit1334, is it possible for me to send you the .aia file so you can look at it and maybe find out where the fault is?
Thanks.