-
Notifications
You must be signed in to change notification settings - Fork 30
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
Make "Uncategorized" channel *REAL* uncategorized #46
Comments
@lgxz Avoid illegal channels that have been used, so the uncategorized channel is the default channel. If you modified the server code, you can add default channel for uid. Thanks |
Yes. The problem is that the messages will be invisible in App completely if I sent messages without any channel information. The App only shows the number of unread messages. And, you can't get rid of the unread number from App forever. |
Server will add default channel. https://github.com/chanify/chanify/blob/e251ca1c307b6414c0978273d0b74e14706121ba/model/token.go#L64 How did you modify the code? Thanks. |
Great. Sorry, I don't know how to paste formatted code.
|
Ok. Here is the commits: https://github.com/lgxz/chanify/commit/002f2066e7ad02a91cb914a15c841ece304d235a |
m := &Message{}
m.From = tk.GetNodeID()
m.Channel = tk.GetChannel()
m.TokenHash = tk.HashValue()
Thanks |
Thanks. The message can be displayed in iOS Notification Center correctly even without the From field. |
Without the You can add defaultChannel, then client will work. |
Thanks. Just tried it, same result. The messages are still invisible in App. Edit: |
I suggest you to set The
Thanks |
The defaultChannel is an unnamed system channel. Messages sent to the defaultChannel will be put in the uncategorised channel by client app. But, if you set the "Name" property of defaultChannel, this will force client app create an unnamed system channel.
Thanks. What is an "invalid channel"? |
This is the commit to send categorised message to user directly: We do not need to know the channel token of every client. By "curl https://server/.../msg?chan=Event&code=100", the clients will create "Event" channel automatically and put message in it. |
v1.2.2 release |
The so-called "Uncategorised" channel is indeed a NORMAL channel and has it's own Token.
I modified the server code to send message with uid instead of the channel token. for example,
https://test.server/v2/sender/:uid/:msg
Then the funny thing is:
Screenshot
The text was updated successfully, but these errors were encountered: