Android App issues after recent app & player updates (Unifi)

I just updated my Sonos One stereo pair to firmware 94.1-75110 and have android app version 82.01.9 but the issue is still happening.

I tried rebooting the speakers after the update but am still having to kill and relaunch the app when it's been sitting in the background.

I too have this issue. It’s restricted to the latest android app (82.00.45) , apple works without issue and if I downgrade to the older Android app the problem goes away and everything works wonderfully. I’ve had a ticket ongoing with support for weeks. Initiall I was told that the sonos devices and controller all need to be on the same Vlan to work but once I manage to get the issue escalated I got some assistance. However, support consulted with the engineers who came back and said that the latest version of the app must have exposed some issue in my network. Tiis is the behaviour I consitently get with the controller on my standard vlan (wifi) and the speakers on my IOT vlan (wifi):

Open Latest version of app:

• Latest version of Apple app: Everything functions as it should
• Latest version of Android app: Everything functions as it should
• Older version of Android app: Everything functions as it should
• System browser and mDNS Discovery apps on Android can see all _sonos._tcp.local services 

Switch off wifi (while the sonos app is open):

• Latest version of Apple app: Cannot see Sonos system (as expected)
• Latest version of Android app: Cannot see Sonos system (as expected)
• Older version of Android app: Cannot see Sonos system (as expected)
• System browser and mDNS Discovery apps on Android cannot find any _sonos._tcp.local or any other services (as expected)

Switch wifi back on (while the sonos app is open):

• Latest version of Apple app: Sonos system can be seen again (as expected)
• Latest version of Android app: System reports "No products found on TNF" (Not as expected). Only closing the app and restarting it will re-establish a connection with the sonos speakers. Sometime a force stop is required.
• Older version of Android app: Sonos system can be seen again (as expected)
• System browser and mDNS Discovery apps on Android can see all _sonos._tcp.local services 

Support tell me, "Android app's cache or discovery service getting 'stuck'. Since the app relies on mDNS (multicast) to find the speakers, it sounds like the app is losing the thread and needs a hard reset to start listening again". As the _sonos._tcp.local services remain clearly visible in Android through the System browser and mDNS Discovery apps, and the old Sonos App manages to find the speakers again, it all points to an issue in the latest version of the Sonos app. This is further supported by the fact that simply closing the app and reopening will more often than not permit it to see the speakers again. However, If I connect my android phone to the IOT wifi (IOT Vlan), the speakers will reappear when the wifi is toggled with the Sonos app open. I feel I’m now being politely told to go away and no solution will be found. If anyone has found a solution I’d love to here it so I don’t have to constantly restart the app and/or force stop it.

On Android, the issue was resolved for me in v83, but has since been reintroduced in v84. Downgrading back to v83 resolves the issue. The app on iOS has not had this issue through v82, 83, or 84. Taken together, this suggests to me that it's an issue with the Android version of the app, as opposed to an issue with network configuration.

Happy to report the issue has been resolved for me in v85 of the Android app.

Recent app and player updates can sometimes introduce compatibility issues, bugs, or performance regressions. Try clearing the app cache, reinstalling the app, and ensuring your device OS is up to date. If problems persist, report details to support for investigation.

I'm sorry to report this issue was reintroduced in v86 of the Android app, and continues to exist on the current v87. This issue continues to only be present on the Android version of the Sonos app, the iOS version does not have the same issue.

Okay. I use Ubiquiti for my network, but I also use an iPhone. I refuse to put Sonos on my IoT VLAN because sometimes updates break things... This is NOT isolated to Sonos:

Apple

Ubiquiti

Microsoft

etc..

etc..

I love my music too much to be separated from it because I suddenly feel they are a security issue. Sonos has not cause a compromise to someone's network to my knowledge.

Please correct me if I am naive and wrong about this.

If you have been with Sonos from the beginning like I have, then you have certainly had a Sonos Bridge on your main network. Not your Guest network for isolation.

For Gods sake, make it easier on yourselves and put your speakers on your trusted network, so that you can enjoy your speakers instead of having so may connection issues. 

Finally, I hope that those who make the decisions, give the go ahead to implement  more security like TFA logins.

Try my Android app: doesn’t use mDNS at all (uses good old SSDP): “Phonos Ultimate” on the Play Store.

As per ​@Pools-3015 . Solution is to not segment devices from the control pane (ie put controller on same VLAN as devices), and turn off the mDNS reflector ‘hack’. Running an mDNS reflector increases the attack surface for your ‘standard’ VLAN.

In my experience, it’s always best to follow manufacturer’s (not just Sonos) guidelines for setup, as this is how the products are designed and tested. Any configuration outside of those guidelines is unsupported, you maybe lucky and find it does work with network ‘hacks’ such as mDNS reflector, but that is not how its designed to work.

Further reading if required:

https://www.derekseaman.com/2023/10/part-3-smart-home-matter-and-thread-deep-dive.html#:~:text=Do%20NOT%20enable%20any%20mDNS%20reflectors/forwarders/Bonjour%20Gateway%20on%20ANY%20network%20devices

https://vercara.digicert.com/resources/multicast-dns-mdns-amplification-ddos#:~:text=Proper%20subnet%20isolation,of%20network%20communication.