59641d7987
Summary: On Flipper Desktop, rawCall uses sendExpectResponse from the client connection. RSocket only rejects the promise if there's an error in the transport layer and thus is unable to send data over the wire. WebSocket sends without errors as errors will always be reported via a different callback api. Having said that, WebSocket client connections were rejecting the promise for a valid client response that contained an error instead of success, which in this specific case is expected. The solution is to always resolve the promise with the response and let the Client interpret the response accordingly. Changelog: Fixes an issue whereas client errors were erroneously disconnecting a client from the Desktop side Reviewed By: aigoncharov Differential Revision: D32983969 fbshipit-source-id: 4215d9234235a9e2035b1d743c317ebdf2f656a2
flipper-server-core
Package that manages connections with flipper clients, queries for adb/idb clients, accepts incoming websocket / rsocket connections and takes care of certificate exchange.
Used by Flipper desktop, flipper-server and flipper-dump