From f13c5e6726d8f187ca398f099b957419df93be0a Mon Sep 17 00:00:00 2001 From: Jz Jektvik <29360158+jektvik@users.noreply.github.com> Date: Wed, 16 Oct 2024 09:21:28 +0200 Subject: [PATCH] docs(android): clarify foregroundServiceType AndroidManifest example --- .../docs/android/foreground-service.md | 19 +++++++++++-------- 1 file changed, 11 insertions(+), 8 deletions(-) diff --git a/docs-react-native/react-native/docs/android/foreground-service.md b/docs-react-native/react-native/docs/android/foreground-service.md index 9fe8c688a..762f69056 100644 --- a/docs-react-native/react-native/docs/android/foreground-service.md +++ b/docs-react-native/react-native/docs/android/foreground-service.md @@ -183,13 +183,16 @@ You may need access to either location, camera or microphone information in your To specify which service types you require, add `notifee`'s foreground service to your `AndroidManifest.xml`: ```xml - - ... - - - - - + + + ... + + + + + + ... + ``` @@ -211,4 +214,4 @@ notifee.displayNotification({ If no [foregroundServiceTypes](/react-native/docs/android/interaction#quick-actions) property is provided, the types are taken from the manifest. -If any permission was granted while running the service, the same notification (with the same notification ID and same channel ID) can be posted again with the new `foregroundServiceTypes` property array with the same notification ID and the current running service will be updated with the new types. \ No newline at end of file +If any permission was granted while running the service, the same notification (with the same notification ID and same channel ID) can be posted again with the new `foregroundServiceTypes` property array with the same notification ID and the current running service will be updated with the new types.