Haptic player error

[Sjmarf]

Got this when switching back to Mlem from another app

Optional(Error Domain=com.apple.CoreHaptics Code=-4810 "(null)" UserInfo={Error =_player != nil}) (Mlem/HapticManager.swift, startEngine():51)

[EricBAndrews]

Did haptics continue to work after this error?

[Sjmarf]

Didn't check, sorry :/

[EricBAndrews]

I'm having some trouble getting this to happen--I think it's probably one of those things where you have to catch the engine in just the wrong state. If the haptics continue to work, we should just silence the error so it doesn't pop a toast; otherwise the engine needs some more sophisticated failure recovery

[EricBAndrews]

I got a repro! Haptics stop working after this error occurs.

[EricBAndrews]

Moving this off 2.0 because #1829 should at least band-aid fix it, and even if it doesn't the error is super rare and doesn't break core functionality (if a user needs those haptics, they can always just restart the app).

Keeping this issue open until either we figure out the root cause or it doesn't show up for long enough that we can call it squashed.