They did find it and address it.. There is a SDK update that is manual in 2.2.8, pushing for it to be automatic in 2.2.9..
They switched databases on the SDK from a proprietary format to SQLite.. The previous format was easily corruptible.. When this happens you get craziness because the nodeId in one place doesn’t match the nodeId in another. This mainly manifests when trying to remove a failed node.
Now that being said, the update does not retroactively fix nodes that already had database corruption, but it should prevent any new corruption from forming.
