! (exclamation mark) in its name, such as !ProtoCompiler-gRPCPluginpod install twiceThe parsing issues that were encountered in 1.3.0 and 1.3.1 to be fixed, and all pods to install without errors.
On the second pod install, the following parsing error still occurs:
[!] ERROR: Parsing unable to continue due to parsing error:
contained in the file located at /path/to/Podfile.lock
Note: This issue has already been noted since 1.3.0 and is detailed by #6925, #6955,#6980, #7239, #7241, and #7268 (that I could find). These issues have all been closed as duplicates (strangely, #6925 and #6955 are marked as dupes of each other) and as fixed by CocoaPods/Core#395.
However, to my understanding, version 1.4.0.rc.1 has the fix merged; yet the issue persists. So this issue should not be closed as fixed yet; or at least, some of the existing issues should be reopened.
There is an open PR at CocoaPods/Core/pull/419 to fix the issue, which is still awaiting feedback on a comment.
The latest version before this issue was introduced is 1.2.1, which was released back in April, and has problems of its own. Considering the relatively long waits between stable releases, it would be greatly appreciated if 1.4.0 could fix this issue once and for all.
gRPC has an example project that can be used to demonstrate the issue. Instructions to set up (found here):
git clone -b $(curl -L https://grpc.io/release) https://github.com/grpc/grpc
cd grpc
git submodule update --init
cd examples/objective-c/helloworld
pod install
The first pod install should work, but running pod install again will fail with 1.4.0.rc.1.
Will move this to 1.5.0.
Confirmed can repro using the above steps.
@dnkoutso Ok rad. Any chance we could aim to get this in 1.4.0? From the number of issued opened for this in the past, seems like this fix is highly sought after. I for one would love to be able to use an up-to-date version of CocoaPods again :) As I mentioned above, there is an open PR for this already at CocoaPods/Core/pull/419
@phlippieb I am sorry but 1.4.0 is about to ship (most likely today) this will have to be for 1.5.0 or 1.4.1 quick update.
In the meantime once we fix it there will be easy ways using bundler for you to consume the fix.
Would love to see this fixed soon!
https://github.com/CocoaPods/Core/pull/381/files is what broke things
Most helpful comment
Note: This issue has already been noted since 1.3.0 and is detailed by #6925, #6955,#6980, #7239, #7241, and #7268 (that I could find). These issues have all been closed as duplicates (strangely, #6925 and #6955 are marked as dupes of each other) and as fixed by CocoaPods/Core#395.
However, to my understanding, version 1.4.0.rc.1 has the fix merged; yet the issue persists. So this issue should not be closed as fixed yet; or at least, some of the existing issues should be reopened.
There is an open PR at CocoaPods/Core/pull/419 to fix the issue, which is still awaiting feedback on a comment.
The latest version before this issue was introduced is 1.2.1, which was released back in April, and has problems of its own. Considering the relatively long waits between stable releases, it would be greatly appreciated if 1.4.0 could fix this issue once and for all.