fix: animation on lock screen, replace by static fox more loader

[tommasini]

Description

Problem:
LockScreen component only triggered biometrics when AppState changed
During rapid background/foreground cycles during login, the component could mount when the app was already in 'active' state
Since no AppState change occurs (app is already active), the listener never fires
User sees FoxLoader indefinitely without biometrics being triggered

Solution:
Simplified the LockScreen component by replacing laggy Lottie animations with a static FoxLoader component to improve performance and user experience.

Changes Made

• Replaced laggy Lottie animations (wordmarkLight, wordmarkDark) with static FoxLoader component
• Removed animation-related styling and positioning code that's no longer needed
• Cleaned up unused state (ready state, animation refs, opacity Animated.Value)
• Removed unnecessary Redux connection and theme imports
• Simplified component structure while preserving authentication functionality
• Handled race condition when the app state already changed before the listener got defined.

Impact

• Improved performance by eliminating laggy animations
• Better user experience with consistent, responsive loading indicator
• Reduced bundle size by removing animation assets (to do)
• Authentication functionality remains unchanged
• No more freezing screen at the diamong due to race condition

Changelog

CHANGELOG entry:

Related issues

Fixes:

Manual testing steps

Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]

Screenshots/Recordings

Before

After

Screen.Recording.2025-09-05.at.18.28.28.mov

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.

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 272dfa1
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/177f26c9-3bb7-46c4-accf-d0c9b17fde05

Note

• You can rerun any failed steps by opening the Bitrise build, tapping Rebuild on the upper right then Rebuild unsuccessful Workflows
• 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

[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 SonarQube Cloud

[Cal-L]

Just wanted to note that this is the patch

[Cal-L]

LGTM

[vinnyhoward]

Nice fix and clean up! LGTM