Skip to content

Conversation

Maushundb
Copy link
Contributor

@Maushundb Maushundb commented Oct 18, 2019

Summary:

This PR fixes the issue described at #805 where when Podfile.lock is an invalid yaml file, the react-native run ios command would fail.

To achieve this, I only parse parts of the Podfile we need, which are valid yaml.

Fixes #805

Test Plan:

Unit test insures that error no longer happens and output is correct.

@thymikee thymikee merged commit b22d70a into react-native-community:master Oct 18, 2019
@thymikee
Copy link
Member

Thank you for the fix and a test <3

@hzz780
Copy link

hzz780 commented Nov 9, 2019

Hi.
Thanks.
And when will we publish this version?

grabbou added a commit that referenced this pull request Nov 14, 2019
* update lockfile

* v3.0.0-alpha.3

* chore: add v3 support table

* v3.0.0-alpha.4

* v3.0.0-alpha.5

* chore: set publishConfig for packages

* v3.0.0-alpha.6

* fix: check for podspecPath in warnAboutPodInstall (#800)

* fix: run npx.cmd on Windows (#801)

* fix: run npx.exe on Windows

* use npx.cmd

* v3.0.0-alpha.7

* fix: podfile parsing on invalid yaml (#810)

* Remove haste

* Update test without large snapshot

* Update configuration

* Revert unecessary changes

* One more file
@Maushundb
Copy link
Contributor Author

Today - https://github.com/react-native-community/cli/releases/tag/v3.0.0

thymikee pushed a commit that referenced this pull request Nov 20, 2019
* update lockfile

* v3.0.0-alpha.3

* chore: add v3 support table

* v3.0.0-alpha.4

* v3.0.0-alpha.5

* chore: set publishConfig for packages

* v3.0.0-alpha.6

* fix: check for podspecPath in warnAboutPodInstall (#800)

* fix: run npx.cmd on Windows (#801)

* fix: run npx.exe on Windows

* use npx.cmd

* v3.0.0-alpha.7

* fix: podfile parsing on invalid yaml (#810)

* Remove haste

* Update test without large snapshot

* Update configuration

* Revert unecessary changes

* One more file
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

unknown tag !<!ruby/object:Pathname> when using with react-native-unimodules
3 participants