OS X and iOS application and framework to play with the Apple Push Notification service (APNs)

Related tags

NWPusher
Overview

Pusher Icon

Pusher

OS X and iOS application and framework to play with the Apple Push Notification service (APNs)

Pusher OS X

Installation

Install the Mac app using Homebrew cask:

brew cask install pusher

Or download the latest Pusher.app binary:

Alternatively, you can include NWPusher as a framework, using CocoaPods:

pod 'NWPusher', '~> 0.7.0'

or Carthage (iOS 8+ is required to use Cocoa Touch Frameworks)

github "noodlewerk/NWPusher"

Or simply include the source files you need. NWPusher has a modular architecture and does not have any external dependencies, so use what you like.

About

Testing push notifications for your iOS or Mac app can be a pain. You might consider setting up your own server or use one of the many push webservices online. Either way it's a lot of work to get all these systems connected properly. When it is all working properly, push notifications come in fast (< 1 sec) and reliably. However when nothing comes in, it can be very hard to find out why.

That's why I made Pusher. It is a Mac and iPhone app for sending push notifications directly to the Apple Push Notification Service. No need to set up a server or create an account online. You only need the SSL certificate and a device token to start pushing directly from your Mac, or even from an iPhone! Pusher has detailed error reporting and logs, which are very helpful with verifying your setup.

Pusher comes with a small framework for both OS X and iOS. It provides various tools for sending notifications programmatically. On OS X it can use the keychain to retrieve push certificates and keys. Pusher can also be used without keychain, using a PKCS #12 file. If you want to get a better understanding of how push notifications work, then this framework is a good place to start and play around.

Features

Mac OS X application for sending push notifications through the APN service:

  • Takes certificates and keys directly from the keychain
  • Fully customizable payload with syntax checking
  • Allows setting expiration and priority
  • Stores device tokens so you don't have to copy-paste them every time
  • Handles PKCS #12 files (.p12)
  • Automatic configuration for sandbox
  • Reports detailed error messages returned by APNs
  • Reads from feedback service

OS X and iOS framework for sending pushes from your own application:

  • Modular, no dependencies, use what you like
  • Fully documented source code
  • Detailed error handling
  • iOS compatible, so you can also push directly from your iPhone :o
  • Demo applications for both platforms

Getting started

Before you can start sending push notification payloads, there are a few hurdles to take. First you'll need to obtain the Apple Push Services SSL Certificate of the app you want to send notifications to. This certificate is used by Pusher to set up the SSL connection through which the payloads will be sent to Apple.

Second you'll need the device token of the device you want to send your payload to. Every device has its own unique token that can only be obtained from within the app. It's a bit complicated, but in the end it all comes down to just a few clicks on Apple's Dev Center website, some gray hairs, and a bit of patience.

Certificate

Let's start with the SSL certificate. The goal is to get both the certificate and the private key into your OS X keychain. If someone else already generated this certificate, you'll need to ask for exporting these into a PKCS12 file. If there is no certificate generated yet, you can generate the certificate and the private key in the following steps:

  1. Log in to Apple's Dev Center
  2. Go to the Provisioning Portal or Certificates, Identifiers & Profiles
  3. Go to Certificates and create a Apple Push Notification service SSL
  4. From here on you will be guided through the certificate generation process.

Keep in mind that you will eventually be downloading a certificate, which you will need to install in your keychain together with the private key. This should look something like this:

Keychain export

NB: There is Development and Production certificates, which should (generally) correspond to respectively DEBUG and RELEASE versions of your app. Make sure you get the right one, check Development (sandbox) or Production, iOS or Mac, and the bundle identifier.

The push certificate should be exported to a PKCS12 file, which allows you to share these with fellow developers:

PKCS12 file

Device token

Now you need to obtain a device token, which is a 64 character hex string (256 bits). This should be done from within the iOS app you're going to push to. Add the following lines to the application delegate (Xcode 6 required):

