feat: look for Podfile in the source directory too

[Kiesco08]

Summary:

I'm adding React Native to an existing native project. The project is fairly large, so it is split up into multiple subprojects and does not follow the typical React Native directory structure. Instead this is how it is setup:

ios/
| | | |_ Pods/
| | |__ **Podfile**
| |___ Project/Project.xcodeproj/
|____ ProjectReactNativeFramework/
... // Other subprojects

Currently, cli assumes that Podfile is a sibling of Project.xcodeproj. This change adds a feature enabling it to look for the Podfile from the source directory, if it is not found in the project directory.

Test Plan:

• When I run yarn react-native config, the Podfile configuration value is no longer null.
• Running yarn react-native run-ios no longer throws the following error:

error Could not find "Podfile.lock" at null.lock. Did you run "pod install" in iOS directory?

[Kiesco08]

This test passes locally 🤔

[grabbou]

Related to #1444 too. I will work on both of these PRs tomorrow and merge one of them (not sure which one tho) in order to resolve this issue.

[grabbou]

Closing in favour of #1459, I would prefer to allow users to set the path manually, rather than extending the automatic detection (it's there to satisfy 99% of standard use cases)

[Kiesco08]

Summary:

I'm adding React Native to an existing native project. The project is fairly large, so it is split up into multiple subprojects and does not follow the typical React Native directory structure. Instead this is how it is setup:

ios/
| | | |_ Pods/
| | |__ **Podfile**
| |___ Project/Project.xcodeproj/
|____ ProjectReactNativeFramework/
... // Other subprojects

Currently, cli assumes that Podfile is a sibling of Project.xcodeproj. This change adds a feature enabling it to look for the Podfile from the source directory, if it is not found in the project directory.

Test Plan:

• When I run yarn react-native config, the Podfile configuration value is no longer null.
• Running yarn react-native run-ios no longer throws the following error:

error Could not find "Podfile.lock" at null.lock. Did you run "pod install" in iOS directory?

[Kiesco08]

This test passes locally 🤔

[grabbou]

Related to #1444 too. I will work on both of these PRs tomorrow and merge one of them (not sure which one tho) in order to resolve this issue.

[grabbou]

Closing in favour of #1459, I would prefer to allow users to set the path manually, rather than extending the automatic detection (it's there to satisfy 99% of standard use cases)

[Kiesco08]

Summary:

I'm adding React Native to an existing native project. The project is fairly large, so it is split up into multiple subprojects and does not follow the typical React Native directory structure. Instead this is how it is setup:

ios/
| | | |_ Pods/
| | |__ **Podfile**
| |___ Project/Project.xcodeproj/
|____ ProjectReactNativeFramework/
... // Other subprojects

Currently, cli assumes that Podfile is a sibling of Project.xcodeproj. This change adds a feature enabling it to look for the Podfile from the source directory, if it is not found in the project directory.

Test Plan:

• When I run yarn react-native config, the Podfile configuration value is no longer null.
• Running yarn react-native run-ios no longer throws the following error:

error Could not find "Podfile.lock" at null.lock. Did you run "pod install" in iOS directory?

[Kiesco08]

This test passes locally 🤔

[grabbou]

Related to #1444 too. I will work on both of these PRs tomorrow and merge one of them (not sure which one tho) in order to resolve this issue.

[grabbou]

Closing in favour of #1459, I would prefer to allow users to set the path manually, rather than extending the automatic detection (it's there to satisfy 99% of standard use cases)

[Kiesco08]

Summary:

I'm adding React Native to an existing native project. The project is fairly large, so it is split up into multiple subprojects and does not follow the typical React Native directory structure. Instead this is how it is setup:

ios/
| | | |_ Pods/
| | |__ **Podfile**
| |___ Project/Project.xcodeproj/
|____ ProjectReactNativeFramework/
... // Other subprojects

Currently, cli assumes that Podfile is a sibling of Project.xcodeproj. This change adds a feature enabling it to look for the Podfile from the source directory, if it is not found in the project directory.

Test Plan:

• When I run yarn react-native config, the Podfile configuration value is no longer null.
• Running yarn react-native run-ios no longer throws the following error:

error Could not find "Podfile.lock" at null.lock. Did you run "pod install" in iOS directory?

[Kiesco08]

This test passes locally 🤔

[grabbou]

Related to #1444 too. I will work on both of these PRs tomorrow and merge one of them (not sure which one tho) in order to resolve this issue.

[grabbou]

Closing in favour of #1459, I would prefer to allow users to set the path manually, rather than extending the automatic detection (it's there to satisfy 99% of standard use cases)

