I think it’s useful.
So from this I can see the request made it to the MusicBrainz server (the call didn’t fail) and the request was not entirely rubbish, because it got a “successful” unauthorised exception. So it looks like the submission token is incorrect.
This could either happen because the MB server is having some intermittent issue, where
- it fails to correctly validate a validly issued token
- it issues bad tokens
Or it could be some flow issue on my side where sometimes it keeps an expired token etc.
I’ll do two things but it may take me a day or two as I’m a bit busy.
- Expose the rejection reason in a failed submit, somewhere easier to access.
- Add a way to submit an redundant edit (e.g. all the ISRCs are already attached – it currently stops you doing this). This would allow testing of the authorisation more easily, cause right now, I can’t login 10 times and test the token is correct each time, since I have to keep finding releases with unattached ISRCs.