-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed prop type: Invalid prop name
of value home-outline
supplied to `Icon
#1215
Comments
name
of value calendar-month
supplied to `Iconname
of value home-outline
supplied to `Icon
I am getting the same issue. The Ionicons v5 icons are not recognised despite being in the glyph map. EDIT: Think I found the issue - the glyph map numbers start again when it reaches the ios ones. So In saying this, I haven't been able to get it working myself, someone who knows what they're doing might have to create the PR |
i'm getting the same issue, still looking for the fix T_T |
Use |
I have the same problem. Still looking for the fix |
Use any other vector icon library's heart Icon like AntDesign as I used this: import AntDesign from 'react-native-vector-icons/AntDesign'; |
Same issue happens with me |
I'm having the same issue even with AntDesign icons. Anyone find a fix? |
I'm having the same issue even with AntDesign icons too. Anyone find a fix? |
It is problem came from android gradle so . Android Edit android/app/build.gradle ( NOT android/build.gradle ) and add the following: apply from: "../../node_modules/react-native-vector-icons/fonts.gradle" Or if did't got so can check this documentation |
I have realized that after the update, the names of some icons have changed. For instance, |
For android, I try to use 'home-outline' icon of
ionicons
but i have error
Failed prop type: Invalid prop 'name' of value 'home-outline' supplied to 'Icon...
I have lastest version of this package
"react-native-vector-icons": "^7.0.0",
And for React-native
"react-native": "~0.62.2",
I read documentation but i don't see why i have this warning :(
The text was updated successfully, but these errors were encountered: