Bug: Sending FCM push notification is not working on server side even if setting "FCM_TOKEN:5942856091:5" Redis key/value manually.

[enkhchuluun]

What happened?

Sending FCM push notification is not working on server side even if setting "FCM_TOKEN:5942856091:5" Redis key/value manually.

It gives mainly following error:

[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x119852d]

goroutine 149 [running]: github.com/openimsdk/open-im-server/v3/internal/push/offlinepush/fcm.(*Fcm).Push(0x0, {0x17d3638, 0xc000c236e0}, {0xc000c369e0, 0x1, 0x0?}, {0xc00069b800, 0x15}, {0xc00069b800, 0x15}, ...) /home/chuka/wspace/test/openim/open-im-server/internal/push/offlinepush/fcm/push.go:73 +0x9cd

This looks like FCM push is not tested yet~

What did you expect to happen?

Should send FCM notification normally

How can we reproduce it (as minimally and precisely as possible)?

• in config.yaml, edit to use fcm and place a firebase key json file in config directory
• set redis key manually
• test notification by send a chat in front UI.

Anything else we need to know?

No response

version

```console $ {name} version # paste output here ```

Cloud provider

OS version

```console # On Linux: $ cat /etc/os-release # paste output here $ uname -a # paste output here # On Windows: C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture # paste output here ```

Install tools

[kubbot]

Hello! Thank you for filing an issue.

If this is a bug report, please include relevant logs to help us debug the problem.

Join slack 🤖 to connect and communicate with our developers.

[FGadvancer]

hi, you should confirm whether you called the "UpdateFcmToken" function in the IM SDK during user registration, like that:

[kubbot]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[kubbot]

This issue was closed because it has been stalled for 7 days with no activity.