microsoft / microsoft/react-native-windows
RNW app e2e debuggability and developer engagement
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
Today an app can take RNW, modify its source, and ship it as part of their package. In the future they will likely take a drop of the RNW dlls.
Consequently, the app package that ends up in the Store, has no symbols for the app, and may not even have symbols for the RNW dlls. This is in contrast to .net UWP apps where we get symbols. It is similar to Games and other native UWP apps.
The result of this is that whenever we have a reliability bug, functionality regression, or appcompat bug, we won't be able to debug it:
- We don't have app symbols. If the app is 1st party we can pass the bug on to them. Otherwise we rely on the developer/ISV to discover this since there doesn't seem to be an outreach program that's set up.
- Even if the developer ends up getting the bug, they may not be able to debug what's going on. They'll have symbols for their own app, hopefully, as well as symbols/source for RNW. However they won't have symbols/source for WUX.
It is not unreasonable to assume that some portion of the bugs in RNW apps will be in how the RNW dll uses WUX and Comp. This is in contrast to .net UWP apps which have "rails" since they're using a well-tested mature framework like .net and there isn't much logic in .net (it just exposes the UWP apps and types), whereas RNW dlls have a bunch of logic to adapt between the WUX and RN APIs and controls.
So, as it is, my concern is that
- There is no engagement & outreach channel for RNW developers (incl access to Watson)
- Even if there were, we don't have the infrastructure in place to make these bugs actionable/debuggable.
Some of this goes away when RNW moves onto WinUI3, however that may not happen for some time.
Contributor 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.
Research direction
No files, tests, or entry points are identified in the issue. Start by mapping the proposed developer outreach channel and the symbol/source requirements for RNW, WUX, and Comp; done would require an agreed, actionable path for reporting and debugging app reliability, regression, and app-compatibility bugs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, react-native
- Domain
- developer-experience, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100