-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Unknown Error Occurs on Topic Subscription #242
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
Comments
rsattar
added a commit
to firebase/firebase-ios-sdk
that referenced
this issue
Aug 30, 2017
This should address the issue filed at: firebase/quickstart-ios#242, where a topic name containing a `%` character was failing. It turns out that the topic name was never being url-encoded.
Apologies for the late response, this is fixed in firebase/firebase-ios-sdk#220, and should be out in an upcoming release of Firebase. If you have more bugs to file about the SDK itself, please file them at https://github.com/firebase/firebase-ios-sdk/issues, instead of in quickstart-ios. Thanks! 👍 |
rsattar
added a commit
to firebase/firebase-ios-sdk
that referenced
this issue
Aug 30, 2017
This should address the issue filed at: firebase/quickstart-ios#242, where a topic name containing a `%` character was failing. It turns out that the topic name was never being url-encoded.
minafarid
pushed a commit
to minafarid/firebase-ios-sdk
that referenced
this issue
Jun 6, 2018
This should address the issue filed at: firebase/quickstart-ios#242, where a topic name containing a `%` character was failing. It turns out that the topic name was never being url-encoded.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Firebase version: 3.15.0
Firebase Messaging version: 1.2.2
iOS version: 9+
Xcode version: 8.2.1
I have tried to subscribe to a topic named something like
sport|baseball
and since the SDK only allows [a-zA-Z0-9-_.~%], I encoded the name intosport%7Cbaseball
. This works on Android; however, on iOS, it doesn't work. It showed following message on debuggerand messages could not arrive.
Currently, our workaround is replacing
|
with_
.The text was updated successfully, but these errors were encountered: