-
Notifications
You must be signed in to change notification settings - Fork 86
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
Actionsheet covers up screen behind it #2103
Comments
please share the full contents of your |
Hello, @rajat693 . Here it is:
|
@rajat693 hey, Rajat! Is there anything else you'd need? |
If you're using KeyboardAvoidingView, try adding pointerEvents="box-none". |
@zainkhas thanks for you suggestion! Unfortunately that didn't work. @rajat693 Here's the structure of the host screen:
The Actionsheet lives inside the ConfigurationInput component. Here's its code:
|
Hi @ydlooming, I tried to debug your issue, but it works fine for me. I'm attaching the GitHub repo below. If you still have issues, please share a GitHub repo or a minimal codebase that demonstrates the problem. |
@rajat693 ok, so it turns out you shouldn't put a |
Description
When opening an Actionsheet, instead of fading the background, it covers it up completely. Select works fine in the same setup.
CodeSandbox/Snack link
No response
Steps to reproduce
Expected: the action sheet appears with a semi-transparent backdrop, still showing the content behind it.
Actual: there is some view behind the backdrop which covers up the screen behind it.
This same setup works fine with Select. Here is a screenshot, inspecting the backdrops of both components:
![Screenshot 2024-04-29 at 18 38 16](https://private-user-images.githubusercontent.com/147612411/326503152-c98f4d5f-e342-4bcb-9fad-df11bcf90a29.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTg5MDA3NjYsIm5iZiI6MTcxODkwMDQ2NiwicGF0aCI6Ii8xNDc2MTI0MTEvMzI2NTAzMTUyLWM5OGY0ZDVmLWUzNDItNGJjYi05ZmFkLWRmMTFiY2Y5MGEyOS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNjIwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDYyMFQxNjIxMDZaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1kMzU2MWViYTRmZmQ1NjBhODNmNzU3Nzg1Y2VlMjZmMjRhM2QwNGRlYjZjNmM2NTA0NDgyNjVmNWI2YzEzZmQzJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.QPe6Id9U97-s3SFaRURRr7dtBHO9Hx1cI2bD5upjq6I)
gluestack-ui Version
1.1.22
Platform
Other Platform
No response
Additional Information
I also tried taking the Actionsheet out into the main screen that hosts the mapped buttons, but that didn't work either.
The text was updated successfully, but these errors were encountered: