fix rpc client bug #112
Closed
fix rpc client bug #112
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
|
Its been a while since this PR but I think the fix for this (rather than me merging as it would change behaviour) is to just use your own payload class. The payload can be anything so long as it returns bytes containing the JSON-encoded payload. So if you make your own notification package as per your code, it should just work. |
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.
when i user rpc to ios push, some error will happen:
err gob: type payload.Payload has no exported fields
err gob: type not registered for interface: payload.aps
err gob: type not registered for interface: payload.Payload
so i fix the bug