Hey guys. This is unfortunately a known issue that we introduced with the 2.0.5 release; we’re working to fix it now and should have resolved this week. There are a couple others threads on the forum here where we were discussing it previously after some users brought it to our attention.
Basically since the key isn’t required for the plugin to run anyway, I’d say ignore it for now. We’ll announce here when the bug is fixed and users can go make the change at that time. But since no functionality is lost without the key active, you aren’t missing anything without it.
Hope that helps and my apologies for the inconvenience thus far. Please let me know if you have any other questions or if I can elaborate on the points above.