Hi @morgan1er,
It’s definitely a cache issue, and it looks like the cache comes from AWS. The good new is that the feed has the correct version of the file. Regarding the site player – you can either wait for cache to be cleared automatically (for default AWS settings, it should happen in an hour), or create a new episode with the same content, and remove the old one.
Hi,
thanks for trying to help me.
It’s been more than an hour and still nothing. But I’m not surprised : this has been going since yesterday when I discovered the problem.
To try to help you, here’s what happened :
- I had several episodes with V1.mp3 online that was working normally everywhere ;
- I made changes to my audio files, so I made V2.mp3 and uploaded them in place of the V1.mp3. Everything worked fine everywhere ;
- But suddenly, I don’t know why, I discovered that Spotify was putting the V1.mp3 versions. I only had this problem on Spotify : Apple Podcasts, Deezer and all the other platforms were OK. And of course, they all have the same feed ;
- So I contacted Spotify and in the end, they told me to upload new V3.mp3 versions. So I took the V2.mp3 files, I renamed them into V3.mp3 and I uploaded them to replace the V2.mp3 ;
- But the changes didn’t appear in Spotify. So we checked and that’s when I discovered the V3.mp3 versions don’t appear on my RSS feed. And it’s been like this since yesterday.
- And to add to the mix up, I tried to make changes inside the description of the new V3.mp3 episodes, to see if they would appear. Well, those changes DO appear online, but I still have the old V2.mp3 versions.
Hope this help. Because right now, I don’t know what to do… That’s why I would like to force my RSS feed to update everything from the start.
I made some further digging and here is what I found.
In the RSS feed, the thing that is going wrong is the enclosure url referring to the V2.mp3 instead of the V3.mp3.
I use a media file prefix for Chartable that appears in the enclosure url so I tried to delete it. When the RSS feed updates after, the media file prefix doesn’t appear anymore in the enclosure url but it still refers to the V2.mp3 instead of the V3.mp3.
So I don’t know why or how, but the RSS feed doesn’t register the new V3.mp3 url that has been changed whereas all the other changes I make a registered.
It must be a bug from SSP, don’t you think ?
Hi,
still no changes…
Is there a way to manually edit the RSS feed ?I could try this at least.
Hi @morgan1er,
If you say all platforms used the correct version, and only Spotify used the old one, it’s probably Spotify’s cache, and I don’t think you can do anything here directly.
Did you try to make a completely new episode, and remove the old one?
Hi,
I’ve already tried that but Spotify admins tell me that since my RSS feed doesn’t show the new V3.mp3, they can’t do anything. I have to edit the informations inside the RSS feed first.
When I try to add or remove an episode, the RSS feed makes the change on this episode only, it doesn’t affect the other ones. The enclosure url of the V2.mp3 episodes never changes, that’s my problem.
Any idea ? Appart from deleting and recreating those particular episodes? Because I don’t want to lose all the stats associated with them.
Thanks.
@morgan1er
Just to be sure we are on the same page. As far as I understand we’re talking about episode called “TELOS A BESOIN DE VOUS”, right? If so, did you try to remove this episode completely, make completely new episode called “TELOS A BESOIN DE VOUS”, and use the V3.mp3 file there?
Not exactly. I tried 2 things:
- Putting this “TELOS A BESOIN DE VOUS” episode in draft then back to published.
- I created a whole new “TEST” episode with the V3.mp3 in draft.
But I can’t add a new published episode to my auditors just like that to debug this.
I finally manage to resolve my problem with the help of another Spotify support guy.
The problem was the media file prefix I used for Chartable. I had already tried to delete it and it didn’t change anything BUT I needed to delete it AND have Spotify force the update of my RSS feed on their side.
So now it works as it should. I won’t put back the chartable prefix for now, maybe I’ll try it again in a couple of weeks because it used to work without any problem (I still don’t know why there was a bug with Spotify to start with).
Thanks for your help anyway.
-
This reply was modified 2 years, 3 months ago by
Morgan1er.
-
This reply was modified 2 years, 3 months ago by Morgan1er.
@morgan1er,
Thanks for informing us, glad you managed to fix it!
