Pocketcasts STILL not syncing and still no solution?

Also looking for a solution. Pocket Cast is not working with Sonos 11/16/25

Pocket Casts integration just stopped working for me as well

Has anyone done what ​@controlav suggested?

Yeah there are multiple posts over on their support forums, as well as here, going all the way back to the re-engineering of the sonos app. As you might expect both companies essentially point the finger at the other. They really need to hop on a bridge call together, potentially with some of the impacted end users, and try to work it out from both sides. It’s very frustrating as it seems to me neither one has much of an incentive to dig very deeply.  

As a work-around, ios users can use the airplay functionality, and android users can use the (paid) app ‘Air Music’ from the play store to stream the audio directly from the phone, which is far from ideal but does work relatively well.

As he suggests, PockeCasts owns the process of syncing the data, not Sonos. 
 

If you read the documentation at the Sonos partners page, as ​@controlav has done (having written his own interface for Sonos’ system), you’ll find that Sonos writes the API that others use, and each ‘plug in’ streamer owns the data. Sonos doesn’t have access to PockeCast’s code, nor their servers, so asking them to ‘do’ something seems challenging. 

This reads like it’s from a Sonos employee who doesn’t want to take responsibility. It is Sonos’ responsibility to get this working for their users, regardless of whether the problem is on Sonos’ or PocketCasts’ end. Sonos needs to communicate with Pocket Casts and figure it out. 

Just to FYI the account isn’t an official Sonos account.

Pocket Casts has had issues on Sonos ever since the May 2024 update. It was indeed a Sonos-related problem, but given how long it’s been, it might be best to switch to a different podcast solution at this point.

Nor am I a Sonos employee. Just relating the facts as I understand them. There’s no requirement for you to like them.

Sonos may or may not have already communicated with PocketCasts, we will never know (Sonos doesn’t disclose internal and/or 3rd party communications).  This is neither here nor there when you know that 1) Sonos has no way of forcing PocketCasts to do anything due to the terms of their agreement, and 2) Sonos has no financial relationship with PocketCasts, so unlike an actual listener/subscriber, Sonos has no leverage.  

Given the above, it has always been the suggestion of Sonos that although lobbying here may seem the most logical, it is far more effective to lobby the service itself directly.  

Some light reading (if you care to): https://docs.sonos.com/docs/how-sonos-works

One would think Sonos’s leverage over Pocket Casts is the threat of pulling it from the platform and with it access to millions of households, but maybe that’s not the case. (or maybe Sonos isn’t motivated to do this)

I think the fact that Sonos and PocketCasts have zero financial relationship has a large factor here, although there certainly could be a large distribution network via Sonos. We don’t have access to those numbers, nor do we know of the communications between the two companies. 

Don’t bother.  It’s something we’ve seen many times before, it’s best not to take the bait.  

My current theory is that double NAT could be causing issues with Pocket Casts and other apps like Plex updating in the Sonos app. Could that be the issue? I have a router performing router functions connected to a T-Mobile gateway that can’t be placed into bridge or modem only mode. Even thoughthe Wifi functions of the gateway device are turned off So even though it’s kind of a pain putting the router in access point mode would eliminate the issue of multiple devices performing DHCP, I’m reading. 

I don’t know if double NAT could cause the pocket cast issue for some people, but double NAT can absolutely cause issues with Sonos, especially around discovery, control, and “missing” devices in the app.