I recently came back to Audiotool after a long time doing other things. When I went to work on a track I had published on the Flash version of Audiotool, I first got a message warning me about a "migration" and not to save if I thought something had gone wrong. Nothing seemingly had, so I went on to work on my track. Audiotool then warned me that I should save (I guess because autosaving doesn't automatically upload to the server and is only stored in local data?), so I went to save it through the Project menu.
Audiotool then - seemingly successfully - got through the "Compiling Track Data" and "Uploading" step, but as soon as the "Uploading" step completed I got an error message box saying "Sorry, something went wrong on our side" and Audiotool restarted itself. This happens every time I attempt to save. I tried changing the licensing, name, genre, permissions, basically everything in the "Edit Properties" dialog on the hypothesis that AT didn't like saving over a migrated track, but that didn't work either.
I opened the developer console to see if there were any obvious error logs associated with the failure to save and the error logs had this to say:
com.audiotool.error.DisplayableException$DefaultDisplayableException: <error.unspecific> -- com.audiotool.library.cular.BadRequestException: Track already migrated - tags: {Operation Name=FLAG_AS_NEXT_TRACK, Response Body=Track already migrated, Cular Error Message=Track already migrated, HTTP status code=400, http method=POST, request uri=http://api.audiotool.com/track/sophia_of_the_rain/flagAsNextTrack.json, Cular Incident ID=-} - could not create session - ErrId=fef81551-74b4-4008-a262-6c9346668cba
So, it seems as though AT thinks the track was already migrated from the Flash version, but there isn't actually a draft on the server associated with the changes I made to the previously-published track. I was able to work around this by copy/pasting the entire project into a new draft, but that feels kind of clunky and the messaging around this feels like it could surface the problem a little more directly.
Comments (1)
just had a similar issue...I somehow brute forced it to migrate...I wish I could say I knew what I did, but I have absolutely no idea.