Crash on android after adding style transform

[mzaien]

Description

I have added a style to an svg illustration to flip it on english or LRT

                    transform: [{scaleX: I18nManager.isRTL ? 1 : -1}],

I solved this issue temproraly with adding different style to flip the svg

transform: [
        { rotateY: I18nManager.isRTL ? '0deg' : '180deg' },
      ]

And to be honest I'm not really sure if this is a RNSVG issue or not since there are other packages that got updated to latest e.g expo , react-native , reanimated , ...etc but I had a similar environment to the one in our company's app.

here is the error log that might help

Your app just crashed. See the error below.
java.lang.IllegalArgumentException: width and height must be > 0

Steps to reproduce

• install the repo
• do a clean prebuild
• run yarn android

Snack or a link to a repository

https://github.com/mzaien/rn-expo-75-51-svg-bug

SVG version

15.6.0

React Native version

0.75.2

Platforms

Android

JavaScript runtime

Hermes

Workflow

Expo Dev Client

Architecture

Paper (Old Architecture)

Build type

Debug app & dev bundle

Device

Android emulator

Device model

Pixel 8

Acknowledgements

Yes

[mzaien]

Seems it is the same issue that was fixed in #2424

@jakex7 can you confirm?, if so when will it be released?

[bohdanprog]

Hello @mzaien, I tried to reproduce your issue using your example, but it seems that I don't have the problem you described.

ScaleX: 1

ScaleX: -1

[arakovskis]

This PR: #2424 fixes crash, but applying these changes makes SVG not rendered at all when scaleX: -1 is applied.
RN: 0.75.2 and latest svg library version.

[bohdanprog]

@arakovskis I ran your app and those environments that you provided.

[bohdanprog]

@mzaien I ran the example that you provided again here is the screen:

[marklu]

I've also encountered this issue, with a transform scaleX: -1. My workaround was to wrap the svg in a View with the transform for now.

[jakex7]

Hi, thanks for all the reports. I was able to reproduce the bug and have implemented a fix for this issue in #2452. It will be included in the next release.

[jakex7]

It has been fixed in #2452 and included in the v15.7.1 release. If for some reason the problem has not been solved, feel free to reopen the issue.