You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a UWP application, and it has certain component that uses React Native windows.
All the UI components we have in the React Native Windows component are from the package "react-native"
The goal was to use the Callout component together with the React native components that are already being used in order to show an FRE (did not find any suitable component in React Native, hence tried the Fluent UI library).
Actual behavior
However, while trying to use the Callout component, received the following error in the debugger:
RCTCallout not found in the UI Manager.
Expected behavior
Should have seen the Callout component in the UI.
I should have looked something like this (image taken from the official docs):
The text was updated successfully, but these errors were encountered:
Willing to submit a PR to fix?
Requested priority
Blocking
Products/applications affected
Microsoft To Do (Universal)
Package version(s)
"@fluentui/react-native": "0.35.7" (npm)
OS version(s)
No response
Platform
Xcode version
No response
Please provide a reproduction of the bug
We have a UWP application, and it has certain component that uses React Native windows.
All the UI components we have in the React Native Windows component are from the package "react-native"
The goal was to use the Callout component together with the React native components that are already being used in order to show an FRE (did not find any suitable component in React Native, hence tried the Fluent UI library).
Actual behavior
However, while trying to use the Callout component, received the following error in the debugger:
RCTCallout not found in the UI Manager.
Expected behavior
Should have seen the Callout component in the UI.
I should have looked something like this (image taken from the official docs):
The text was updated successfully, but these errors were encountered: