-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
SVG Component Showing Blank After Updating to Version 15.4.0 #2449
Labels
Comments
Did you try to update to 15.5.0 version? I saw this in changelog #2345 |
jakex7
added a commit
that referenced
this issue
Sep 18, 2024
…ty (#2456) # Summary On Android when element before masked element has strokeOpacity different from 1, the paint is reused to draw an offscreen layer resulting in wrong opacity. Partially fixes (only on Android) #2449 ## Test Plan Add `stroke` and `strokeOpacity` to element directly before masked element. ## Compatibility | OS | Implemented | | ------- | :---------: | | Android | ✅ |
jakex7
added a commit
that referenced
this issue
Sep 23, 2024
# Summary Without the `maskUnits` attribute, masks may not render correctly, as seen in issue #2449. This pull request adds support for `maskUnits` and ensures proper cropping within the mask boundaries. ## Compatibility | OS | Implemented | | ------- | :---------: | | iOS | ✅ | | MacOS | ✅ | | Android | ✅ |
Hi @aljadan, |
Hello @jakex7 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
After updating to React Native SVG version 15.4.0, everything works as expected except for one specific SVG component, which appears blank
Steps to reproduce
1- Build the application for iOS/Android using version 15.4.0
2- Open the application on a simulator (both iOS and Android)
3- Observe that the SVG component appears blank
Snack or a link to a repository
https://github.com/aljadan/react-native-svg-issue
SVG version
15.4.0
React Native version
0.74.5
Platforms
Android, iOS
JavaScript runtime
None
Workflow
None
Architecture
None
Build type
None
Device
None
Device model
No response
Acknowledgements
Yes
The text was updated successfully, but these errors were encountered: