The error raised by JitsiMeetJS.init() is already in the state of features/base/lib-jitsi-meet so it's not a good design to store the same error in the state of features/unsupported-browser.