From 891aa95a038855488102c687ea1c70a3967fefbc Mon Sep 17 00:00:00 2001 From: m-develops <16712065+m-develops@users.noreply.github.com> Date: Thu, 5 Nov 2026 13:16:56 +0100 Subject: [PATCH] Document resource in application-level plugin meta-data The Firebase notification icon example used value, which writes android:value. Firebase reads that key as a resource ID, so the example never took effect. Application-level meta-data now accepts resource (NativePHP/mobile-air#640), written as android:resource. --- .../mobile/4/plugins/advanced-configuration.md | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-) diff --git a/resources/views/docs/mobile/4/plugins/advanced-configuration.md b/resources/views/docs/mobile/4/plugins/advanced-configuration.md index 550411b5..d5a668b7 100644 --- a/resources/views/docs/mobile/4/plugins/advanced-configuration.md +++ b/resources/views/docs/mobile/4/plugins/advanced-configuration.md @@ -172,16 +172,24 @@ Add application-level `` elements for SDK configuration: }, { "name": "com.google.firebase.messaging.default_notification_icon", - "value": "@drawable/ic_notification" + "resource": "@drawable/ic_notification" } ] } } ``` -Each entry has: -- **name** — The meta-data key -- **value** — The value (supports `${ENV_VAR}` placeholders) +Each entry has a `name` and either a `value` or a `resource`: + +| Key | Description | +|-----|-------------| +| `name` | The meta-data key (required) | +| `value` | A literal value, written as `android:value`. Supports `${ENV_VAR}` placeholders | +| `resource` | A resource reference such as `@drawable/ic_notification` or `@color/brand`, written as `android:resource` | + +Use `resource` when the SDK reads the key as a resource ID. Firebase Messaging reads +`default_notification_icon` and `default_notification_color` this way, so with `value` it can't find the icon and +falls back to its default. ## Declarative Assets