RocketChat / RocketChat/Rocket.Chat.ReactNative
bug: app V4.67.0 on Android 13 and older can not connect to rc-instance with current certificate (while Browser on same device can)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.4k
- Forks
- 1.5k
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 90
Description
Describe the Bug
Hi RocketChat-team,
the current Rocket.Chat.ReactNative-app V4.67.0 on Android 13 and older can not connect to a RocketChat-instance with current certificate saying "invalid url" while a browser like firefox on same device has no problems.
The issuer of the certificate is harica, which is the current certificate authority for GÉANT the european research communities (universities etc.).
We tried different certificates (ec/rsa) with different sizes etc.
Is there a work around this?
Or will there be a version of the Rocket.Chat.ReactNative-app with a current own list of certificate chains?
regards
Steps to Reproduce
Trying to connect to a server as described above.
Expected Behavior
Problem free TLS-connection to the Server
Actual Behavior
the current Rocket.Chat.ReactNative-app V4.67.0 on Android 13 and older can not connect to a RocketChat-instance with current certificate saying "invalid url".
Rocket.Chat Server Version
7.7.9
Rocket.Chat App Version
V4.67.0
Device Name
Multiple Android phones like Huawai, Google Pixel
OS Version
at least Android 13 and older
Additional Context
browsers like firefox on same device have no problems.
The issuer of the certificate is harica, which is the current certificate authority for GÉANT the european research communities (universities etc.).
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
No source file, test, or entry point is named. Start by reproducing the Android 13-and-older connection failure with Rocket.Chat.ReactNative V4.67.0 against the stated certificate, then trace where the app reports "invalid url" during TLS setup; done means the app connects successfully to the Harica-certified server.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, react-native, typescript
- Domain
- mobile, networking, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100