Custom mapping not working

🐛 Bug Report

Passing a custom mapping like this doesn’t work for some reason

But passing it like this works

Custom mapping is the same for both scenarios

UI Kitten and Eva version

Package	Version
@eva-design/eva	^2.0.0-alpha.1
@ui-kitten/components	^5.0.0-alpha.1

Environment information

  System:
    OS: macOS 10.15.3
    CPU: (8) x64 Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz
  Binaries:
    Node: 13.9.0 - ~/.nvm/versions/node/v13.9.0/bin/node
    Yarn: 1.22.4 - ~/.yvm/shim/yarn
    npm: 6.14.4 - ~/.nvm/versions/node/v13.9.0/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 13.4, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
    Android SDK:
      API Levels: 27, 28
      Build Tools: 27.0.3, 28.0.3, 29.0.3
  IDEs:
    Android Studio: 3.5 AI-191.8026.42.35.6010548
    Xcode: 11.4/11E146 - /usr/bin/xcodebuild
  npmPackages:
    react: ~16.13.1 => 16.13.1 
    react-native: https://github.com/expo/react-native/archive/sdk-37.0.1.tar.gz => 0.61.4 

[artyorsh]

it should pointed out in the docs as a side note that the custom mapping must not to be used

That is what I did 🙌

[artyorsh]

@KaKaVip yep, thanks for the details. I fixed that in d120d5d. This is an upcoming change anyway, but if you need to use it currently, this may achieved by modifying props like the migration guide says. Sorry for such type of issue.

@gabrielepmattia thanks for the details 👍The commit above also gives some notes on this. The problem is you use metro configuration which creates a styles during the build time. customMapping property is not required in this case as it is completely ignored. What you can do is modifying your metro.config.js with.

const evaConfig = {
  evaPackage: '@eva-design/eva',
  customMappingPath: './path-to/custom-mapping.json', 
};

Maake sure to restart the bundler afterwards.