- (BOOL)application:(UIApplication *)application
    didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
    if ([application respondsToSelector:@selector(registerUserNotificationSettings:)]) {
        NSLog(@"Requesting permission for push notifications..."); // iOS 8
        UIUserNotificationSettings *settings = [UIUserNotificationSettings settingsForTypes:
            UIUserNotificationTypeAlert | UIUserNotificationTypeBadge |
            UIUserNotificationTypeSound categories:nil];
        [UIApplication.sharedApplication registerUserNotificationSettings:settings];
    } else {
        NSLog(@"Registering device for push notifications..."); // iOS 7 and earlier
        [UIApplication.sharedApplication registerForRemoteNotificationTypes:
            UIRemoteNotificationTypeAlert | UIRemoteNotificationTypeBadge |
            UIRemoteNotificationTypeSound];
    }
    return YES;
}

- (void)application:(UIApplication *)application
    didRegisterUserNotificationSettings:(UIUserNotificationSettings *)settings
{
    NSLog(@"Registering device for push notifications..."); // iOS 8
    [application registerForRemoteNotifications];
}

- (void)application:(UIApplication *)application
    didRegisterForRemoteNotificationsWithDeviceToken:(NSData *)token
{
    NSLog(@"Registration successful, bundle identifier: %@, mode: %@, device token: %@",
        [NSBundle.mainBundle bundleIdentifier], [self modeString], token);
}

- (void)application:(UIApplication *)application
    didFailToRegisterForRemoteNotificationsWithError:(NSError *)error
{
    NSLog(@"Failed to register: %@", error);
}

- (void)application:(UIApplication *)application handleActionWithIdentifier:(NSString *)identifier
    forRemoteNotification:(NSDictionary *)notification completionHandler:(void(^)())completionHandler
{
    NSLog(@"Received push notification: %@, identifier: %@", notification, identifier); // iOS 8
    completionHandler();
}

- (void)application:(UIApplication *)application
    didReceiveRemoteNotification:(NSDictionary *)notification
{
    NSLog(@"Received push notification: %@", notification); // iOS 7 and earlier
}

- (NSString *)modeString
{
#if DEBUG
    return @"Development (sandbox)";
#else
    return @"Production";
#endif
}

Now, when you run the application, the 64 character push string will be logged to the console.

Push from OS X

With the SSL certificate and private key in the keychain and the device token on the pasteboard, you're ready to send some push notifications. Let's start by sending a notification using the Pusher app for Mac OS X. Open the Pusher Xcode project and run the PusherMac target:

Pusher OS X

The combo box at the top lists the available SSL certificates in the keychain. Select the certificate you want to use and paste the device token of the device you're pushing to. The text field below shows the JSON formatted payload text that you're sending. Read more about this format in the Apple documentation under Apple Push Notification Service.

Now before you press Push, make sure the application you're sending to is in the background, e.g. by pressing the home button. This way you're sure the app is not going to interfere with the message, yet. Press push, wait a few seconds, and see the notification coming in.

If things are not working as expected, then take a look at the Troubleshooting section below.

Pusher OS X

Push from iOS

The ultimate experience is of course pushing from an iPhone to an iPhone, directly. This can be done with the Pusher iOS app. Before you run the PusherTouch target, make sure to include the certificate, private key, and device token inside the app. Take the PKCS12 file that you exported earlier and include it in the PusherTouch bundle. Then go to NWAppDelegate.m in the Touch folder and configure pkcs12FileName, pkcs12Password, and deviceToken. Now run the PusherTouch target:

Pusher iOS

If everything is set up correctly, you only need to Connect and Push. Then you should receive the Testing.. push message on the device.

Again, if things are not working as expected, take a look at the Troubleshooting section below or post an issue on GitHub.

Consult Apple's documentation for more info on the APNs architecture: Apple Push Notification Service

Pushing from code

