Oliver George

Running release via Xcode provides the following logging ``` 2018-12-22 15:06:45.189 [error][tid:com.facebook.react.JavaScript] Can't find variable: a 2018-12-22 15:06:45.190745+1100 FutureApp[21212:263025] Can't find variable: a 2018-12-22 15:06:45.193 [fatal][tid:com.facebook.react.ExceptionsManagerQueue] Unhandled JS Exception: Can't...

I'm not able to test just now. I need Xcode 9 to get work code building. 203 alone didn't seem to help. Haven't tried the combo.

@CalderBot Yes, the combination worked. Nice. If I understand the worker.js patch it's disabling the constantFoldingPlugin which seemed to be the bit which conflicted with the Google Closure optimised code.

Here's my workaround for the advanced compilation bug... https://github.com/condense/mercury-app/wiki/Fixing-advanced-compilation-bug

I think :infer-externs is a practical alternative to manually managing externs now. https://clojurescript.org/guides/externs

I can work around with something like: ``` yarn add react-dom # updates package.json re-natal use-component react-dom # updates .re-natal re-natal use-figwheel # updates .index.*.js ``` Not sure if this...

Wow, weird. I just checked and a fresh app doesn't fail.

(just confirming I will do my best to reproduce this so we can close as user error with confidence)

This had me stumped. Thanks for the tip.

One solution is to rely less on tooling, manually adding modules in the configuration file using `re-natal require react-navigation`. The incompatibility here is that `require-all` will remove the module if...