[Bug] [libFirebaseCppApp-13_4_0.so] firebase::messaging::Notification::~Notification()

[Jas0nMars]

Description

---

pid: 0, tid: 13381 >>> com.xh.vaultrush <<<

backtrace:
#00 pc 0x000000000022b57c /data/app/~~pDvKFCGSyRU7IyjolF3SGw==/com.xh.vaultrush-eI8F-KVSuwEGS2Flio3KBw==/lib/arm64/libFirebaseCppApp-13_4_0.so (firebase::messaging::Notification::~Notification()+16)
#1 pc 0x000000000022bc28 /data/app/~~pDvKFCGSyRU7IyjolF3SGw==/com.xh.vaultrush-eI8F-KVSuwEGS2Flio3KBw==/lib/arm64/libFirebaseCppApp-13_4_0.so (firebase::messaging::Message::~Message()+28)
#2 pc 0x000000000022bbd8 /data/app/~~pDvKFCGSyRU7IyjolF3SGw==/com.xh.vaultrush-eI8F-KVSuwEGS2Flio3KBw==/lib/arm64/libFirebaseCppApp-13_4_0.so (Firebase_Messaging_CSharp_delete_FirebaseMessageInternal+20)
#3 pc 0x00000000018b5a88 /data/app/~~pDvKFCGSyRU7IyjolF3SGw==/com.xh.vaultrush-eI8F-KVSuwEGS2Flio3KBw==/lib/arm64/libil2cpp.so (BuildId: de65035e43838ef8b0fa661a964f011f6be5f5d1)
#4 pc 0x00000000018b593c /data/app/~~pDvKFCGSyRU7IyjolF3SGw==/com.xh.vaultrush-eI8F-KVSuwEGS2Flio3KBw==/lib/arm64/libil2cpp.so (BuildId: de65035e43838ef8b0fa661a964f011f6be5f5d1)
#5 pc 0x00000000018b57f4 /data/app/~~pDvKFCGSyRU7IyjolF3SGw==/com.xh.vaultrush-eI8F-KVSuwEGS2Flio3KBw==/lib/arm64/libil2cpp.so (BuildId: de65035e43838ef8b0fa661a964f011f6be5f5d1)
#6 pc 0x0000000001716644 /data/app/~~pDvKFCGSyRU7IyjolF3SGw==/com.xh.vaultrush-eI8F-KVSuwEGS2Flio3KBw==/lib/arm64/libil2cpp.so (BuildId: de65035e43838ef8b0fa661a964f011f6be5f5d1)
#7 pc 0x0000000001716590 /data/app/~~pDvKFCGSyRU7IyjolF3SGw==/com.xh.vaultrush-eI8F-KVSuwEGS2Flio3KBw==/lib/arm64/libil2cpp.so (BuildId: de65035e43838ef8b0fa661a964f011f6be5f5d1)
#8 pc 0x0000000001743920 /data/app/~~pDvKFCGSyRU7IyjolF3SGw==/com.xh.vaultrush-eI8F-KVSuwEGS2Flio3KBw==/lib/arm64/libil2cpp.so (BuildId: de65035e43838ef8b0fa661a964f011f6be5f5d1)
#9 pc 0x00000000017568d8 /data/app/~~pDvKFCGSyRU7IyjolF3SGw==/com.xh.vaultrush-eI8F-KVSuwEGS2Flio3KBw==/lib/arm64/libil2cpp.so (BuildId: de65035e43838ef8b0fa661a964f011f6be5f5d1)
#10 pc 0x0000000001743868 /data/app/~~pDvKFCGSyRU7IyjolF3SGw==/com.xh.vaultrush-eI8F-KVSuwEGS2Flio3KBw==/lib/arm64/libil2cpp.so (BuildId: de65035e43838ef8b0fa661a964f011f6be5f5d1)
#11 pc 0x000000000173c7a8 /data/app/~~pDvKFCGSyRU7IyjolF3SGw==/com.xh.vaultrush-eI8F-KVSuwEGS2Flio3KBw==/lib/arm64/libil2cpp.so (BuildId: de65035e43838ef8b0fa661a964f011f6be5f5d1)
#12 pc 0x00000000016ae3d8 /data/app/~~pDvKFCGSyRU7IyjolF3SGw==/com.xh.vaultrush-eI8F-KVSuwEGS2Flio3KBw==/lib/arm64/libil2cpp.so (BuildId: de65035e43838ef8b0fa661a964f011f6be5f5d1)
#13 pc 0x00000000000b6974 /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+264)
#14 pc 0x0000000000053210 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+68)

I have the problem on 13.2, while i have seen the issue #1334 and change the version to 13.4 , but i still have the problem. It seems like happened on the notification was sended by server.

Reproducing the issue

No response

Firebase Unity SDK Version

13.4

Unity editor version

2022.3.62f1c1

Installation Method

.unitypackage

Problematic Firebase Component(s)

No response

Other Firebase Component(s) in use

No response

Additional SDKs you are using

No response

Targeted Platform(s)

Android

Unity editor platform

Windows

Scripting Runtime

IL2CPP

Release Distribution Type

Pre-built SDK from https://firebase.google.com/download/unity

Relevant Log Output

If using CocoaPods for Apple platforms, the project's Podfile.lock

Expand Podfile.lock snippet

👀 Replace this line with the contents of your Podfile.lock!

[niccolo-hare]

Hi @Jas0nMars, thanks for bringing this to our attention. I also couldn't reproduce this crash on a sample project I set up. What I did was I used version 13.4.0 of the Unity SDK as well and sent a message directly from the HTTP v1 API (via curl), and I was able to receive the message without encountering any problems.

For some background, I believe the source of the crash mentioned in #1334 was due to Messaging being deleted as it was passed from C++ to C# (as noted on the fix). This seems to imply that the message was received by the SDK and was handling it before the crash occurred. So I'm guessing there might be something going on with how the message is handled by the SDK, similar to #1334.

To help us investigate this further, could you provide some additional details:

• Are you seeing any patterns or similarities with the users being affected by this issue? (Ex. Device models/OEMs, OS version, region, etc.)
• Could you provide more information regarding how you send your message? Are you sending your requests using the Admin SDK or directly via the HTTP v1 API?
• Could you share a full sample of the request or payload you used for your campaign(s) affected by this issue? Please ensure that there are no PIIs included in your sample.

[Jas0nMars]

Hi@niccolo-hare ,Thanks for handling this!
1.On console , It seems that players with higher android versions are more affected.

2.Here is how I send notifications, I used admin sdk.

And here is how I receive notifications, I just init the sdk and do nothing else.