[GitHub] [cordova-ios] erisu edited a comment on pull request #1133: Update Readme: Xcode and clean

[GitBox]

erisu edited a comment on pull request #1133:
URL: https://github.com/apache/cordova-ios/pull/1133#issuecomment-923784600


   OK, I have remembered it now and confirmed,
   
   If a user is installing a plugin that uses Pods, opening the `xcodeproj` 
will not load the Pods as it is a separate project. And then, the code that 
imports the pods will fail and leads to build failures.
   
   If the project contains Pods, the users should open `xcworkspace`.
   
   This is why I always suggested to people to open the `xcworkspace`. 
`xcworkspace` works for all cases.
   
   If we mentioned anything about `xcodeproj`, it could lead to confusion.
   
   If anything is mentioned, just the `xcworkspace` is fine.
   
   Here is also an example screenshot of the XCode project navigator to show 
the difference.
   
   | xcworkspace | xcodeproj |
   | -- | -- |
   | <img width="260" alt="xcworkspace" 
src="https://user-images.githubusercontent.com/1029107/134143738-47849f66-6ac2-4952-90dc-2c4633c540cf.png";>
 | <img width="344" alt="xcodeproj" 
src="https://user-images.githubusercontent.com/1029107/134143783-770bb37b-49ee-4719-aa91-d4fc28646e58.png";>
 |
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org