-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Safari Push and Mobile Device Management #9
Merged
Merged
Changes from 1 commit
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
587351c
Support Safari Push and Mobile Device Management
nathany 53f360a
Merge branch 'empty_alert' into safari
nathany 3a34658
update README to use pointer to badge
nathany d2faf52
Merge branch 'master' into safari
nathany 63c006b
Merge remote-tracking branch 'origin/master' into safari
nathany File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry on the delay on this.
This feels a little awkward – there is some implicit behavior that isn't clear from the API. It feels like it should only be the
if
and noelse
. Whether or not"aps"
is included shouldn't really depend on whether"mdm"
exists.My suggestion is:
And then including the approach for
APS
in this PR https://github.com/nathany/apns/pull/1 – it'll make the code much cleaner.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bdotdub The thing is the json shouldn't include an empty "aps" node when using MDM.
Perhaps it makes more sense to check if aps is empty? Of course APS isn't just a string, so that's a deep check to ensure the entirety of APS is zero values.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bdotdub So I looked into your suggestion because I agree it's awkward as is.
But as far as I know, for Passbook notifications, the JSON should be
{"aps":{}}
even though there is nothing in the APS struct (aps.isZero()
returns true).For Mobile Device Management, there should be no aps key, as in
{"mdm":"00000000-1111-3333-4444-555555555555"}
.So unfortunately there is a dependency there, at least as far as I can tell based on the documentation and other implementations. :-(