Error setting property 'fill' of RNSVGGroup with tag #125: JSON value '4294967295' of type NSNumber cannot be converted to NSArray

Hello, after upgrading react native and the node modules to latest I am having a very strange error when starting the app. From the iOS logs:

2020-06-16 23:10:30.902 E  AppName[65398:ccb98] [com.facebook.react.log:native] Error setting property 'fill' of RNSVGGroup with tag #125: JSON value '4294967295' of type NSNumber cannot be converted to NSArray
2020-06-16 23:10:30.913 E  AppName[65398:ccb98] [com.facebook.react.log:native] Error setting property 'fill' of RNSVGGroup with tag #125: Too few elements in array (expected at least 5): (null)

In the simulator:

React native info output:

System:
    OS: macOS Mojave 10.14.6
    CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
    Memory: 3.31 GB / 32.00 GB
    Shell: 5.3 - /bin/zsh
  Binaries:
    Node: 10.16.0 - /usr/local/Cellar/node/12.4.0/bin/node
    Yarn: Not Found
    npm: 6.9.0 - /usr/local/bin/npm
    Watchman: Not Found
  Managers:
    CocoaPods: 1.7.5 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 12.2, macOS 10.14, tvOS 12.2, watchOS 5.2
    Android SDK:
      API Levels: 28, 29
      Build Tools: 28.0.3, 29.0.0
      System Images: android-27 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom, android-28 | Google Play Intel x86 Atom, android-29 | Google APIs Intel x86 Atom, android-29 | Google Play Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: 3.4 AI-183.6156.11.34.5522156
    Xcode: 10.2.1/10E1001 - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_212 - /usr/bin/javac
    Python: 2.7.16 - /usr/local/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.13.1 => 16.13.1
    react-native: ^0.63.0-rc.1 => 0.63.0-rc.1
  npmGlobalPackages:
    *react-native*: Not Found

I couldn’t find a similar issue anywhere else and am not sure whether this is a react-native-svg problem.

[doumart]

I’m having this too on react-native-svg@11.0.1 If I revert to 11.0.0, all works

[WoLewicki]

@koloff @jkoutavas @doumart @isotopeee @jorgegvallejo do you have a reproduction of the issue? It is hard to tell anything without it.