[Kiesco08]

Summary:

I'm adding React Native to an existing native project. The project is fairly large, so it is split up into multiple subprojects and does not follow the typical React Native directory structure. Instead this is how it is setup:

ios/
| | | |_ Pods/
| | |__ **Podfile**
| |___ Project/Project.xcodeproj/
|____ ProjectReactNativeFramework/
... // Other subprojects

Currently, cli assumes that Podfile is a sibling of Project.xcodeproj. This change adds a feature enabling it to look for the Podfile from the source directory, if it is not found in the project directory.

Test Plan:

• When I run yarn react-native config, the Podfile configuration value is no longer null.
• Running yarn react-native run-ios no longer throws the following error:

error Could not find "Podfile.lock" at null.lock. Did you run "pod install" in iOS directory?

[Kiesco08]

This test passes locally 🤔

[grabbou]

Related to #1444 too. I will work on both of these PRs tomorrow and merge one of them (not sure which one tho) in order to resolve this issue.

[grabbou]

Closing in favour of #1459, I would prefer to allow users to set the path manually, rather than extending the automatic detection (it's there to satisfy 99% of standard use cases)

[Kiesco08]

Summary:

I'm adding React Native to an existing native project. The project is fairly large, so it is split up into multiple subprojects and does not follow the typical React Native directory structure. Instead this is how it is setup:

ios/
| | | |_ Pods/
| | |__ **Podfile**
| |___ Project/Project.xcodeproj/
|____ ProjectReactNativeFramework/
... // Other subprojects

Currently, cli assumes that Podfile is a sibling of Project.xcodeproj. This change adds a feature enabling it to look for the Podfile from the source directory, if it is not found in the project directory.

Test Plan:

• When I run yarn react-native config, the Podfile configuration value is no longer null.
• Running yarn react-native run-ios no longer throws the following error:

error Could not find "Podfile.lock" at null.lock. Did you run "pod install" in iOS directory?

[Kiesco08]

This test passes locally 🤔

[grabbou]

Related to #1444 too. I will work on both of these PRs tomorrow and merge one of them (not sure which one tho) in order to resolve this issue.

[grabbou]

Closing in favour of #1459, I would prefer to allow users to set the path manually, rather than extending the automatic detection (it's there to satisfy 99% of standard use cases)

[Kiesco08]

Summary:

I'm adding React Native to an existing native project. The project is fairly large, so it is split up into multiple subprojects and does not follow the typical React Native directory structure. Instead this is how it is setup:

ios/
| | | |_ Pods/
| | |__ **Podfile**
| |___ Project/Project.xcodeproj/
|____ ProjectReactNativeFramework/
... // Other subprojects

Currently, cli assumes that Podfile is a sibling of Project.xcodeproj. This change adds a feature enabling it to look for the Podfile from the source directory, if it is not found in the project directory.

Test Plan:

• When I run yarn react-native config, the Podfile configuration value is no longer null.
• Running yarn react-native run-ios no longer throws the following error:

error Could not find "Podfile.lock" at null.lock. Did you run "pod install" in iOS directory?

[Kiesco08]

This test passes locally 🤔

[grabbou]

Related to #1444 too. I will work on both of these PRs tomorrow and merge one of them (not sure which one tho) in order to resolve this issue.

[grabbou]

Closing in favour of #1459, I would prefer to allow users to set the path manually, rather than extending the automatic detection (it's there to satisfy 99% of standard use cases)

[Kiesco08]

Summary:

I'm adding React Native to an existing native project. The project is fairly large, so it is split up into multiple subprojects and does not follow the typical React Native directory structure. Instead this is how it is setup:

ios/
| | | |_ Pods/
| | |__ **Podfile**
| |___ Project/Project.xcodeproj/
|____ ProjectReactNativeFramework/
... // Other subprojects

Currently, cli assumes that Podfile is a sibling of Project.xcodeproj. This change adds a feature enabling it to look for the Podfile from the source directory, if it is not found in the project directory.

Test Plan:

• When I run yarn react-native config, the Podfile configuration value is no longer null.
• Running yarn react-native run-ios no longer throws the following error:

error Could not find "Podfile.lock" at null.lock. Did you run "pod install" in iOS directory?

[Kiesco08]

This test passes locally 🤔

[grabbou]

Related to #1444 too. I will work on both of these PRs tomorrow and merge one of them (not sure which one tho) in order to resolve this issue.

[grabbou]

Closing in favour of #1459, I would prefer to allow users to set the path manually, rather than extending the automatic detection (it's there to satisfy 99% of standard use cases)