Round-trips a string and bytes through the whole chain. Exists to prove
the binding chain works, including in reverse: Rust invokes the observer
passed to probeWithObserver back across JSI while the call is still in
flight. It has no cryptographic meaning.
onProbeSignal, if given, receives that one call's own diagnostic and
nothing else. It is deliberately NOT routed through
emitCryptoSignal/onCryptoSignal: that channel is spec section 7.3's
broadcast for genuine crypto state changes (verification_requested,
trust_changed, verification_completed, unexpected_device,
key_missing), which every subscriber should learn about. This list has
twice been shorter than the union it quotes: it named three of four and
left out the one that hands a caller something no other call will, and
then it named four of five and left out the one a scanned flow produces.
CryptoSignal is the list; this is a quotation of it.
A probe's signal is a per-call diagnostic of this function, not a
crypto state change, so it must reach only the caller that asked for it --
broadcasting it made two independent callers of runProbe (e.g. the
example app's guided walkthrough and its diagnostics panel, mounted as
siblings) each see the other's signal too.
Round-trips a string and bytes through the whole chain. Exists to prove the binding chain works, including in reverse: Rust invokes the observer passed to
probeWithObserverback across JSI while the call is still in flight. It has no cryptographic meaning.onProbeSignal, if given, receives that one call's own diagnostic and nothing else. It is deliberately NOT routed throughemitCryptoSignal/onCryptoSignal: that channel is spec section 7.3's broadcast for genuine crypto state changes (verification_requested,trust_changed,verification_completed,unexpected_device,key_missing), which every subscriber should learn about. This list has twice been shorter than the union it quotes: it named three of four and left out the one that hands a caller something no other call will, and then it named four of five and left out the one a scanned flow produces.CryptoSignalis the list; this is a quotation of it.A probe's signal is a per-call diagnostic of this function, not a crypto state change, so it must reach only the caller that asked for it -- broadcasting it made two independent callers of
runProbe(e.g. the example app's guided walkthrough and its diagnostics panel, mounted as siblings) each see the other's signal too.