You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a device is advertising over dns-sd and the TX bits change (device name) a message is sent out to indicate that the old advertisement should be expired and the new one should be used.
In the current implementation of the casting app, we stop listening to updates after the discoveryDurationSeconds timeout. This causes us to miss messages and Android seems to fall back to the cached value of the DNS advertisement.
We need to change the usage pattern here so that clients stop the discovery manually after it is started and keep it active for the lifetime they need it for.
Reproduction steps
When a device is advertising over dns-sd and the TX bits change (device name) a message is sent out to indicate that the old advertisement should be expired and the new one should be used.
In the current implementation of the casting app, we stop listening to updates after the discoveryDurationSeconds timeout. This causes us to miss messages and Android seems to fall back to the cached value of the DNS advertisement.
We need to change the usage pattern here so that clients stop the discovery manually after it is started and keep it active for the lifetime they need it for.
Bug prevalence
Always
GitHub hash of the SDK that was being used
6dd5294
Platform
android
Platform Version(s)
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: