Warning after upgrading from SDK39 to 43: "settings" is not a valid icon name for family "material-community"

Please provide the following:

  1. SDK Version: 43
  2. Platforms(Android/iOS/web/all): Android
  3. Add the appropriate “Tag” based on what Expo library you have a question on.
    material-community
    I am facing the warning after upgrading my expo sdk from 39 to 43. I spent days on google but found any answers related to this warning message. Please any idea on how to fix this? Thanks

Bellow is the warning message:

“settings” is not a valid icon name for family “material-community”
at node_modules\react-native\Libraries\LogBox\LogBox.js:118:10 in registerWarning
at node_modules\react-native\Libraries\LogBox\LogBox.js:64:8 in warnImpl
at node_modules\react-native\Libraries\LogBox\LogBox.js:37:4 in console.warn
at node_modules\expo\build\environment\react-native-logs.fx.js:18:4 in warn
at node_modules@expo\vector-icons\build\createIconSet.js:36:20 in Icon#render
at node_modules\react-native\Libraries\Renderer\implementations\ReactNativeRenderer
-dev.js:12821:21 in finishClassComponent
at node_modules\react-native\Libraries\Renderer\implementations\ReactNativeRenderer
-dev.js:12750:43 in updateClassComponent
at node_modules\react-native\Libraries\Renderer\implementations\ReactNativeRenderer
-dev.js:19794:22 in beginWork$1
at node_modules\react-native\Libraries\Renderer\implementations\ReactNativeRenderer
-dev.js:18563:22 in performUnitOfWork
at node_modules\react-native\Libraries\Renderer\implementations\ReactNativeRenderer
-dev.js:18499:21 in workLoopSync
at node_modules\react-native\Libraries\Renderer\implementations\ReactNativeRenderer
-dev.js:18464:18 in renderRootSync
at node_modules\react-native\Libraries\Renderer\implementations\ReactNativeRenderer
-dev.js:18158:31 in performSyncWorkOnRoot
at node_modules\react-native\Libraries\Renderer\implementations\ReactNativeRenderer
-dev.js:5911:33 in runWithPriority$argument_1
at node_modules\scheduler\cjs\scheduler.development.js:468:23 in unstable_runWithPr
iority
at node_modules\react-native\Libraries\Renderer\implementations\ReactNativeRenderer
-dev.js:5906:23 in flushSyncCallbackQueueImpl
at node_modules\react-native\Libraries\Renderer\implementations\ReactNativeRenderer
-dev.js:5893:28 in flushSyncCallbackQueue
at node_modules\react-native\Libraries\Renderer\implementations\ReactNativeRenderer
-dev.js:17745:30 in scheduleUpdateOnFiber
at node_modules\react-native\Libraries\Renderer\implementations\ReactNativeRenderer
-dev.js:7387:25 in classComponentUpdater.enqueueForceUpdate
at node_modules\react\cjs\react.development.js:384:2 in Component.prototype.forceUp
date
at http://192.168.8.169:19000/node_modules\expo\AppEntry.bundle?platform=androi
d&dev=true&hot=false&minify=false:163057:27 in
at node_modules\react-native-reanimated\src\reanimated1\core\AnimatedCall.js:9:15 i
n listener
at node_modules\react-native\Libraries\vendor\emitter_EventEmitter.js:135:10 in Ev
entEmitter#emit
at node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:414:4 in __cal
lFunction
at node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:113:6 in __gua
rd$argument_0
at node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:365:10 in __gu
ard
at node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:112:4 in callF
unctionReturnFlushedQueue

Hi @kassybf

It looks like there is no longer an icon called settings in the MaterialCommunityIcons icon family.

Go here and choose “MaterialCommunityIcons” from the Filters:

https://icons.expo.fyi/

Then try searching for “settings” or “cog” to see what’s available.

When you’ve found one you like, find the “settings” icon in your code and change it to the one you chose above.

1 Like

Dear @wodin
Many thanks for your great contribution. As you have suggested, I had mentioned ‘settings’ icon in my App.js using MaterialCommunityIcons family. I just replaced it by Ionicons family and everything works fine!
Once more, thank you very much

1 Like

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.