Subscribe not passing 'channel_name' on react-native
See original GitHub issueGreetings,
We’re trying to integrate pusher into our react-native app, but we’ve hit a snag. When calling pusher.subscribe('private-channel-name')
, we get a request to the authentication endpoint sent previously, but the request does not include the name of the channel.
Issue Analytics
- State:
- Created 7 years ago
- Comments:14 (5 by maintainers)
Top Results From Across the Web
android - Create notification channel react native
I'm using react-native-firebase v6 to handle push notifications. since there is no create channel id feature in this version, What is solution ...
Read more >Topic Push Notification || Subscribe & Unsubscribe ... - YouTube
In this video we are going to learn how to subscribe to Topic Push Notification in React Native. We are going to implement ......
Read more >React Native In App Purchases and Subscriptions ... - YouTube
Let's learn How to implement In-App Purchases and Subscriptions in a React Native project using RevenueCat. Enroll NOW for "The ...
Read more >Communication between native and React Native
Properties are the most straightforward way of cross-component communication. So we need a way to pass properties both from native to React ......
Read more >Context
Context provides a way to pass data through the component tree without having to pass props down ... Any component can read it,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Having the same issue. Was able to use the workaround of manually setting the content-type.
Blessaður Haukur!
We put this on hold and focused on other parts of our app for a while, but we’re going to make another attempt later this week or early next week. I’ll update this issue with more information when we’ve tried that, as it may have been fixed implicitly in the meantime.