Skip to content
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

Flyout no longer launches #13475

Closed
TatianaKapos opened this issue Jul 19, 2024 · 1 comment · Fixed by #13476
Closed

Flyout no longer launches #13475

TatianaKapos opened this issue Jul 19, 2024 · 1 comment · Fixed by #13476
Assignees
Milestone

Comments

@TatianaKapos
Copy link
Contributor

Problem Description

Seen on both main and 0.75-branch, Flyout gives an error message when trying to launch.
image
image

Steps To Reproduce

  1. Run playground on main or the 0.75-stable branch
  2. Open rntester and navigate to Flyout Page

Expected Results

Flyout should launch

CLI version

npx react-native -v

Environment

npx react-native info

Community Modules

No response

Target Platform Version

10.0.22621

Target Device(s)

Desktop

Visual Studio Version

Visual Studio 2022

Build Configuration

Debug

Snack, code example, screenshot, or link to a repository

No response

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs: Triage 🔍 New issue that needs to be reviewed by the issue management team (label applied by bot) label Jul 19, 2024
@TatianaKapos TatianaKapos self-assigned this Jul 19, 2024
@Yajur-Grover
Copy link
Contributor

This is the issue tracking adding tests for launching a Flyout/Popup which would capture this scenario in the future: #11102.

@chrisglein chrisglein added this to the Next milestone Jul 22, 2024
@chrisglein chrisglein added Area: Flyout and removed Needs: Triage 🔍 New issue that needs to be reviewed by the issue management team (label applied by bot) labels Jul 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants