Possible to debug locally developed native lib without using bare workflow?

Hi all.

I’m trying to debug an issue in a RN component library I contribute to, that only appears to happen on Expo. I’ve got a local development copy of the library on my laptop, and am using yalc to “publish” to a local directory, and then adding to my expo project from there. The entry in package.json looks like this for reference:

"@react-native-community/slider": "file:.yalc/@react-native-community/slider",

What I’m not sure about is how and when edits to native code (Objective-C) are being deployed to the Expo client running on the iOS simulator. Observable behaviour suggests they aren’t. Log messages don’t appear in the console. The test case even runs with intentionally broken local Obj-C code, which makes me think the native code being run by the Expo client isn’t what I think it is.

Can anybody provide some advice on whether this is even possible? Would like to achieve it without having to switch to the bare workflow.


Expo CLI 4.2.1 environment info:
OS: macOS 10.15.7
Shell: 5.7.1 - /bin/zsh
Node: 14.5.0 - ~/n/bin/node
npm: 6.14.5 - ~/n/bin/npm
CocoaPods: 1.9.3 - /usr/local/bin/pod
Platforms: iOS 14.4, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2
Android SDK:
API Levels: 29
Build Tools: 28.0.3, 29.0.2, 29.0.3
System Images: android-29 | Intel x86 Atom, android-29 | Google APIs Intel x86 Atom, android-29 | Google Play Intel x86 Atom
Xcode: 12.4/12D4e - /usr/bin/xcodebuild
expo: ~40.0.0 => 40.0.1
react: 16.13.1 => 16.13.1
react-dom: 16.13.1 => 16.13.1
react-native: https://github.com/expo/react-native/archive/sdk-40.0.1.tar.gz => 0.63.2
react-native-web: ~0.13.12 => 0.13.18
expo-cli: 4.2.1
Expo Workflow: managed

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.