|
|
Is it reporting an Easy Key exist when none should be? |
|
|
correct i can do a screen recording to reproduce the issue for you |
|
|
Screenshot 2021-08-25 230735.jpg (110,001 bytes) |
|
|
Screenshot 2021-08-25 230858.jpg (28,197 bytes) |
|
|
Was able to confirm that easy key does not currently exist despite it showing that it is. |
|
|
Was able to reproduce. Wow, I can't believe that just broke at release. I'm sure it's a simple logic error, like the Easy Key is available but the bit is flipped the wrong way, so it thinks it's not. Should be an easy fix. |
|
|
The fix was a simple missing "0" of all things. Basically, when it checks if your new key exist already, the network will either return the full key (if it existed) or a simple 0 to represent no key exist by that name. The code was checking for a blank response instead of just the plain 0. Blank response is not reliable because if the network doesn't respond, even if the key did exist, would also be blank. The zero is a real response to check against and should be fixed in the next minor release. |
- Anonymous
