Infrastructure: Restore Storybook stories excluded by native desktop crashes
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- react-native, typescript
Research direction
Start with apps/storybook/storybook.config.mts and apps/storybook/README.md, then run the supported yarn storybook ... -- lifecycle with one excluded module at a time. Record the first native failure and story ID for each endpoint, add termination regression coverage, and remove exclusions only when the native cohorts and required checks pass.
Written by the indexing model from the issue text.
Description
Goal
Restore native Storybook coverage currently excluded because of desktop-host fail-fast crashes. Parent: #4275. Bug follow-up to the delivered endpoint/pipeline milestones #4259/#4256.
Observed state - 2026-10-01
The app's checked-in platform patterns deliberately exclude:
| Endpoint | Excluded modules |
|---|---|
| Windows Fabric | Accordion and standalone native Callout |
| Win32 Paper / REX 0.81.1 | Accordion and ListItem |
| macOS | None of these modules |
The Storybook README documents native fail-fast termination (0xc0000409) as the reason. Current main manifests contain 168 macOS, 158 Windows, and 152 Win32 stories; exclusions are real missing coverage, not equivalent catalogs.
This audit verified source/configuration and generated catalogs, not a new interactive reproduction of each crash. Reproduce against the current resolved forks before attributing a root cause; do not infer that an old runtime diagnosis still explains every endpoint.
Reproduction
On the affected native endpoint, create a minimal isolated fixture or deliberately scoped local catalog for one excluded module at a time. Use the supported yarn storybook ... --<platform> lifecycle from apps/storybook, preserve exact process identity, and retain the first actionable native failure and story ID. Do not remove all exclusions from the normal PR lane before safe per-module qualification.
Acceptance criteria
- Record a current minimal reproduction, resolved runtime/renderer/OS, first failing story, and native termination/error evidence for each excluded module/endpoint.
- Fix or consume the owning native/runtime repair without suppressing the crash, replacing the native endpoint, or claiming a render-only proxy as coverage.
- Add a regression that detects application termination as a failure and exercises the affected behavior, including delayed focus survival where relevant.
- Remove each platform exclusion only after its native story cohort passes the full owned traversal/tests and cleanup on that endpoint.
- Manifest/index checks and documentation accurately distinguish any remaining justified exclusions; require a linked issue and reason for each.
- Windows/Win32 remain separate Fabric/Paper endpoints, other platforms preserve behavior, and native/package checks and necessary changesets pass.
Coordination
Restoring Accordion coverage unblocks the original focus-survival and accessibility cohorts (#4347/#4343). Coordinate #4349 for required-pipeline qualification. Native package/component fixes may also relate to #3971/#4274, but those broader issues do not currently track these exact catalog exclusions.
- Dominant language
- TypeScript
- Stars
- 1.4k
- Forks
- 179
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 30
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/fluentui-react-native
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/fluentui-react-native#4174 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
microsoft/fluentui-react-native#4343 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
microsoft/fluentui-react-native#4345 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
microsoft/fluentui-react-native#4346 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
microsoft/fluentui-react-native#4347 ·
Maintainers usually reply within 1 day
All issues in microsoft/fluentui-react-native
Similar issues
-
Bump Firebase JS SDK (12.19.0 → 13.0.0)Possibly taken @SelaseKay claimed this today. OpenNeeds Attention type: enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
invertase/react-native-firebase#9364 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 4 days
-
e2e-failure ready-to-code
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
redhat-developer/rhdh-plugin-export-overlays#4261 · 1 comment ·
Maintainers usually reply within 1 day
-
[Bug] 官网文档的图片挂了Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
area:cli bug triage:in-progress
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day