Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Before this change, the probing flow always returned success for any sent probe. Now it uses the
paymentIdsfrom the returned probe handles, waits for matching.probeSuccessful/.probeFailedevents, and updates the UI to use the actual result.Details
LightningService.sendProbereturns dispatched probepaymentIds (ProbeDispatch).WalletViewModel.waitForProbeOutcomematches on those IDs, uses a small in-memory cache so events aren’t missed between dispatch and registering the listener, clears cache on node stop / wipe.Needs synonymdev/ldk-node#77
Screenshot / Video
Simulator.Screen.Recording.-.iPhone.17.-.2026-04-08.at.18.48.21.mov