Update BSK with autofill 10.2.0

[daxmobile]

Task/Issue URL: https://app.asana.com/0/1206839421155398/1206839421155398
Autofill Release: https://github.com/duckduckgo/duckduckgo-autofill/releases/tag/10.2.0
BSK PR: duckduckgo/BrowserServicesKit#723

Description

Updates Autofill to version 10.2.0.

Autofill 10.2.0 release notes

What's Changed

• Remove unused Android UA check by @jonathanKingston in Remove unused Android UA check duckduckgo-autofill#494
• fix tracker radar kit reference by @brindy in fix tracker radar kit reference duckduckgo-autofill#505
• Update password-related json files (2024-03-04) by @daxmobile in Update password-related json files (2024-03-04) duckduckgo-autofill#518
• separate 'third party provider' feature by @shakyShane in separate 'third party provider' feature duckduckgo-autofill#252
• marking flaky tests by @shakyShane in marking flaky tests duckduckgo-autofill#524
• remove device-specifc 'isEnabled' checks by @shakyShane in remove device-specifc 'isEnabled' checks duckduckgo-autofill#523
• fixing some flaky tests by @shakyShane in fixing some flaky tests duckduckgo-autofill#526
• Fixes bugs for Lufthansa, Twitter, Rumble by @GioSensation in Fixes bugs for Lufthansa, Twitter, Rumble duckduckgo-autofill#529
• Update Github action dependency by @GioSensation in Update Github action dependency duckduckgo-autofill#531

New Contributors

• @brindy made their first contribution in fix tracker radar kit reference duckduckgo-autofill#505

Full Changelog: duckduckgo/duckduckgo-autofill@10.1.0...10.2.0

Steps to test

This release has been tested during autofill development. For smoke test steps see this task.

[amddg44]

@GioSensation @shakyShane it looks like there is an issue with this autofill release and email incontext signup on iOS. EmailManager.autofillUserScriptDidCompleteInContextSignup is no longer firing, so the final stage of the email sign-up and sign-in flows are broken with the Email Protection screen never getting dismissed.

I checked and there were no errors in the console, it's like a message handler just stopped firing or was possibly removed? Let me know if I can do anything to help

Simulator.Screen.Recording.-.iPhone.15.Pro.-.2024-03-20.at.17.11.15.mp4

Simulator.Screen.Recording.-.iPhone.15.Pro.-.2024-03-20.at.17.03.06.mp4

[GioSensation]

FYI, we've noticed that the native side is not sending the proper getRuntimeConfiguration in the in-context signup webview. The PR where we removed isEnabled checks is probably relying on the runtime config being present and correct, and this may cause the communication to start failing. Anya will look into this.

[amddg44]

Thanks both! The issue was indeed a runtime config support issue in the in-context webview; i've opened a PR with a fix (and I also added a debug option to reset the days since installed to 0 for ease of testing the incontext signup flow)

[GioSensation]

Nice! Thanks, Anya! FWIW, this is the options we have for email protection on Android, in case you need further inspiration.

[amddg44]

Thanks @GioSensation that is definitely inspiring! 😄