This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-09-02
Channels
- # bangalore-clj (4)
- # beginners (30)
- # boot (11)
- # cljsrn (11)
- # clojure (18)
- # clojure-conj (2)
- # clojure-italy (1)
- # clojure-uk (6)
- # clojurescript (14)
- # clojurewerkz (1)
- # core-async (3)
- # fulcro (14)
- # hoplon (12)
- # lumo (7)
- # off-topic (24)
- # onyx (2)
- # portkey (1)
- # protorepl (1)
- # re-frame (8)
- # spacemacs (14)
- # specter (95)
- # unrepl (14)
Hi, anyone know how to register native modules when integrating with old native apps? I have a simple view which used https://github.com/voximplant/react-native-voximplant (which have some native modules), I tried linking manually, it compiled successfully but failed at the run time, couldn’t find the native module. https://facebook.github.io/react-native/docs/integration-with-existing-apps.html
solved my problem, 🙂
What tricks do people use to get around 0x8badf00d (resource limit hit, too slow to launch) when attempting to run on iOS device?
@oskarth I’ve never hit that, but I found that :advanced
reduced my startup latency from 3 s to 2 s on an older device. You must be encountering multi-second startup timeouts? If :advanced
doesn’t fix it I wonder if it is possible to show a splash screen and then initialize React Native after the app has launched. I suspect that there is something else severely blocking startup, though that you will want to actually fix.
@mfikes thanks, this is specifically for development, and iOS seems to hit watchdog limit after 30s and shut down while it is in the process of requiring modules/assets
@oskarth Oh, I thought the watchdog was turned of when connected to an app launching via Xcode. (It has been a few years, though, since I've encountered the watchdog.)
@mfikes normally in debug mode, yes. However, we have a pesky EXC_BAD_ACCESS
bug that makes the debugger unable to run (we are running an Ethereum Go node on the device)
This might be a bug in LLDB or some (custom?) go stack management (https://github.com/status-im/status-go/issues/273 https://github.com/ethereum/go-ethereum/issues/14369)
nice!