Possible reconnectWait unit mismatch on Android
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
Research direction
Start at the Android implementation of the reconnectWait and reconnectWaitMax cases shown in the issue, then verify the Java APIs' expected units. Compare that behavior with the documented seconds-based values and confirm the result using a small reconnect delay such as .reconnectWait(2). Done means both Android settings consistently honor the documented units.
Written by the indexing model from the issue text.
Description
Think i found a small issue.
reconnectWait and reconnectWaitMax appear to use different units across platforms.
They are documented as seconds, but the Android implementation passes them directly to Java APIs that expect milliseconds:
case .reconnectWait(let value):
builder = builder.setReconnectionDelay(Long(value))
case .reconnectWaitMax(let value):
builder = builder.setReconnectionDelayMax(Long(value))
Could these values need to be multiplied by 1,000 on Android?
For example, .reconnectWait(2) seems to produce a 2 ms delay on Android instead of 2 seconds.
- Dominant language
- Swift
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
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.
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
type: docs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
googleapis/google-cloud-swift#971 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
bitcoindevkit/bdk-ffi#1125 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
mozilla-mobile/firefox-ios#35743 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
manaflow-ai/cmux#13417 ·