[0.42.0] Missing Pod specs
See original GitHub issueI’m not sure I should report this here or in Yoga repo.
Running pod install
with react-native 0.42.0 I got the following error:
None of your spec sources contain a spec satisfying the dependency:
Yoga (= 0.42.0.React)
.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:6
- Comments:5 (3 by maintainers)
Top Results From Across the Web
loki-distributed 0.67.1 - grafana - Artifact Hub
Key Type Default
compactor.affinity object
compactor.command string nil
compactor.enabled bool false
Read more >AWS EKS: unable to attach IAM role to pods - Stack Overflow
The envoy container is unable to move to ready state. Looking for environment variables in the container shows missing variables. kubectl exec - ......
Read more >Installation · React Native Camera
This document is split into two main sections: Required installation steps for basic usage of react-native-camera; Additional installation ...
Read more >rn-appgain-sdk - npm Package Health Analysis - Snyk
Looks like rn-appgain-sdk is missing a security policy. ... Explicitly include Yoga if you are using RN >= 0.42.0 pod 'yoga', :path =>...
Read more >homebrew-core - Homebrew Formulae
a2ps 4.14 Any‑to‑PostScript filter
aacgain 1.8 AAC‑supporting version of mp3gain
aalib 1.4rc5 Portable ASCII art graphics library
aamath 0.3 Renders mathematical expressions as ASCII art
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
The official fix for this is to explicitly specify the location of React Native’s copy of Yoga in your Podfile:
Would anyone like to submit a docs PR?
Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we’re automatically closing issues after a period of inactivity. Please do not take it personally!
If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:
If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.