We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi! 👋
Firstly, thanks for your work on this project! 🙂
Today I used patch-package to patch [email protected] for the project I'm working on.
[email protected]
We've seen a strange behavior that an empty bottom sheet has been displayed after the app resumed from the background with a different orientation.
Steps to reproduce:
Here is the diff that solved my problem:
diff --git a/node_modules/stream-chat-react-native-core/src/components/AttachmentPicker/AttachmentPicker.tsx b/node_modules/stream-chat-react-native-core/src/components/AttachmentPicker/AttachmentPicker.tsx index 2399593..4d46a64 100644 --- a/node_modules/stream-chat-react-native-core/src/components/AttachmentPicker/AttachmentPicker.tsx +++ b/node_modules/stream-chat-react-native-core/src/components/AttachmentPicker/AttachmentPicker.tsx @@ -264,7 +264,7 @@ export const AttachmentPicker = React.forwardRef( return ( <> <BottomSheet - containerHeight={fullScreenHeight} + // containerHeight={fullScreenHeight} enablePanDownToClose={true} handleComponent={ /**
This issue body was partially generated by patch-package.
The text was updated successfully, but these errors were encountered:
Hey @andreicrat, do you see how containerHeight would cause a problem here?
containerHeight
Sorry, something went wrong.
No branches or pull requests
Hi! 👋
Firstly, thanks for your work on this project! 🙂
Today I used patch-package to patch
[email protected]
for the project I'm working on.We've seen a strange behavior that an empty bottom sheet has been displayed after the app resumed from the background with a different orientation.
Steps to reproduce:
Here is the diff that solved my problem:
This issue body was partially generated by patch-package.
The text was updated successfully, but these errors were encountered: