FCM: `apns.fcmOptions.imageUrl` and `notification.imageUrl` not rendering images for < iOS 18 and < ipadOS 18
@chong-shao ya está trabajando en esto.
Desde el 19/12/2024.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
[REQUIRED] Step 2: Describe your environment
- Operating System version: < iOS 18, < ipadOS 18 (client), Ubuntu 14.04.6 LTS (server)
- Firebase SDK version: 12.0.0
- Firebase Product: Cloud messaging (FCM)
- Node.js version: 16 (LTS)
- Yarn version: 1.22.22
[REQUIRED] Step 3: Describe the problem
-
Images do not render on iOS < 18 and ipadOS < 18 devices, when sending a payload with
apns.fcmOptions.imageUrlornotification.imageUrl. I thought it might be related to image size so I sent an image with a size of 400 bytes but still no luck. -
Slightly unrelated, but the docs state to use
apns.fcmOptions.image(source) whilst the TypeScript interface declaresapns.fcmOptions.imageUrl(code). I've tried setting an ignore rule for the compiler to useapns.fcmOptions.imagein the payload, whilst this also renders images for iOS 18 and ipadOS 18, it still doesn't render for iOS 17 and ipadOS 17 devices.
Steps to reproduce:
What happened? How can we make the problem occur?
This could be a description, log/console output, etc.
- Create notification payload with image url set as
apns.fcmOptions.imageUrlornotification.imageUrl - Send notification (using
sendEachForMulticast()) - Observe received notification on iOS 18 and ipadOS 18 devices, image successfully displayed on both
- Observe received notification on iOS 17 and ipadOS 17 devices, image not displayed on either
Example: Successful notification on ios 18 with image
Relevant Code:
Example payload
{
apns: {
fcmOptions: {
imageUrl: "imageUrl"
},
payload: {
aps: {
alert: {
body: "body"
},
mutableContent: true
}
}
}
}
- Lenguaje dominante
- TypeScript
- Estrellas
- 1.7k
- Forks
- 419
- Merge medio
- 4 d 20 h
- PR fusionados (30 d)
- 16
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de firebase/firebase-admin-node
-
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
firebase/firebase-admin-node#3234 ·
-
firebase/firebase-admin-node#3221 · 3 comentarios · 1 asignado ·
-
api: messaging
Dificultad 3/5 1-2 días Aptitud para principiantes 70/100
firebase/firebase-admin-node#3215 ·
-
api: messaging
Dificultad 5/5 Más de una semana Aptitud para principiantes 28/100
firebase/firebase-admin-node#3214 ·
-
api: firestore type: feature request
firebase/firebase-admin-node#3183 · 1 comentario · 1 asignado ·
Todos los issues de firebase/firebase-admin-node
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
mksglu/context-mode#1200 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
jaegertracing/jaeger-ui#4506 ·
-
area:desktop area:ui bug platform:macos
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
anthropics/claude-code#96687 ·
-
good first issue
Dificultad 1/5 Menos de una hora Aptitud para principiantes 95/100
AOSSIE-Org/DebateAI#582 · 2 comentarios ·