ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Decide between @capacitor-community/push and @capacitor-fcm/fcm for Ionic push notifications. Compare features, trade‑offs, and see a step‑by‑step implementation of the community push plugin with validation steps.
Step‑by‑step guide to diagnose why Expo push notifications aren’t appearing, with checks for tokens, listeners, credentials, and OTA updates, plus fixes and when to escalate.
Decide whether to use Capacitor’s built‑in Push Notifications plugin or integrate Firebase Cloud Messaging directly. Compare constraints, trade‑offs, and see a concrete implementation example.
Learn how to register and receive FCM push messages in a Titanium Android app, from adding the ti.fcm module to handling token retrieval and troubleshooting common pitfalls.
Goal: receive background push payloads in an Appcelerator Titanium app on iOS 15+ without showing a system notification banner, while still waking the app to process the payload. Constraint: Ti.App.addEventListener('notification', ...) handles remote notifications, but the SDK does not expose a dedicated silent-push flag. Setting the APNs alert field to an e
I'm designing the alert strategy for an Expo app (SDK 50+, tested in a development build since Expo Go no longer supports push) and want to split notifications into Android channels via setNotificationChannelAsync — e.g., a HIGH-importance "messages" channel and a LOW-importance "promotions" channel — with iOS interruptionLevel handling the equivalent on App
Push notification testing in development builds Goal: verify that a development client built with expo-dev-client can receive a remote push notification via Expo’s push service without configuring production APNs or FCM credentials. Constraints: iOS remote push requires a physical device, Android channel behavior may differ between Expo’s service and direct
capacitor
firebase
ionic
android
expo
titaniumsdk
appcelerator