-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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: do not overwrite external inputAccessoryView
on Fabric
#48339
fix: do not overwrite external inputAccessoryView
on Fabric
#48339
Conversation
@cipolleschi sorry to tag you, but I know you do a lot of iOS stuff in react-native, so wanted to kindly ask you to review this PR 🙏 👀 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This fix looks good. Thank you for taking care of it!
@cipolleschi has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
@cipolleschi merged this pull request in 5fc5827. |
This pull request was successfully merged by @kirillzyusko in 5fc5827 When will my fix make it into a release? | How to file a pick request? |
Summary: If 3rd party libs are using `inputAccessoryView` - the current code can easily break it. Whenever props gets changed we call `setDefaultInputAccessoryView` which will simply overwrite the current `inputAccessoryView` (which is highly undesirable). The same fix on paper was made ~7 years ago: bf36983 ## Changelog: <!-- Help reviewers and the release process by writing your own changelog entry. Pick one each for the category and type tags: [IOS] [FIXED] - Fixed problem with accessory view & 3rd party libs For more details, see: https://reactnative.dev/contributing/changelogs-in-pull-requests Pull Request resolved: #48339 Test Plan: Make sure `inputAccessoryView` functionality works as before Reviewed By: javache Differential Revision: D67451188 Pulled By: cipolleschi fbshipit-source-id: bc3fa82ae15f8acedfd0b4e17bdea69cbd8c8a8d
This pull request was successfully merged by @kirillzyusko in d34032b When will my fix make it into a release? | How to file a pick request? |
Summary:
If 3rd party libs are using
inputAccessoryView
- the current code can easily break it. Whenever props gets changed we callsetDefaultInputAccessoryView
which will simply overwrite the currentinputAccessoryView
(which is highly undesirable).The same fix on paper was made ~7 years ago: bf36983
Changelog:
[IOS] [FIXED] - Fixed problem with accessory view & 3rd party libs
Test Plan:
Make sure
inputAccessoryView
functionality works as before