Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Windows 11 22/H2 and NetInfo.fetch issue
See original GitHub issueI have noted that request const state: NetInfoState = await NetInfo.fetch() seems to sometimes get stuck on latest Windows 11 22/H2. No errors thrown, it is in stuck. I say about that 1 from 5 application start get stuck.
Application get stuck on await NetInfo.fetch(), it does not get network status (i think). App continues starting when switching Windows into Flight mode.
No any issues for example in Windows 10 Pro 22/H2 19045.2251
Does anyone have noted the same issue?
Environment
Surface Laptop 4 Windows 11 Pro 22/H2 22621.900
Platforms
Windows 11
Versions
- react-native-netinfo: 9.3.6
- react-native: 0.69.6
- react: 18.0.0
Issue Analytics
- State:
- Created 9 months ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Heh, i could not managed to build release/x64 version of the example app to test it on Windows 11.
npx react-native bundlecommand may use wrong --entry-file index.js. Valid may be lib/commonjs/index.js…i do not really knowApplication seems to work now well after removing the call
co_await winrt::resume_background(). I will come back if some issues still exists.If i have the time i could test this issue also with example app with this module on Windows 11.