-
Notifications
You must be signed in to change notification settings - Fork 25
fix(wallet): say what actually happens after a send we could not confirm #1125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
romchornyi
wants to merge
5
commits into
develop
Choose a base branch
from
fix/32189-send-outcome-copy
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+87
−7
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
e467a1d
fix(wallet): say what actually happens after a send we could not confirm
jeanpierreroma 7d70df7
fix(wallet): route every send outcome through the same copy
jeanpierreroma 3a1112c
fix(wallet): promise only the retry the shipped SDK actually performs
jeanpierreroma a08edba
docs(wallet): drop the last claim that retries survive closing the app
jeanpierreroma 6270146
chore(wallet): add the broadcast-outcome strings to the source catalog
jeanpierreroma File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 Suggestion: Add translations for the new broadcast-outcome strings
Both new NSLocalizedString keys are introduced here, but the PR contains no corresponding entries in the app's .strings catalogs. As a result, non-English devices—including the Russian-locale device from support ticket 32189—fall back to the English development strings. Add the source keys to the localization pipeline/catalogs and provide translations where available so the localization portion of the fix is effective.
source:
gpt-6-astra(phase2-reviewer: general)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in
62701467a— and thank you, this was the half of the change that actually mattered for the reporter on 32189, and I had broken it myself without noticing.The keys were missing because the extraction that adds them runs during the build and rewrites all 43 catalogs, and I had been reverting that churn wholesale after every build. That is the right habit for keeping a pristine checkout clean and exactly the wrong one on a branch that introduces strings — so the code shipped localized and the catalog never heard about it.
Both entries are now in
en.lproj, in alphabetical position with their translator comments. Added by hand rather than by committing the build output, so the diff is two entries instead of a four-thousand-line reshuffle;plutil -lintpasses.English only, which looks like the convention here — recently added keys such as "The operator key is missing from the keychain…" exist in
en.lprojand nowhere else, and the other 42 locales are filled by the periodic translation pass (#1076 did 376 strings in one go). I have not invented translations: a wrong Russian string would be worse for that customer than an English one he can at least paste into a translator. If this repo expects the new keys seeded into every locale as untranslated copies, say so and I will add them.🤖 Reviewed with Claude Code
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Resolved (re-reviewed at
62701467): The two broadcast-outcome keys are now present in DashWallet/en.lproj/Localizable.strings with matching comments and exact source strings. Other locales remain for the normal translation pipeline rather than being populated with unverified translations.