Push fixes for 112 #485
Merged
Push fixes for 112 #485
Conversation
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
paddybyers
force-pushed
the
push-fixes-for-112
branch
3 times, most recently
from
3b9b7c4 to
1808409
Compare
…lientId, and propagate to the device registration
…quested; fix reset()
paddybyers
force-pushed
the
push-fixes-for-112
branch
from
1808409 to
3c85143
Compare
This was referenced Jul 11, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR contains fixes for a number of miscellaneous issues found during end-to-end testing of push notifications and push activation.
Fixes:
#481
#480
#477
#475
#484