高昇

> > > @dppo 点击按钮能明显感觉到有点卡顿，可能是由于拦截的缘故。 > > > > > > 但是我代码并没有处理拦截返回的操作只是设置了Navigator.setInterceptor，但是返回时并没有走这个方法啊。 > > 额，对，是没走。走的是原生通道，照理说不会卡才对。 在页面有webview时挺明显的，如果直接调用代码返回`props.navigator.pop();`，就挺顺畅的。

same issues 7.15.0

Similar problem happening on android with fabric enabled ` "@react-navigation/native": "^6.1.6", "@react-navigation/native-stack": "^6.9.12", "react": "18.2.0", "react-native": "0.71.7", "react-native-safe-area-context": "^4.5.2", "react-native-screens": "^3.20.0" `

When update react-native-reanimated to 3.0.1 It seems to have solved this problem

"react-native": "0.71.3", "react-native-screens": "^3.20.0", use new arch There is still this problem

react-native version is 0.71.3 and use new arch

when i set top ActionSheet context = 'global' , This problem seems to be solved But I don't know if there are other problems with this setting new sheetStacks logs...

This can be a temporary fix ``` diff --git a/dist/js/tracing/timetodisplaynative.js b/dist/js/tracing/timetodisplaynative.js index 23b433f6956dc03ed3a5ecc84635bb2bfbba03ca..cafd5143f62c4df8fccc512c44257b8207a828f5 100644 --- a/dist/js/tracing/timetodisplaynative.js +++ b/dist/js/tracing/timetodisplaynative.js @@ -1,5 +1,5 @@ import * as React from 'react'; -import {...

same problem.