-
Notifications
You must be signed in to change notification settings - Fork 437
[FIX] Updated development environment setup instructions #2575
base: develop
Are you sure you want to change the base?
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #2575 +/- ##
============================================
- Coverage 46.21% 26.49% -19.72%
============================================
Files 625 456 -169
Lines 28917 16903 -12014
============================================
- Hits 13364 4479 -8885
+ Misses 15553 12424 -3129
Continue to review full report at Codecov.
|
| 3. Build the project by ⌘ + R | ||
|
|
||
| 2. Navigate to the unzipped folder and run the following commands-</br> | ||
| `pod deintegrate`</br> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@prateekguptaiiitk Why deintegrate is necessary here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pod deintegrate helps to remove all traces of Cocoapods from the project. So after that if we do pod install we can start to install them afresh. pod update will solve any version inconsistencies. Without pod deintegrate project was throwing random build errors.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@prateekguptaiiitk pod update will cause the CocoaPods to update libraries even if they're not in the same version as in Podfile.lock, right? It could cause some inconsistencies between projects in this case I think. Just pod install should be enough for anyone cloning the project, but most of the time that's not even necessary because the Pods folder is already being cloned.
Have you experienced any problems cloning the app for the first time and running it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes @rafaelks I along with some others experienced problems while setting up the project for the first time and running it. Even running pod install didn't help. When I ran pod deintegrate and then pod install my problem was resolved and project was built successfully.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While I didn't experience any problem setting up the project for the first time, as the Pods were already there, I think the problem is usually with updating swiftlint and fastlane.
Updating fork
@RocketChat/ios
Closes #2553