-
Notifications
You must be signed in to change notification settings - Fork 52
Description
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:
- iOS
- Android
Packages
Which packages are affected by the issue?
- @shopify/react-native-performance
- @shopify/react-native-performance-lists-profiler
- flipper-plugin-shopify-react-native-performance
- @shopify/react-native-performance-navigation
- @shopify/react-native-performance-navigation-bottom-tabs
- @shopify/react-native-performance-navigation-drawer
Environment
- I've removed the packages that I don't use
package | version |
---|---|
@shopify/react-native-performance | x.y.z |
@shopify/react-native-performance-lists-profiler | x.y.z |
flipper-plugin-shopify-react-native-performance | x.y.z |
@shopify/react-native-performance-navigation | x.y.z |
@shopify/react-native-performance-navigation-bottom-tabs | x.y.z |
@shopify/react-native-performance-navigation-drawer | x.y.z |
@react-navigation/native | x.y.z |
@react-navigation/bottom-tabs | x.y.z |
@react-navigation/drawer | x.y.z |
@react-navigation/stack | x.y.z |
react-native | x.y.z |