Pusher can also be used as a framework to send notifications programmatically. The included Xcode project provides examples for both OS X and iOS. The easiest way to include NWPusher is through CocoaPods:

pod 'NWPusher', '~> 0.7.0'

CocoaPods also compiles documentation, which can be accessed through CocoaDocs. Alternatively you can include just the files you need from the Classes folder. Make sure you link with Foundation.framework and Security.framework.

Before any notification can be sent, you first need to create a connection. When this connection is established, any number of payloads can be sent.

Note that Apple doesn't like it when you create a connection for every push. Therefore be careful to reuse a connection as much as possible in order to prevent Apple from blocking.

To create a connection directly from a PKCS12 (.p12) file:

    NSURL *url = [NSBundle.mainBundle URLForResource:@"pusher.p12" withExtension:nil];
    NSData *pkcs12 = [NSData dataWithContentsOfURL:url];
    NSError *error = nil;
    NWPusher *pusher = [NWPusher connectWithPKCS12Data:pkcs12 password:@"pa$$word" error:&error];
    if (pusher) {
        NSLog(@"Connected to APNs");
    } else {
        NSLog(@"Unable to connect: %@", error);
    }

When pusher is successfully connected, send a payload to your device:

    NSString *payload = @"{\"aps\":{\"alert\":\"Testing..\"}}";
    NSString *token = @"0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF";
    NSError *error = nil;
    BOOL pushed = [pusher pushPayload:payload token:token identifier:rand() error:&error];
    if (pushed) {
        NSLog(@"Pushed to APNs");
    } else {
        NSLog(@"Unable to push: %@", error);
    }

After a second or so, we can take a look to see if the notification was accepted by Apple:

    NSUInteger identifier = 0;
    NSError *apnError = nil;
    NSError *error = nil;
    BOOL read = [pusher readFailedIdentifier:&identifier apnError:&apnError error:&error];
    if (read && apnError) {
        NSLog(@"Notification with identifier %i rejected: %@", (int)identifier, apnError);
    } else if (read) {
        NSLog(@"Read and none failed");
    } else {
        NSLog(@"Unable to read: %@", error);
    }

Alternatively on OS X you can also use the keychain to obtain the SSL certificate. In that case first collect all certificates:

    NSError *error = nil;
    NSArray *certificates = [NWSecTools keychainCertificatesWithError:&error];
    if (certificates) {
        NSLog(@"Loaded %i certificates", (int)certificates.count);
    } else {
        NSLog(@"Unable to access keychain: %@", error);
    }

After selecting the right certificate, obtain the identity from the keychain:

    NSError *error = nil;
    NWIdentityRef identity = [NWSecTools keychainIdentityWithCertificate:certificate error:&error];
    if (identity) {
        NSLog(@"Loaded identity: %@", [NWSecTools inspectIdentity:identity]);
    } else {
        NSLog(@"Unable to create identity: %@", error);
    }

Take a look at the example project for variations on this approach.

Consult Apple's documentation for more info on the client-server communication: Provider Communication

Feedback Service

The feedback service is part of the Apple Push Notification service. The feedback service is basically a list containing device tokens that became invalid. Apple recommends that you read from the feedback service once every 24 hours, and no longer send notifications to listed devices. Note that this can be used to find out who removed your app from their device.

Communication with the feedback service can be done with the NWPushFeedback class. First connect using one of the connect methods:

    NSURL *url = [NSBundle.mainBundle URLForResource:@"pusher.p12" withExtension:nil];
    NSData *pkcs12 = [NSData dataWithContentsOfURL:url];
    NSError *error = nil;
    NWPushFeedback *feedback = [NWPushFeedback connectWithPKCS12Data:pkcs12 password:@"pa$$word" error:&error];
    if (feedback) {
        NSLog(@"Connected to feedback service");
    } else {
        NSLog(@"Unable to connect to feedback service: %@", error);
    }

When connected read the device token and date of invalidation:

    NSError *error = nil;
    NSArray *pairs = [feedback readTokenDatePairsWithMax:100 error:&error];
    if (pairs) {
        NSLog(@"Read token-date pairs: %@", pairs);
    } else {
        NSLog(@"Unable to read feedback: %@", error);
    }

Apple closes the connection after the last device token is read.

Pushing to macOS

On macOS, you obtain a device token for your app by calling the registerForRemoteNotificationTypes: method of the NSApplication object. It is recommended that you call this method at launch time as part of your normal startup sequence. The first time your app calls this method, the app object requests the token from APNs. After the initial call, the app object contacts APNs only when the device token changes; otherwise, it returns the existing token quickly.

The app object notifies its delegate asynchronously upon the successful or unsuccessful retrieval of the device token. You use these delegate callbacks to process the device token or to handle any errors that arose. You must implement the following delegate methods to track whether registration was successful:

  • Use the application:didRegisterForRemoteNotificationsWithDeviceToken: to receive the device token and forward it to your server.
  • Use the application:didFailToRegisterForRemoteNotificationsWithError: to respond to errors.

Note: If the device token changes while your app is running, the app object calls the appropriate delegate method again to notify you of the change.

The app delegate calls the registerForRemoteNotificationTypes: method as part of its regular launch-time setup, passing along the types of interactions that you intend to use. Upon receiving the device token, the application:didRegisterForRemoteNotificationsWithDeviceToken: method forwards it to the app’s associated server using a custom method. If an error occurs during registration, the app temporarily disables any features related to remote notifications. Those features are re-enabled when a valid device token is received.

    - (void)applicationDidFinishLaunching:(NSNotification *)notification {
        // Configure the user interactions first.
        [self configureUserInteractions];

        [NSApp registerForRemoteNotificationTypes:(NSRemoteNotificationTypeAlert | NSRemoteNotificationTypeSound)];
    }
    - (void)application:(NSApplication *)application
        didRegisterForRemoteNotificationsWithDeviceToken:(NSData *)deviceToken {
        // Forward the token to your server.
        [self forwardTokenToServer:deviceToken];
    }
    - (void)application:(NSApplication *)application
        didFailToRegisterForRemoteNotificationsWithError:(NSError *)error {
        NSLog(@"Remote notification support is unavailable due to error: %@", error);
        [self disableRemoteNotificationFeatures];
    }

Certificate and key files

Pusher reads certificate and key data from PKCS12 files. This is a binary format that bundles both X.509 certificates and a private key in one file. Conversion from other file formats to and from PKCS12 is provided by the OpenSSL CLI.

Inspect PKCS12:

openssl pkcs12 -in pusher.p12

where the output should be something like:

...
friendlyName: Apple Development/Production IOS/Mac Push Services: <your-bundle-identifier>
localKeyID: <key-id>
...
-----BEGIN CERTIFICATE-----
...
friendlyName: <private-key-used-for-generating-above-certificate>
localKeyID: <same-key-id>
...
-----BEGIN PRIVATE KEY-----
...

Make sure your build matches the Development/Production, iOS/Mac, and bundle identifier.

Inspect PKCS12 structure:

openssl pkcs12 -in pusher.p12 -info -noout

Inspect PEM:

openssl rsa -in pusher.pem -noout -check
openssl rsa -in pusher.pem -pubout
openssl x509 -in pusher.pem -noout -pubkey

PKCS12 to PEM:

openssl pkcs12 -in pusher.p12 -out pusher.pem -clcerts -aes256

Alternatively you can use the command below, which does not encrypt the private key (not recommended):

openssl pkcs12 -in pusher.p12 -out pusher.pem -nodes -clcerts

PEM to PKCS12:

openssl pkcs12 -export -in pusher.pem -out pusher.p12

Consult the OpenSSL documentation for more details: OpenSSL Documents - pkcs12

Troubleshooting

Apple's Push Notification Service is not very forgiving in nature. If things are done in the wrong order or data is formatted incorrectly the service will refuse to deliver any notification, but generally provides few clues about went wrong and how to fix it. In the worst case, it simply disconnects without even notifying the client.

Some tips on what to look out for:

  • A device token is unique to both the device, the developer's certificate, and to whether the app was built with a production or development (sandbox) certificate. Therefore make sure that the push certificate matches the app's provisioning profile exactly. This doesn't mean the tokens are always different; device tokens can be the same for different bundle identifiers.

  • There are two channels through which Apple responds to pushed notifications: the notification connection and the feedback connection. Both operate asynchronously, so for example after the second push has been sent, we might get a response to the first push, saying it has an invalid payload. Use a new identifier for every notification so these responses can be linked to the right notification.

If it fails to connect then check:

  • Are the certificates and keys in order? Use the OpenSSL commands listed above to inspect the certificate. See if there is one push certificate and key present. Also make sure you're online, try ping www.apple.com.

  • Is the certificate properly loaded? Try initializing an identity using [NWSecTools identityWithPKCS12Data:data password:password error:&error] or [NWSecTools keychainIdentityWithCertificate:certificate error:&error].

  • Are you using the right identity? Use [NWSecTools inspectIdentity:identity] to inspect the identity instance. In general NWSecTools can be helpful for inspecting certificates, identities and the keychain.

  • Can you connect with the push servers? Try [NWPusher connectWithIdentity:identity error:&error] or [NWPusher connectWithPKCS12Data:pkcs12 password:password error:&error].

  • Pusher connects on port 2195 with hosts gateway.push.apple.com and gateway.sandbox.push.apple.com, and on port 2196 with hosts feedback.push.apple.com and feedback.sandbox.push.apple.com. Make sure your firewall is configured to allow these connections.

If nothing is delivered to the device then check:

  • Is the device online? Is it able to receive push notifications from other services? Try to get pushes from other apps, for example a messenger. Many wireless connections work visibly fine, but do not deliver push notifications. Try to switch to another wifi or cellular network.

  • Are you pushing to the right device token? This token should be returned by the OS of the receiving device, in the callback -application: didRegisterForRemoteNotificationsWithDeviceToken:. The push certificate should match the provisioning profile of the app, check Development or Production, iOS or Mac, and the bundle identifier. Make sure the receiving app is closed, so it cannot interfere with the delivery.

  • Does the push call succeed? Isn't there any negative response from the push server or feedback server? Both [pusher pushPayload:payload token:token identifier:rand() error:&error] and [pusher readFailedIdentifier:&identifier apnError:&apnError error:&error] should return YES, but wait a second between pushing and reading. Also try to connect to the feedback service to read feedback.

Consult Apple's documentation for more troubleshooting tips: Troubleshooting Push Notifications

Build with Xcode

The source comes with an Xcode project file that should take care of building the OS X and iOS demo applications. Alternatively you can also build Pusher.app from the commandline with xcodebuild:

xcodebuild -project NWPusher.xcodeproj -target PusherMac -configuration Release clean install

After a successful build, Pusher.app can be found in the build folder of the project.

Documentation

Documentation generated and installed using appledoc by running from the project root:

appledoc .

See the appledoc documentation for more info.

License

Pusher is licensed under the terms of the BSD 2-Clause License, see the included LICENSE file.

Authors

Issues
  • General cert name

    General cert name

    Apple recently changed their APNS handling and new certificates are named "Apple Push Services" instead of "Apple Production IOS Push Services". When I now try to import one of these Pusher refuses to import them.

    opened by whiskey 18
  • SSL Handshake failure for production certificate.

    SSL Handshake failure for production certificate.

    Hi, am using your test app for IOS trying to get push notifications to work. I have included the correct p12 file and password. But when I try to connect it gives me the error: Unable to connect: Unable to perform SSL handshake

    Weird thing is I also tried on the Mac app and it works just perfect on there so am thinking it isn't my certificate. Any clues to why this is failing?

    opened by BalintDezso 18
  • Library function to push same payload on multiple tokens

    Library function to push same payload on multiple tokens

    Hello there, Your library is working flawlessly and I am missing the following:

    Could you add something like that?

    -(void)pushPayloadString:(NSString *)payload tokens:(NSArray *)tokens expires:(NSDate *)expires block:(void(^)(NWPusherResult response))block;

    to push the same payload on multiple tokens.

    Regards, Nikos

    opened by nickbit 17
  • No push certificates found

    No push certificates found

    When using NWPusher, I'm not able to import the Apple Push Services certificate I've just created for Adhoc distribution.

    Steps to reproduce:

    1 - Create a new App ID; 2 - Create a Production Certificate for Push Notifications; 3 - Create the AdHoc provisioning profile. 4 - Export the Production Certificate (Apple Push Services) into a .p12 file. 5 - Open it with NWPusher.

    The result is:

    Unable to import p12 file: no push certificates found.

    opened by andremacpereira 14
  • Extract OS X and iOS frameworks to allow modularity

    Extract OS X and iOS frameworks to allow modularity

    Hi, I wanted to leverage your great code in one of my projects without pulling the dependancies manually. For that I extracted relevant aspects into OS X and iOS frameworks allowing to use project through Carthage dependency manager. It doesn't affect existent projects in any way, except for bumping minimum required version for iOS app to 8.0, which is the minimum version allowing embedded frameworks.

    opened by zats 11
  • Notification error: APN invalid token

    Notification error: APN invalid token

    Hello, when I try to use APN Production SSL Certificate to do Push Notifications it failed and got "Notification error: APN invalid token". But if I use Development SSL Certificate it work fine!!

    Did any one know what is the problem in it? thanks a lot!!

    opened by louisyip 10
  • Add support for APNS auth token (p8)

    Add support for APNS auth token (p8)

    Apple provides a way to send push notifications without the need of certificates by creating never expiring authentication keys (http://stackoverflow.com/questions/39943701/how-to-send-apns-push-messages-using-apns-auth-key-and-standard-cli-tools). Unfortunately NWPusher does not support this kind of authentication yet.

    enhancement 
    opened by BenchR267 8
  • Unable to connect : SSL Handshake failed.

    Unable to connect : SSL Handshake failed.

    I have download the Certificate exported all that and still can not connect to server/ How to troubleshoot this? Thanks

    opened by cerw 6
  • Rich Content Push Notifications not going through

    Rich Content Push Notifications not going through

    Push notifications with "mutable-content":0 are delivered right away, but I'm trying to test to see if rich push notifications are working with my app via the Pusher desktop app with this payload and they don't seem to be delivered to my iPhone.

    Is there some reason why Pusher would not support this? Or maybe it's Apple that's failing to deliver, but as far as I can tell the payload is correct.

    {
      "aps": {
        "alert": {
          "title": "Realtime Custom Push Notifications",
          "subtitle": "Now with iOS 10 support!",
          "body": "Add multimedia content to your notifications"
        },
        "sound": "default",
        "badge": 1,
        "mutable-content": 1,
        "category": "realtime",
        "data": {
          "attachment-url": "https://framework.realtime.co/blog/img/ios10-video.mp4"
        }
      }
    }
    
    opened by tettoffensive 4
  • Cannot connecting to APNS

    Cannot connecting to APNS

    Hi,

    I don't know if it is related to the Keynote of today but it seems that we have connecting issues :

    Connecting Failure

    Version 0.7.0 (15)

    Thanks

    opened by bill350 4
  • Unable to read: Read connection closed

    Unable to read: Read connection closed

    When click push, it show this error Unable to read: Read connection closed, push failed, from the log, below is the detail log information

    [08:11:25.089961 Pusher NWAppDelegate.m:369] [info] Connected  (xxx-xxxx.xxx.xxx.xxx sandbox)
    [08:11:27.173382 Pusher NWAppDelegate.m:399] [info] Pushing..
    [08:11:28.237458 Pusher NWAppDelegate.m:413] [warn] Unable to read: Read connection closed
    

    When I use the same device token push with SamartPush, it show push success, but I could not seen the notification banner on my iPhone.

    Does any one known this issue?

    opened by a-href 0
  • VOIP Notifications are not sending using p12

    VOIP Notifications are not sending using p12

    When I applied p12 certificates properly PKPushRegister(VOIP) notifications are sent and working fine both sender/receiver side for few days using NWPusher, but suddenly stopped receiving notifications, I don't know where the issue occur exactly. When I try to use same p12 certificate using Pusher Tool, VOIP notifications are properly sent and then I thought that issue is with NWPusher and this NWPusher is not supporting for "p8" certificate to send VOIP notifications.

    Please help me in this

    opened by narendargit 1
  • Pusher app does not able to sent push message

    Pusher app does not able to sent push message

    I have tried to send push notification but all the time I got error: Unable to read: Read connection closed I tried with few apps, same results. https://ibb.co/gdfxrCN

    opened by StefanMiticon 9
  • Update brew install command

    Update brew install command

    You no longer use the cask parameter when installing a brew cask. It will result in an error. I updated the main README to reflect this.

    opened by jhubbardsf 0
  • Time to start deprecating project from Github

    Time to start deprecating project from Github

    Project has been very useful for decade or so.. But as there seems to be no plans to implement support for Apples new API, it's probably better start archiving it. Anyway Apple is closing down the legacy provider in March/2021.

    https://developer.apple.com/documentation/usernotifications/setting_up_a_remote_notification_server/sending_notification_requests_to_apns?language=objc

    APNs will not support legacy binary protocol as of March 31, 2021. We recommend updating to the HTTP/2-based API from this page as soon as possible.

    opened by noxo 2
  • Feature Request: Support for Push Notifications to the Simulator

    Feature Request: Support for Push Notifications to the Simulator

    With the recent update we can now send push notifications to the simulator using a the following:

    xcrun simctl push <device id> <app bundle id> <filename>.apns

    The apns file is the json package for the push notification.

    It would be great to have a visual tool to do this, and i feel that pusher would be a great place to do that. The command is a bit tedious to get the deviceId's, especially when switch which device you are targeting and the ability to choose device from a drop down of running simulators would be very convenient.

    opened by 11health-joshua 0
  • Not Able to send push notification

    Not Able to send push notification

    Hi,

    I am not able to send push notification any more from Pusher Mac app. It was showing Notification error: APN invalid Token. please give the solution for the issue

    opened by sukritisuku 10
  • Add ability to set apns-push-type header

    Add ability to set apns-push-type header

    In iOS 13 it is required to set apns-push-type to background if we want to use silent push notifications, otherwise notifications won't be delivered.

    Is there a way to set that header?

    opened by josippetric 3
  • Support custom http headers (for apns-priority and iOS 13)

    Support custom http headers (for apns-priority and iOS 13)

    iOS 13 requires the apns-priority header to be set to 5 when sending background (content-available = 1) notifications. If the header is left off, it defaults to 10 and the push fails. So currently whenever you send a background notification with Pusher in iOS 13, it fails.

    Rather than having the app set this header automatically, I'd prefer to be able to add headers manually so that we can test with other APNS header types.

    opened by jscalo 4
  • Value of expiration

    Value of expiration

    In file NWAppDelegate.m at row 247 is code: case 3: return [NSDate dateWithTimeIntervalSince1970:300]; but I think correct code should be: case 3: return [NSDate dateWithTimeIntervalSinceNow:300];

    opened by raptorxcz 0
Releases(0.7.5)
Owner
noodlewerk
noodlewerk
The debug application for Apple Push Notification Service (APNs).

Knuff The debug application for Apple Push Notification Service (APNs). Download the latest version Features Send push notifications to APNS (Apple Pu

Knuff 4.9k Jul 29, 2021
The easiest way to install and switch between multiple versions of Xcode - with a mouse click.

Xcodes.app The easiest way to install and switch between multiple versions of Xcode. If you're looking for a command-line version of Xcodes.app, try x

Robots and Pencils 1.2k Aug 5, 2021
A simple but highly customizable `UICollectionViewLayout` for `UICollectionView`.

CollectionViewPagingLayout Layout Designer SnapshotTransformView ScaleTransformView StackTransformView Custom implementations About This is a simple b

Amir Khorsandi 1.3k Aug 4, 2021
The Git interface you've been missing all your life has finally arrived.

GitUp Work quickly, safely, and without headaches. The Git interface you've been missing all your life has finally arrived. Git recently celebrated it

GitUp 9.8k Jul 31, 2021
A free, native Apple macOS app for testing HTTP/REST endpoints

About CocoaRestClient is a Mac OS X app for testing HTTP/Restful endpoints. I love curl, but sometimes I need my output XML or JSON pretty printed. I

Mike Mattozzi 2.2k Aug 2, 2021
ColorSet is a macOS utility and framework allowing developers to manage custom interface colors with ease.

ColorSet About ColorSet is a macOS utility and framework allowing developers to manage custom interface colors with ease. Rationale As of macOS 10.14

DigiDNA 126 Aug 5, 2021
The unofficial WWDC app for macOS

The unofficial WWDC app for macOS Enjoy WWDC from the comfort of your Mac with the unofficial WWDC app for macOS. Whether you're (virtually) attending

Guilherme Rambo 8.1k Jul 31, 2021
:closed_book: Swift Logging Utility for Xcode Google Docs

QorumLogs Swift Logging Utility in Xcode & Google Docs Log Levels class MyAwesomeViewController: UIViewController { override func viewDidLoad() {

Goktug Yilmaz 782 Jul 16, 2021
Fork of Pieter's nice git GUI for OS X. Includes branch/tag sidebar and various fixes. Current development focus is on removing legacy git command line usage in favour of libgit2 and objective-git.

What is GitX? GitX is a graphical client for the git version control system, written specifically for OS X Mavericks. This means that it has a native

Rowan James 2.1k Jul 31, 2021
Use the Touch Bar on any Mac

Touch Bar Simulator Use the Touch Bar on any Mac Launch the Touch Bar simulator from anywhere without needing to have Xcode installed, whereas Apple r

Sindre Sorhus 1.5k Aug 4, 2021
Managing Pull Requests and Issues For GitHub GitHub Enterprise

Trailer For maintained binaries and/or more info: Latest macOS version Latest iOS version Trailer for the command-line and Linux Trailer for Android N

Paul Tsochantaris 967 Jul 23, 2021
MySQL/MariaDB database management for macOS

Sequel Ace Sequel Ace is the "sequel" to longtime macOS tool Sequel Pro. Sequel Ace is a fast, easy-to-use Mac database management application for wor

Sequel-Ace 3.4k Aug 5, 2021
Apache NetBeans

Apache NetBeans Apache NetBeans is an open source development environment, tooling platform, and application framework. Build status GitHub actions Tr

The Apache Software Foundation 1.6k Aug 4, 2021
MQTT X - Elegant Cross-platform MQTT 5.0 Desktop Client

MQTT X English | 简体中文 | 日本語 MQTT X is a cross-platform MQTT 5.0 client tool open sourced by EMQ, which can run on macOS, Linux and Windows, and suppor

Scalable Enterprise MQTT Broker 1.2k Aug 5, 2021