You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 12, 2023. It is now read-only.
null is not an object (evaluating 'RNDominantColor.getColorFromURL')
- node_modules/rn-dominant-color/index.js:9:21 in Promise$argument_0
- node_modules/promise/setimmediate/core.js:45:6 in tryCallTwo
- node_modules/promise/setimmediate/core.js:200:22 in doResolve
- node_modules/promise/setimmediate/core.js:66:11 in Promise
- node_modules/rn-dominant-color/index.js:8:11 in getColorFromURL
- node_modules/react-native/Libraries/Core/Timers/JSTimers.js:135:14 in _callTimer
- node_modules/react-native/Libraries/Core/Timers/JSTimers.js:387:16 in callTimers
- node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:425:19 in __callFunction
- node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:112:6 in __guard$argument_0
- node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:373:10 in __guard
- node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:111:4 in callFunctionReturnFlushedQueue
* [native code]:null in callFunctionReturnFlushedQueue
The text was updated successfully, but these errors were encountered:
@CharliBregnballe I experienced the same issue, and upon a bit of investigation, it turns out react native did not auto-link (despite having RN version 0.60), so I ran npx react-native link rn-dominant-color to link it manually, and voila! everything works fine. It may not help, but I just thought I'd share.
Trying to test in both bare and managed workflow expo app with RN v0.62.2. Happens in both ios and android.
Code:
Got this error:
The text was updated successfully, but these errors were encountered: