Marc Rousavy

I think this is already possible with the custom Selection Dot feature, no?

Ah whoops, I actually never tested the Android example here. The example app's setup is maybe a bit wrong...

What should I test?

> If by chance the project works for you by running it on an android device. It doesn't, that's what I was saying. I extracted this component from a private...

I already tried cleaning the `CameraBridge.h` file to not import anything at all which would resolve an import cycle, but apparently that wasn't the problem. Would it work if I...

Sorry, I must've accidentally deleted the branch when cleaning a bit. The issue is still present in the [frame-processor branch](https://github.com/cuvent/react-native-vision-camera/tree/frame-processors)

No, unfortunately I couldn't manage to get the bridging header import working. I had to manually forward-declare the Swift classes, which seems like a hacky workaround. See code [here](https://github.com/cuvent/react-native-vision-camera/blob/a0e063414ab727da2e63ab1d40b9d646bd6556d8/ios/Frame%20Processor/FrameProcessorRuntimeManager.mm#L43-L51)

Did you create two separate podspecs or did you use subspecs? I tried to use subspecs, one for the Swift code ("Core") and one for the .h, .m, .mm logic...

@yogevbd That's a good idea, what do you think about just giving the user full control via an `x` coordinate value? So: ``` popGestureX: Dimensions.get('window').width * 0.1 popGestureX: Dimensions.get('window').width *...

Makes sense to me. I think I have some time tomorrow/saturday if you're too busy to look into this yourself! @yogevbd