React Native Notifications

Name: React Native Notifications
Author: HoangNguyen0403

ASecurity

Push notifications for React Native using Firebase or Expo Notifications. Use when integrating push notifications with Firebase or Expo in React Native.

549 stars
0 votes
0 copies
3 views
Added June 6, 2026

developmentrustreact

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned June 6, 2026

npx -y skills add HoangNguyen0403/agent-skills-standard --skill react-native-notifications --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of React Native Notifications?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for React Native Notifications

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/hoangnguyen0403-react-native-notifications/badge)](https://www.skillsdirectory.com/skills/hoangnguyen0403-react-native-notifications)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: react-native-notifications
description: Push notifications for React Native using Firebase or Expo Notifications. Use when integrating push notifications with Firebase or Expo in React Native.
metadata:
  triggers:
    files:
    - '**/*notification*.ts'
    - '**/*notification*.tsx'
    - '**/App.tsx'
    keywords:
    - Notifications
    - messaging
    - FCM
    - expo-notifications
    - react-native-firebase
---
# React Native Notifications

## **Priority: P1 (OPERATIONAL)**


## Guidelines

- **Library**: Choose `@react-native-firebase/messaging` (Bare) or `expo-notifications` (Managed).
- **Setup**: Configure Platform channels (Android) and APNs (iOS).
- **Lifecycle**: Handle Foreground (`onMessage`), Background (`onNotificationOpenedApp`), and Quit (`getInitialNotification`) states.
- **Permissions**: Prime users before requesting system authorization.

See [implementation examples](references/implementation.md) for complete FCM handler setup with permission request and lifecycle handlers.

## Anti-Patterns

- **No Unconditional Requests**: Spamming permission dialogs leads to high denial rates.
- **No Missing Handlers**: Forgetting "Quit" state handling results in lost deep links.
- **No Unvalidated Data**: Blindly trusting payload data causes runtime crashes.

## References

See [references/implementation.md](references/implementation.md) for FCM setup, APNs config, and lifecycle handlers.