So I just tried to save a playlist after adding some song, but it just stopped working giving the following error. It did work earlier today.
The whole server went down for a second earlier but came back on refresh. Is there some work going on or is something else the issue?
Comments
There's no work going on right now. Is this a new playlist?
As a workaround, does it show the play queue in the Web app - could you save from there?
It's not new. But both overriding the old one and saving under a new name doesn't work. Error is the same both ways.
It doesn't load on the web player I fear.
I used the web player to listen then added it on the app. It seems the web player saved the songs I listened to there as last playing.
I spend a few hours curating which songs to add, which are now over 100 extra songs, bringing it to 534 songs in total. They're so placed chronologically based on artist then release date, so it's also not easy to just write those songs down. I'm kinda fearful to close the app and loose the work.
Had a very similar error last night. Playlist was getting javascript errors and pathing errors, even though I never changed the original playlist filepaths. Did the same thing Cambionn did - override the original playlist with the updated one, removed it, then re-imported into the Astiga web player. It looks like it's working now.
Was there a server issue last night? When I tried logging into Astiga community or the web player I kept getting 404 page errors and I assume this is why it wasn't correctly fetching the playlist.
I managed to get the playlist in the webbrowser and save it from there!
The app however still gives me that error. But at least I don't have to worry about loosing that playlist. Might test later if tge issue persist with other playlists.
Was there a server issue last night?
Yes, this was rectified around 16:00 BST.
@Cambionn The play queue in the database was last updated last night at 22:53. The first track does look like the one in your screenshot. I've copy and pasted the queue so you won't lose it - but was this created on the Web or the app?
Like I said, I could save the queue now after it showed up on the website, which I did. So no more fear of loosing it.
Saving the queue as playlist from the app is what didn't work.
Thanks, will check this.
When I try this locally, it works. Are you able to try to replicate again, and I can take a look at the server logs?
The issue is still there I fear. I just tested again today.
The issue doesn't appear when I add a new playlist. It was fine on this one too until adding more songs. I wonder if the size (530+) has anything to do with it. Smaller playlists work fine.
Can you tell me the time you tried? Or try again and let me know the time?
Just tried again. 12:49 Dutch time.
Thanks!
Ok, I think I can see the request being sent. I'll try to replicate tomorrow.
Replicated - you were correct, the playlist was too long. Fix will be in the next build (we'll fix it on the server).