Indexing errors show up as indexing not supported

[jryans]

We should refine our error handling for event indexing. At the moment, if you have some error such as:

EventIndex: Error initializing the event index {"message":"Error opening the database: IndexError(IOError(IOError { path: None, err: Custom { kind: Other, error: \"Invalid MAC\" } }))"}

the Settings UI manifests this as if you are on web / a platform that does not support indexing at all:

At the very least, Settings UI should reflect that indexing is supported on your platform, but some error has occurred. Even better would be highlighting the error details as well.

[thomasfrobieter]

I still get:

Error opening the database: IndexError(IOError(IOError { path: None, err: Custom { kind: Other, error: "Invalid MAC" } }))

In Element Desktop (Win 10):
Version von Element: 1.10.1
Version von Olm: 3.2.8

UPDATE: Fixed by resetting the search-index with the button right under the error message in the Element > Security settings.