Support

How can we help?

Support for Push Tools by raadtech.co. Browse the guides and FAQ below, or reach out directly — we respond to every message.

Email Support
support@raadtech.co
01

Setup Guides

Setting up APNs (.p8 auth)

  1. 1

    In your Apple Developer account, go to Certificates, Identifiers & Profiles → Keys.

  2. 2

    Create a new key, enable Apple Push Notifications service (APNs), and download the .p8 file.

  3. 3

    In Push Tools → APNs tab, click 'Import Key' and select the .p8 file.

  4. 4

    Enter your Team ID (found in Membership section of your developer account), Key ID (shown after key creation), and Bundle ID of your target app.

  5. 5

    Toggle Sandbox for development or Production for the live App Store build.

Setting up FCM (HTTP v1)

  1. 1

    In Firebase Console, select your project and go to Project Settings → Service Accounts.

  2. 2

    Click 'Generate New Private Key' and confirm. A .json file will download.

  3. 3

    In Push Tools → FCM tab, click 'Import Service Account' and select the downloaded JSON.

  4. 4

    Paste a valid FCM device registration token into the Device Token field.

  5. 5

    Compose your message and click Send. The OAuth token is cached for ~55 minutes automatically.

Setting up Expo push

  1. 1

    In your Expo project, call Notifications.getExpoPushTokenAsync() and copy the token — it starts with ExponentPushToken[.

  2. 2

    In Push Tools → Expo tab, paste the token in the Device Token field.

  3. 3

    Optionally add an Expo Access Token (from expo.dev/accounts → Access Tokens) for authenticated requests.

  4. 4

    Fill in Title and Body, configure optional fields (data, TTL, badge), and click Send.

  5. 5

    The response panel shows the ticket status and receipt ID for follow-up checks.

02

Frequently Asked Questions

QWhy is my Expo push token not working?

Make sure the token starts with ExponentPushToken[ and is for a device with notifications enabled. Tokens from simulators are not valid — use a physical device. Also confirm your Expo Access Token (if set) hasn't expired.

QMy APNs notification is delivered in sandbox but not production — why?

Sandbox and production use different APNs endpoints. Ensure you've toggled to 'Production' in the APNs tab and that your .p8 key has the Apple Push Notifications service capability enabled in your Apple Developer account.

QHow do I get an FCM service account JSON file?

In the Firebase Console, go to Project Settings → Service Accounts → Generate New Private Key. Download the JSON and import it in Push Tools via the FCM tab. The file stays on your machine; it is never transmitted to raadtech.co.

QWhere are my credentials stored?

All credentials — APNs .p8 keys, FCM service account JSON, and Expo access tokens — are stored in the macOS Keychain via the OS keyring API. They are never written to plain text files or sent to any raadtech.co server.

QWhat is the Device Book?

Device Book lets you save and name device tokens (Expo, FCM, APNs) so you don't have to paste them every time. It's stored locally in a JSON file on your Mac. You can import and export it from the Device Book panel.

QMy FCM request returns a 401 / OAuth error — what's wrong?

The service account JSON may have expired or have insufficient permissions. Re-download a fresh service account key from Firebase Console and make sure it has the Firebase Cloud Messaging API enabled in Google Cloud Console.

QCan I send Live Activity updates with Push Tools?

Yes. Use the Live Activity tab to compose start, update, and end payloads. You'll need an APNs .p8 key configured and the correct push-type set to live-activity. Only physical iPhones on iOS 16.1+ support Live Activities.

QHow do I file a bug or request a feature?

Email us at support@raadtech.co with a description of the issue and your macOS version. We review every message.

03

Troubleshooting

Symptom

Push Tools quits immediately on launch

Fix

Make sure you're running macOS 13 or later. If you downloaded the app outside the App Store, open System Settings → Privacy & Security and approve the app.

Symptom

Import key / Import JSON does nothing

Fix

File access is sandboxed to Desktop, Documents, Downloads, and temp. Move your .p8 or .json file to one of those locations and try again.

Symptom

APNs returns InvalidProviderToken

Fix

Your .p8 key, Team ID, or Key ID is incorrect. Double-check all three values against your Apple Developer account. Key IDs are 10 characters long.

Symptom

Expo ticket shows DeviceNotRegistered

Fix

The device token is no longer valid — the app was uninstalled or notifications were revoked. Regenerate the token from a fresh install on a physical device.

Symptom

FCM returns 403 PERMISSION_DENIED

Fix

The Firebase Cloud Messaging API may not be enabled in your Google Cloud project. In Cloud Console, search for 'Firebase Cloud Messaging API' and enable it.

Still stuck?

Email us directly — we read every message and typically reply within one business day.

support@raadtech.co
© 2026 raadtech.co · All rights reserved
Privacy PolicyHome