pusher / pusher/pusher-websocket-react-native
Include custom host support in next release and fix Android Gradle build issues
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 76
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
Description
Description
Hi,
I’m using this package with Laravel Reverb, a self-hosted Pusher-compatible WebSocket server.
The latest published version (1.3.5) does not include the host, wsPort, and wssPort options added in #165, so I tested the current master version.
The custom host configuration itself works correctly, but the Android build fails because of Gradle task dependencies in the package.
For example:
Could not determine the dependencies of task
':pusher_pusher-websocket-react-native:generateDebugRFile'.
Task with path
':pusher-websocket-react-native:parseDebugLocalResources'
not found in project
':pusher_pusher-websocket-react-native'.
I also reproduced the issue after completely removing the package from node_modules and reinstalling the current master version without making any manual changes:
@pusher/pusher-websocket-react-native@1.3.5
git#afc49fa22c7c8dd279b929971db42531a8cdd5a1
The Android build fails again with the same Gradle error.
As a test, removing the related tasks.configureEach block from the package's android/build.gradle allows the Android project to build successfully, and the custom WebSocket connection also reaches CONNECTED.
Environment
- React Native:
0.81.1 - React:
19.1.0 - Gradle:
8.14.3 - Java:
21.0.6 - New Architecture: enabled
- Android compile/target SDK:
36
Request
It would be great if the next published release could include the custom host, wsPort, and wssPort support from #165 while also ensuring that Android builds successfully without requiring any changes inside node_modules.
This would make Laravel Reverb and other self-hosted Pusher-compatible servers usable with the published React Native package.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect the package's android/build.gradle and compare the current master build with the host, wsPort, and wssPort changes from #165. Reproduce the Android Gradle failure using the stated environment, then verify that the build succeeds without node_modules edits and that the custom host support is included in the published package.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, react-native, typescript
- Domain
- build-system, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 64/100