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

fix: "Exception thrown while executing UI block: -[rive_react_native.RiveReactNativeView setOnClick:]: unrecognized selector sent to instance" #215

Merged
merged 2 commits into from
Jan 2, 2024

Conversation

LewisYearsley
Copy link
Contributor

RE: #214

When upgrading to React Native 0.73, it seems views receive experimental and unused props from React Native. By deriving the custom view RiveReactNativeView from RCTView from React Native instead of UIView, stubs for these props are provided for free.

I have checked this makes the specific issue I'm trying to fix go away and seems to run just fine, but please help me to understand if there may be unintended consequences or a better approach that might be more suitable.

Thanks in advance!

@lorenzoangelini
Copy link

I tried the fix, and seems that it nessessary also the import
#import <React/RCTView.h>
to RiveReactNative-Bridging-Header

@LewisYearsley
Copy link
Contributor Author

Yes, seems reasonable. Thanks for pointing out and will check!

@LewisYearsley
Copy link
Contributor Author

Thanks, that's added now @lorenzoangelini

@zplata
Copy link
Contributor

zplata commented Jan 2, 2024

Thanks! We'll merge this in for our next patch release

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

Successfully merging this pull request may close these issues.

4 participants