Yeah, I don't think the native should ever fail assuming it's written properly so I don't think we should bother handling failure for now. Trying to handle failure in a damage-minimizing way actually gets messy in the case of clear/clearAll, since it's hard to know the state that the native side was in (i.e., which alarms were actually cleared from native) at the time of failure in order to maintain consistency between native and javascript's alarm storage.