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
All of a sudden the hot code reload fails and no more changes are pushed. That usually means that I screwed something up. If I reload the emulator I just get Waiting for Figwheel to load files. The figwheel REPL shows nothing and a (reset-autobuild) successfully recompiles the project.
It is like these issues fall between compile issues shown by figwheel and the red screen of RN. I have not got around to make an MWE but an example issue is when I accidentally ran the function r/adapt-react-class twice on an object.
Not sure if this issue is related to re-natal but I never experienced them in React Web.
The text was updated successfully, but these errors were encountered:
Yep, I could reproduce it and fixed. The problem was in case of debugging in chrome erors thrown by importScripts function were not logged at all. No errors logged - no red screen.
I also removed some error messages which did not look very useful. You can just patch your figwheel-bridge.js for now until this fix is released.
reagent6, iOS, Mac
TLDR: Some RN errors are not reported anywhere
All of a sudden the hot code reload fails and no more changes are pushed. That usually means that I screwed something up. If I reload the emulator I just get
Waiting for Figwheel to load files
. The figwheel REPL shows nothing and a(reset-autobuild)
successfully recompiles the project.It is like these issues fall between compile issues shown by figwheel and the red screen of RN. I have not got around to make an MWE but an example issue is when I accidentally ran the function
r/adapt-react-class
twice on an object.Not sure if this issue is related to re-natal but I never experienced them in React Web.
The text was updated successfully, but these errors were encountered: