Android Question Strongly consider using FLAG_IMMUTABLE, only use FLAG_MUTABLE if some functionality depends on the PendingIntent being mutable, e.g. if it needs to be

D

Declan

Well-Known Member
Licensed User
Longtime User
I have a B4X app that receives Firebase Notifications.
When the app is running, I receive FB Notifications with no problem.
However, if the app is running in the Background, I receive the following error:
B4X: 
** Activity (splash) Pause event (activity is not paused). **
B4XPage_Background
** Activity (splash) Resume **
B4XPage_Foreground
** Activity (splash) Pause event (activity is not paused). **
B4XPage_Background
java.lang.IllegalArgumentException: com.ecowatch.AVPsecure: Targeting S+ (version 31 and above) requires that one of FLAG_IMMUTABLE or FLAG_MUTABLE be specified when creating a PendingIntent.
Strongly consider using FLAG_IMMUTABLE, only use FLAG_MUTABLE if some functionality depends on the PendingIntent being mutable, e.g. if it needs to be used with inline replies or bubbles.
    at android.app.PendingIntent.checkFlags(PendingIntent.java:401)
    at android.app.PendingIntent.getActivityAsUser(PendingIntent.java:484)
    at android.app.PendingIntent.getActivity(PendingIntent.java:470)
    at android.app.PendingIntent.getActivity(PendingIntent.java:434)
    at com.google.firebase.messaging.CommonNotificationBuilder.createContentIntent(com.google.firebase:firebase-messaging@@20.3.0:125)
    at com.google.firebase.messaging.CommonNotificationBuilder.createNotificationInfo(com.google.firebase:firebase-messaging@@20.3.0:27)
    at com.google.firebase.messaging.CommonNotificationBuilder.createNotificationInfo(com.google.firebase:firebase-messaging@@20.3.0:9)
    at com.google.firebase.messaging.DisplayNotification.handleNotification(com.google.firebase:firebase-messaging@@20.3.0:27)
    at com.google.firebase.messaging.FirebaseMessagingService.dispatchMessage(com.google.firebase:firebase-messaging@@20.3.0:65)
    at com.google.firebase.messaging.FirebaseMessagingService.passMessageIntentToSdk(com.google.firebase:firebase-messaging@@20.3.0:44)
    at com.google.firebase.messaging.FirebaseMessagingService.handleMessageIntent(com.google.firebase:firebase-messaging@@20.3.0:27)
    at com.google.firebase.messaging.FirebaseMessagingService.handleIntent(com.google.firebase:firebase-messaging@@20.3.0:17)
    at com.google.firebase.messaging.EnhancedIntentService.lambda$processIntent$0$EnhancedIntentService(com.google.firebase:firebase-messaging@@20.3.0:43)
    at com.google.firebase.messaging.EnhancedIntentService$$Lambda$0.run(Unknown Source:6)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
    at com.google.android.gms.common.util.concurrent.zza.run(com.google.android.gms:play-services-basement@@17.6.0:2)
    at java.lang.Thread.run(Thread.java:1012)
I don't understand the use of "FLAG_IMMUTABLE" / "FLAG_MUTABLE" or where is is required/set in the code.
 
Sort by date Sort by votes

DonManfred

Expert
Licensed User
Longtime User
Declan said:
However, if the app is running in the Background, I receive the following error
Click to expand...
are you sure to use B4A 13 with an updated SDK?
Did you change FirebaseMessaging Service to a FilebaseMessaging Receiver?

Check the Tutorial

[B4X] Firebase Push Notifications 2023+

Google has deprecated the previous method of sending push notifications. It will stop working on June 2024. If you have an already working solution then you only need to update the B4J side. Do make sure that you switched from the service to a receiver on B4A. The new API is (confusingly) named...
www.b4x.com
 
Upvote 0
D

Declan

Well-Known Member
Licensed User
Longtime User
DonManfred said:
are you sure to use B4A 13 with an updated SDK?
Click to expand...
Yes, B4A 13.00
I have a number of apps that use the FB notifications and it is my understanding that nothing on the B4A had to be changed, only on the B4J side that pushes the FB notification.
DonManfred said:
Check the Tutorial
Click to expand...
Yes, all requirement have been met.
Notifications are received when the app is running, but not when app is in the background.
 
Upvote 0

aeric

Expert
Licensed User
Longtime User
From the error, I guess this problem only happened in Android 12+ (API 31).
 
Last edited:
Upvote 0

aeric

Expert
Licensed User
Longtime User

Error receiving message firebaseMessaging Targeting S+

I made changes as DonManfred once guided me by adding the receiver to receive notification. and in parts it worked. When the app is open I am able to receive the message normally now. But if I close and send the message it gives me the following error: java.lang.IllegalArgumentException...
www.b4x.com
 
Last edited:
Upvote 0
You must log in or register to reply here.

Similar Threads

  • Question
Android Question Strongly consider using FLAG_IMMUTABLE, only use FLAG_MUTABLE if some functionality depends on the PendingIntent being mutable, e.g. if it needs to be
Replies
6
Views
782
victormedranop
A
  • Question
Android Question Targeting S+ (version 31 and above) requires that one of FLAG_IMMUTABLE or FLAG_MUTABLE....
Replies
1
Views
898
Erel
  • Question
Android Question setSystemUiVisibility flags
Replies
3
Views
1K
Cableguy
  • Solved
Android Question NFC2.EnableForegroundDispatch no longer works on api 31 (FLAG_MUTABLE issue)
Replies
1
Views
1K
Pxs
  • Solved
Android Question Help: FLAG_IMMUTABLE or FLAG_MUTABLE
2 3 4
Replies
62
Views
10K
Zeev Goldstein
Menu
Log in
Register
Cookies are required to use this site. You must accept them to continue using the site. Learn more…