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
using "lazy" as false inside react navigation "screenOptions" navigator leads to RenderTimeoutErrors, because we cant determine where and how should we start timer
ERROR ScreenProfilerNotStartedError: TaskQueue: Error with task : No previous state was found for screen 'xyz' with componentInstanceId 0. This probably means that the navigation-start event was never recorded, while a subsequent render flow event was (render pass start, data operation profiling, etc.). You seem to have used some profiling API but likely forgot to use the 'useStartProfiler' hook to start the flow. Read the usage here: https://shopify.github.io/react-native-performance/fundamentals/measuring-render-times., js engine: hermes
Vadko
changed the title
lazy prop for react-navigation causes RenderTimeoutError
lazy=false prop for react-navigation causes RenderTimeoutError
May 5, 2023
Vadko
changed the title
lazy=false prop for react-navigation causes RenderTimeoutError
lazy=false prop for react-navigation causes RenderTimeoutError and ScreenProfilerNotStartedError
May 5, 2023
Current behavior
using "lazy" as false inside react navigation "screenOptions" navigator leads to RenderTimeoutErrors, because we cant determine where and how should we start timer
ERROR ScreenProfilerNotStartedError: TaskQueue: Error with task : No previous state was found for screen 'xyz' with componentInstanceId 0. This probably means that the navigation-start event was never recorded, while a subsequent render flow event was (render pass start, data operation profiling, etc.). You seem to have used some profiling API but likely forgot to use the 'useStartProfiler' hook to start the flow. Read the usage here: https://shopify.github.io/react-native-performance/fundamentals/measuring-render-times., js engine: hermes
Expected behavior
using "lazy" doesnt lead to the timeout
To Reproduce
Platform:
Packages
Which packages are affected by the issue?
Environment
The text was updated successfully, but these errors were encountered: