Skip to content

chore(runway): cherry-pick fix: cp-7.51.2 scroll behaviour on Solana New Feature view #17813

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

Merged
merged 1 commit into from
Aug 1, 2025

Conversation

runway-github[bot]
Copy link
Contributor

@runway-github runway-github bot commented Aug 1, 2025

Description

This PR fixes the iOS-specific scrolling issue with the Solana feature
popup that was preventing users from accessing the bottom buttons. The
problem occurred when the title text spans multiple lines (particularly
in non-English languages), causing the "Not now" button to appear below
the visible screen area. While users could scroll down to reach the
button, the ScrollView would automatically snap back to the top, making
the buttons inaccessible and effectively blocking app usage.

Root Cause: The issue was caused by conflicting flex layouts where
contentContainerStyle with flex: 1 forced the ScrollView content to
always try to fill the full height, creating layout calculation
conflicts on iOS that resulted in the automatic scroll-back behavior.

Solution:

  • Replaced flex: 1 with flexGrow: 1 and minHeight: '100%' to allow
    proper content expansion without forcing full height
  • Enhanced ScrollView configuration for better iOS compatibility

Changelog

CHANGELOG entry: Fixed Solana popup scrolling issue that prevented iOS
users from accessing bottom buttons

Related issues

Fixes: #17795

Manual testing steps

  1. Open MetaMask on an iOS device (physical device or simulator)
  2. Clear the Solana feature modal storage flag to trigger the popup:
  • In developer tools, delete AsyncStorage key:
    @MetaMask:solanaFeatureModalShownV2
  • Or temporarily add
    StorageWrapper.removeItem(SOLANA_FEATURE_MODAL_SHOWN) to the component
  1. Restart the app to see the Solana popup
  2. Test with different scenarios:
  • Short title (English): Verify normal display with buttons visible
  • Long title (other languages): Change device language to
    German/Spanish/French or temporarily replace title with long text
  1. When title spans 3+ lines:
    • Scroll down to reach the "Not now" button
    • Verify content stays scrolled and doesn't snap back to top
  • Verify both "Import your wallet" and "Not now" buttons are clickable
  1. Test on both iPhone simulator and physical device for best coverage

Screenshots/Recordings

Before

After

https://www.loom.com/share/26aefcc54516462596e16fa0aa88e81d

  • Smooth scrolling behavior without snap-back
  • Bottom buttons remain accessible after scrolling
  • Consistent experience across different text lengths and languages

Pre-merge author checklist

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. e4d305d

…New Feature view (#17807)

## **Description**

This PR fixes the iOS-specific scrolling issue with the Solana feature
popup that was preventing users from accessing the bottom buttons. The
problem occurred when the title text spans multiple lines (particularly
in non-English languages), causing the "Not now" button to appear below
the visible screen area. While users could scroll down to reach the
button, the ScrollView would automatically snap back to the top, making
the buttons inaccessible and effectively blocking app usage.

**Root Cause:** The issue was caused by conflicting flex layouts where
`contentContainerStyle` with `flex: 1` forced the ScrollView content to
always try to fill the full height, creating layout calculation
conflicts on iOS that resulted in the automatic scroll-back behavior.

**Solution:** 
- Replaced `flex: 1` with `flexGrow: 1` and `minHeight: '100%'` to allow
proper content expansion without forcing full height
- Enhanced ScrollView configuration for better iOS compatibility

## **Changelog**

CHANGELOG entry: Fixed Solana popup scrolling issue that prevented iOS
users from accessing bottom buttons

## **Related issues**

Fixes: #17795

## **Manual testing steps**

1. Open MetaMask on an iOS device (physical device or simulator)
2. Clear the Solana feature modal storage flag to trigger the popup:
- In developer tools, delete AsyncStorage key:
`@MetaMask:solanaFeatureModalShownV2`
- Or temporarily add
`StorageWrapper.removeItem(SOLANA_FEATURE_MODAL_SHOWN)` to the component
3. Restart the app to see the Solana popup
4. Test with different scenarios:
- **Short title (English)**: Verify normal display with buttons visible
- **Long title (other languages)**: Change device language to
German/Spanish/French or temporarily replace title with long text
5. When title spans 3+ lines:
   - Scroll down to reach the "Not now" button
   - Verify content stays scrolled and doesn't snap back to top
- Verify both "Import your wallet" and "Not now" buttons are clickable
6. Test on both iPhone simulator and physical device for best coverage

## **Screenshots/Recordings**

### **Before**
- Recording in #17795
- Users reported scrolling down but screen automatically moving back up
- "Not now" button became inaccessible on longer text
- App effectively blocked for users with this popup

### **After**
https://www.loom.com/share/26aefcc54516462596e16fa0aa88e81d

- Smooth scrolling behavior without snap-back
- Bottom buttons remain accessible after scrolling
- Consistent experience across different text lengths and languages

## **Pre-merge author checklist**

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I've included tests if applicable
- [x] I've documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I've applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

## **Pre-merge reviewer checklist**

- [x] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [x] 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.
Copy link
Contributor

github-actions bot commented Aug 1, 2025

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.

@tommasini tommasini added the Run Smoke E2E Requires smoke E2E testing label Aug 1, 2025
Copy link
Contributor

github-actions bot commented Aug 1, 2025

https://bitrise.io/ Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: b99f8e5
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/a50ca2f4-b987-4cb9-8c61-b09fa1fa3f45

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

Copy link

sonarqubecloud bot commented Aug 1, 2025

@tommasini tommasini merged commit b1354d5 into release/7.51.2 Aug 1, 2025
45 of 48 checks passed
@tommasini tommasini deleted the runway-cherry-pick-7.51.2-1754039642 branch August 1, 2025 10:54
@github-actions github-actions bot locked and limited conversation to collaborators Aug 1, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Run Smoke E2E Requires smoke E2E testing team-runway-bot
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants