Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exception thrown while executing UI block: -[BlurView setOnClick:]: unrecognized selector sent to instance 0x11898b1c0 #611

Open
neeteshraj opened this issue Mar 18, 2024 · 2 comments

Comments

@neeteshraj
Copy link

neeteshraj commented Mar 18, 2024

Exception thrown while executing UI block: -[BlurView setOnClick:]: unrecognized selector sent to instance 0x11898b1c0

__44-[RCTUIManager flushUIBlocksWithCompletion:]_block_invoke
RCTUIManager.m:1211
__44-[RCTUIManager flushUIBlocksWithCompletion:]_block_invoke_2
__RCTExecuteOnMainQueue_block_invoke
_dispatch_call_block_and_release
_dispatch_client_callout
_dispatch_main_queue_drain
_dispatch_main_queue_callback_4CF
CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE
__CFRunLoopRun
CFRunLoopRunSpecific
GSEventRunModal
-[UIApplication _run]
UIApplicationMain
main
start_sim
0x0
0x0

I am using react-native 0.73.6

@DarvilCZE
Copy link

DarvilCZE commented Mar 20, 2024

Hi all,

We are having the same issue. The happens to us when the BlurView component is a direct child of some Touchable component. In our case, it was TouchableWithouFeedback.

But we found a workaround for fixing it. When we put a simple View between the Touchable and the BlurView the app doesn't crash anymore.

The initial implementation, which crashes:

<TouchableWithoutFeedback onPress={() => {}}>
    <BlurView ... >
        {...}
    </BlurView>
</TouchableWithoutFeedback>

Working implementation:

<TouchableWithoutFeedback onPress={() => {}}>
    <View>
        <BlurView ... >
            {...}
        </BlurView>
    </View>
</TouchableWithoutFeedback>

@berdyshev
Copy link

I'm experiencing the same issue. @DarvilCZE thanks for the workaround, waiting for the fix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants