-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Update to 2.1.5 breaks my project. #928
Comments
I just removed the references from the project but now I have a different issue .. seems like everytime I upgrade there is a problem in native-base :\ |
Did you follow the steps mentioned? |
I ran your first piece of code with no effect. I dont know what you mean by deleting my ios/android directories |
did you create your app with CRNA? |
no it is an old project. I just pulled it down from git ran, npm install and it freaked out with all these errors |
ios/android directory means folders named |
@yaronlevi Yes, that's because of the breaking change. Let me know if that fixes it. |
i guess I am lost...and i guess more new that what i actually considered. Why do i need to delete these with all my custom java and custom ios code. What value does that give me? |
@stadiumbeejm okay hold on, I'll just get back with an alternative. |
@stadiumbeejm The steps have been updated in the initial comment. can you try that out and let me know. |
你好, |
Hi guys,
Hope it help : D |
Closing this as the above solution works. Let us know if you still face this |
I tried the following solution and solved the problem, without having to manually delete the entries. |
When we upgrade to 2.1.5 and above from an older version of native-base, there are multiple build errors.
This is happening because we have removed the unused fonts from the package #900.
If you've not many any changes to native code:
Deleting the android/ios directories and running
react-native upgrade
fixes it.Otherwise
Unlinking vector-icons and cleaning the build should fix it.
Steps
react-native link
The text was updated successfully, but these errors were encountered: