Skip to content

Conversation

@habovh
Copy link

@habovh habovh commented Oct 9, 2025

A critical issue was introduced by #505 that breaks usage of any of the following props on iOS platform:

  • permissions
  • defaultAudience
  • nonceIOS
  • loginTrackingIOS
  • tooltipBehaviorIOS

Attempting to use any of these props will trigger the following runtime native error on mount:

Thread 1: "-[RCTFBSDKLoginButtonView setPermissions:]: unrecognized selector sent to instance 0x133e15610"

This happens because the view exposed by native is not an instance of FBSDKLoginButton anymore, but a new wrapper RCTFBSDKLoginButtonView introduced in #505. Therefore, in the various RCT_EXPORT_VIEW_PROPERTY and RCT_CUSTOM_VIEW_PROPERTY macros, the view references point to the wrapper RCTFBSDKLoginButtonView which does not implement the properties itself.

This commit exposes the underlying FBSDKLoginButton property on the custom RCTFBSDKLoginButtonView wrapper, and re-exports these props as custom properties with the correct viewClass for correct static type checking.

Warning

I am not proficient in Objective-C. This should be extensively tested and checked as I might have made mistakes. Do not assume every use case has been tested!

A critical issue was introduced by thebergamo#505 that breaks usage of any of the following props on iOS platform:
- `permissions`
- `defaultAudience`
- `nonceIOS`
- `loginTrackingIOS`
- `tooltipBehaviorIOS`

This commit exposes the underlying `FBSDKLoginButton` property on the custom `RCTFBSDKLoginButtonView` wrapper,
and re-exports these props as custom properties with the correct viewClass for correct static type checking.
@stale
Copy link

stale bot commented Nov 10, 2025

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label Nov 10, 2025
@habovh
Copy link
Author

habovh commented Nov 10, 2025

This is not stale, but nobody is taking care of it. This PR very much needs to be merged.

@stale stale bot removed the wontfix This will not be worked on label Nov 10, 2025
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.

1 participant