I do think it is a common error that is most often solved by simply force stopping Aurora and re-launching it. As you see in the bug report that @squidf links, that poster was able to go back to their original device listing and downloads continued to work. Others got it solved by changing the language used. But what I think happens is those configuration changes essentially force-reload Aurora. Not sure though.