-
Notifications
You must be signed in to change notification settings - Fork 429
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
Speculative password import prompt crash fix #3569
Closed
Closed
Conversation
This file contains 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
6 tasks
amddg44
approved these changes
Nov 13, 2024
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.
The unit tests timed out on the first pass (unrelated to this), all good on the second run
graeme
added a commit
to duckduckgo/BrowserServicesKit
that referenced
this pull request
Nov 14, 2024
Please review the release process for BrowserServicesKit [here](https://app.asana.com/0/1200194497630846/1200837094583426). **Required**: Task/Issue URL: https://app.asana.com/0/1203822806345703/1208648341254407/f iOS PR: duckduckgo/iOS#3569 macOS PR: duckduckgo/macos-browser#3542 What kind of version bump will this require?: Patch **Description**: There's a crash in moderate numbers which is occurring during the password import prompt flow. This is speculative fix for that. The reason seemed to be that the `replyHandler` was being called too many times. However: - The docs for `userContentController:didReceiveScriptMessage:replyHandler:` say " The replyHandler can be called at most once. If the replyHandler is deallocated before it is called, the Promise will be rejected with a JavaScript Error object with an appropriate message indicating the handler was never called." - In the case of `startCredentialsImportFlow` where the crash is occurring, the JS is not awaiting. So there is no need to call the replyHandler. **Steps to test this PR**: Just smoke tests for the feature: https://app.asana.com/0/1142021229838617/1208543152554655/f **OS Testing**: * [ ] iOS 14 * [ ] iOS 15 * [ ] iOS 16 * [ ] macOS 10.15 * [ ] macOS 11 * [ ] macOS 12 --- ###### Internal references: [Software Engineering Expectations](https://app.asana.com/0/59792373528535/199064865822552) [Technical Design Template](https://app.asana.com/0/59792373528535/184709971311943)
This PR was superceded already and BSK has been updated. So I'll just close |
mgurgel
pushed a commit
to duckduckgo/BrowserServicesKit
that referenced
this pull request
Nov 18, 2024
Please review the release process for BrowserServicesKit [here](https://app.asana.com/0/1200194497630846/1200837094583426). **Required**: Task/Issue URL: https://app.asana.com/0/1203822806345703/1208648341254407/f iOS PR: duckduckgo/iOS#3569 macOS PR: duckduckgo/macos-browser#3542 What kind of version bump will this require?: Patch **Description**: There's a crash in moderate numbers which is occurring during the password import prompt flow. This is speculative fix for that. The reason seemed to be that the `replyHandler` was being called too many times. However: - The docs for `userContentController:didReceiveScriptMessage:replyHandler:` say " The replyHandler can be called at most once. If the replyHandler is deallocated before it is called, the Promise will be rejected with a JavaScript Error object with an appropriate message indicating the handler was never called." - In the case of `startCredentialsImportFlow` where the crash is occurring, the JS is not awaiting. So there is no need to call the replyHandler. **Steps to test this PR**: Just smoke tests for the feature: https://app.asana.com/0/1142021229838617/1208543152554655/f **OS Testing**: * [ ] iOS 14 * [ ] iOS 15 * [ ] iOS 16 * [ ] macOS 10.15 * [ ] macOS 11 * [ ] macOS 12 --- ###### Internal references: [Software Engineering Expectations](https://app.asana.com/0/59792373528535/199064865822552) [Technical Design Template](https://app.asana.com/0/59792373528535/184709971311943)
graeme
deleted the
graeme/speculative-password-import-prompt-crash-fix
branch
December 17, 2024 14:15
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Task/Issue URL: https://app.asana.com/0/1203822806345703/1208648341254407/f
Description:
Just a BSK bump for a macOS crash fix.
Steps to test this PR:
Just green CI
Definition of Done (Internal Only):
Copy Testing:
’
rather than'
Orientation Testing:
Device Testing:
OS Testing:
Theme Testing:
Internal references:
Software Engineering Expectations
Technical Design Template