Had this issue since i bought my kindle late last year, tried using amazon support chat to fix this, but they didnt help at all. It keeps telling me I have exceeded the device limit and I need to rebuy the dictionary, however, I neither have a device registered using this book, nor does amazoneven allow me to but it anymore.
Also, as far as I was aware, with my original kindle, it came with a dictionary built in, without having to buy one seperatly, I'm not sure if this is discontinued, not working for me, or just part of my imagination so.
I'm sorry you're having this issue! Thank you so much for including all those screenshots - they are always so helpful!
I've been doing some research, and you are not alone with this dictionary problem. Our development team is aware of, and actively working on getting this issue fully resolved. I am monitoring the situation, and as soon as I get some more details I will share them right here.
Thank you again for your understanding, and for your patience. Welcome to the forum
I'm sorry you're having this issue! I am showing this issue was resolved. I recommend making sure your Fire tablet is on the latest update. Swipe down from the top of your screen, select Settings > Device Options > System Updates.
If that doesn't get your dictionary working properly again, please reach out directly to our Kindle team (click here) so they can assist further and get in touch with our technicians if necessary. Let us know how it goes!
There hasnt been a system update since atleast december (last time mine was updated, and says theres no new update) and the issue is still going on, and last time I contacted amazon directly outside of this forum it was two hours of someone making me install a random dictionary, which yes, gave me access to the dictionary, but I still couldnt use it whilst reading another book without leaving that book.
I apologise for that last part, to fix this issue I just had to go back into my book, highlight a word, then click download dictionary, and it worked! Wish I had known that it had been fixed earlier though :(