Marco Izzo
Marco Izzo
After more investigation, the issues seems to be systematic on iOS 11
Workaround is to add **return nil;** on top of the inputAccessoryView inside _RNCWebView.m_ file of react-native-webview package but honestly I do not know what is the impact... I use this...
Thanks for the response @PetroPavlenko, I don't think so because that issue is on start app (mine randomly during the usage of the app) and it's related to a library...
Unfortunately I have this error also before xcode 16 and ios 17... so cannot be that one 😔
I was able to get the error during test automation process: Hope can help someone to suggest me some fix... ` The app has crashed, see the details below: Signal...
Unfortunately no... my last tentative will be in upgrading RN, but still not planned
Yes I use redux
I jumped from RN 0.71 to RN0.73.2 (upgrade also many other libraries) and now the problem seems not anymore present. ¯\_(ツ)_/¯
@lucaswitch here you are ``` { "scripts": { "android": "react-native run-android", "ios": "react-native run-ios", "start": "react-native start", "aab": "npx react-native bundle --platform android --dev false --entry-file index.js --bundle-output android/app/src/main/assets/index.android.bundle &&...