Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Error with react-native@0.56
See original GitHub issueThe project won’t build with RN 0.56. react-native run-android crashes with the following error:
/Users/ashoat/Dropbox/src/squadcal/native/node_modules/react-native-exit-app/android/build/intermediates/res/merged/release/values-v24/values-v24.xml:3: AAPT: Error retrieving parent for item: No resource found that matches the given name 'android:TextAppearance.Material.Widget.Button.Borderless.Colored'.
/Users/ashoat/Dropbox/src/squadcal/native/node_modules/react-native-exit-app/android/build/intermediates/res/merged/release/values-v24/values-v24.xml:4: AAPT: Error retrieving parent for item: No resource found that matches the given name 'android:TextAppearance.Material.Widget.Button.Colored'.
/Users/ashoat/Dropbox/src/squadcal/native/node_modules/react-native-exit-app/android/build/intermediates/res/merged/release/values-v26/values-v26.xml:15:21-54: AAPT: No resource found that matches the given name: attr 'android:keyboardNavigationCluster'.
/Users/ashoat/Dropbox/src/squadcal/native/node_modules/react-native-exit-app/android/build/intermediates/res/merged/release/values-v24/values-v24.xml:3: error: Error retrieving parent for item: No resource found that matches the given name 'android:TextAppearance.Material.Widget.Button.Borderless.Colored'.
/Users/ashoat/Dropbox/src/squadcal/native/node_modules/react-native-exit-app/android/build/intermediates/res/merged/release/values-v24/values-v24.xml:4: error: Error retrieving parent for item: No resource found that matches the given name 'android:TextAppearance.Material.Widget.Button.Colored'.
/Users/ashoat/Dropbox/src/squadcal/native/node_modules/react-native-exit-app/android/build/intermediates/res/merged/release/values-v26/values-v26.xml:15: error: Error: No resource found that matches the given name: attr 'android:keyboardNavigationCluster'.
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
AwesomeProject error with react 0.56-0.55.4 #20146 - GitHub
1. Clear watchman watches: `watchman watch-del-all`. 2. Delete the `node_modules` folder: `rm -rf node_modules && npm install`. 3. Reset Metro ...
Read more >error code: 500 on react native 0.56 for android - Stack Overflow
There seems to be some issue with latest react native version. Create the project with below command. react-native init --version="0.54.0" ...
Read more >Upgrading to new versions - React Native
Some upgrades won't be done automatically with the React Native CLI and require manual work, e.g. 0.28 to 0.29 , or 0.56 to...
Read more >XCode10 Beta + ReactNative 0.56 | Apple Developer Forums
I got the following error when I try to build the simple RN 0.56 application: ... build phase: <PATH_TO_PROJECT>/node_modules/react-native/React/Modules/ ...
Read more >React Native - Jest: Broken since update to 0.56. How to fix it?
is actually nothing to do with react-native 0.56. is caused by the babel presets 5, just revert this package will do the trick....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
For me it is simple, for long running projects I always scrape together all you need for building your app and add it to git… the only disadvantage is the additional space you use (but hey, how much does a GB on simple HD cost these days?). Once I had had used a libary in an experimental project, 2 years later I needed it and that library was deleted by the owner… luckily I had the project in working condition on an old spare laptop or I could start over from scratch! You can almost think of it as an assurance: as long as everything goes as planned you don’t need it… but when it goes wrong you are happy you invested in it and would be screwed if didn’t! 😃
So it’s the compileSdkVersion and buildToolVersion you have changed if i’m correct?
See https://github.com/wumke/react-native-exit-app/pull/16 for a even better solution that should be used by all libraries if you’d ask me! (I will implement it in all next releases and new libraries…)