fix: update default search engine to google

[mindofmar]

Description

1. What is the reason for the change?

We have received several reports of phishing links being the top result within DuckDuckGo's search engine when searching for official web3 sites. This is a security risk to users and creates a poor user experience if the user cannot trust the search results.

See example here. (first result is a phishing link, shown above the official Uniswap.org website)

3. What is the improvement/solution?

Switch the default search engine to Google, which shows more reliable results.

Manual testing steps

1. Go to the Explore tab
2. Run a search query using the mobile browser
3. Ensure that the Browser searches on Google instead of DuckDuckGo

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[mindofmar]

I have read the CLA Document and I hereby sign the CLA

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 8d5e6a1
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/f890c631-722b-4247-a31e-d5a4be81df65

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[vinnyhoward]

Pulled it down and works great, PR looks good as well. But I did encounter an issue where DDG would persist. I had to delete the app or the changes won't take hold.

[sethkfman]

The settings reducer needs to run through a migration on upgrade to update the default search engine property.

• Reducer
• Migration directories - app/store/migrations/index.ts

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 34fb849
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/50a4e1c5-7b6d-480d-96b2-2ec1cdfd7578

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

Tip

• Check the documentation if you have any doubts on how to understand the failure on bitrise

[mindofmar]

Hey @vinnyhoward would you mind pulling in my changes and re-trying? I've added a migration script.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: d08db0e
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/8c9f0a5e-38a4-4f5e-a881-0c77edeb0a2a

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

Tip

• Check the documentation if you have any doubts on how to understand the failure on bitrise

[Cal-L]

Failures on Bitrise not related to this PR

[Cal-L]

LGTM

[vinnyhoward]

Pulled down and tested. LGTM✅