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.
Build failed with react native 0.31
See original GitHub issueWhen i try to build with RN 0.31 I’ve got this issue
CSSLayout/CSSLayout.h' file not found with <angled> include; use "quotes" instead
CSSLayout.h:26:10: 'CSSLayout/CSSMacros.h' file not found with <angled> include; use "quotes" instead
I don’t know what to do
Thanks
Issue Analytics
- State:
- Created 7 years ago
- Reactions:2
- Comments:6
Top Results From Across the Web
Android build failure with react-native 0.31 · Issue #30 - GitHub
I get the following error while running react-native run-android command in the my app after including the library. If I remove the library, ......
Read more >React Native 0.31: Could not get BatchedBridge Error
A common issue is that the packager is not started automatically when you run react-native run-android . You can start it manually using...
Read more >Troubleshooting - React Native
If you run into issue where executing npm run android on macOS throws the above error, try to run sudo chmod +x android/gradlew...
Read more >React Native build: Error while merging dex archives-Reactjs
In my case I installed both @react-native-community/picker and also @react-native-picker/picker. After removing deprecated one with yarn remove ...
Read more >react-native-maps - npm
React Native Mapview component for iOS + Android. Latest version: 1.3.2, last published: 3 months ago. Start using react-native-maps in your ...
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
Use XCode’s quick fix - right click over the problem area and apply fix. It should be resolved.
It looks like this was fixed in RN 0.34.0 (released today). See: https://github.com/facebook/react-native/commit/6e216d20343fccbb7bf9853ffb06a0d2628e9fc5