-
Notifications
You must be signed in to change notification settings - Fork 3.2k
[Due for payment 2025-02-28] Implement the React-Native Pusher library for iOS and Android #56480
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
Hi, I'm Viktoryia from Callstack - expert contributor group - and I would like to work on this issue. |
Updates: The main difference that will result in significant code updates is the way we process events:
What I managed to do today:
The app can already initialize the pusher, subscribe to the private channel, and even receive events for it, but it can't process the events correctly because handlers need to be updated. That's what I'm going to work on next. |
That sounds like great progress, thank you! |
Updates:
|
I don't think we have anything specific to pusher, no. Here are the main things that I would test out:
I think that's generally it. |
Updates:
|
Updates:
We just need to finalize the recordings for all platforms. The PR will most likely be ready for the review tomorrow. |
The PR has been opened for the review! |
Thanks @VickyStash! Once this is deployed to production, I'm gonna keep an eye on the logs to see if it improves the connection errors we were seeing. This will be reported in #52437 |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.3-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2025-02-28. 🎊 For reference, here are some details about the assignees on this issue:
|
@tgolen Please assign me here as reviewer |
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO. |
@tgolen Bump for assignment |
@VickyStash Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@VickyStash 6 days overdue. This is scarier than being forced to listen to Vogon poetry! |
@tgolen @shubham1206agra can the issue be closed? |
After payment, yes |
@VickyStash Eep! 4 days overdue now. Issues have feelings too... |
@VickyStash Still overdue 6 days?! Let's take care of this! |
@VickyStash 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it! |
Was the payment ever finished on this @shubham1206agra? |
Oh, I think this issue is missing a Bug-Zero team member to handle the payment 😊 Let's see if I can fix that. |
Triggered auto assignment to @trjExpensify ( |
@trjExpensify welcome to this issue! All it needs is a payment to @shubham1206agra for a C+ review of the PR. Could you please help with that? |
Wagwan! On the 28th per the title, yah? |
Well, yeah... Feb. 28th 😊 This one slipped through the cracks a little so I think ASAP would be cool here whenever you can. |
Ohhhh, I can read now. Cool, cool.. Payment summary as follows:
You can go ahead and request on NewDot now! |
$250 approved for @shubham1206agra |
Uh oh!
There was an error while loading. Please reload this page.
Problem
Pusher has been having problems reconnecting on Android devices (see this GH). This keeps people from using the app properly.
Solution
After speaking with Pusher support, they recommend using their React-Native Pusher library instead of Pusher-JS for the mobile clients. We will need to continue using Pusher-JS for web and desktop clients.
This will cause some changes to our pusher libraries like
PusherConnectionManager.ts
andpusher.ts
and maybe evenPusherUtils.ts
in order to use a different lib for the mobile platforms.Issue Owner
Current Issue Owner: @VickyStashThe text was updated successfully, but these errors were encountered: