Cocoapods pod update: Parsing unable to continue due to parsing error #12172

a75c6 · 2017-08-14T04:39:37Z

Should this be an issue in the gRPC issue tracker?

Yes

What version of gRPC and what language are you using?

1.4.2 with Objective-C / Swift

What operating system (Linux, Windows, …) and version?

OSX 10.12.6

What runtime / compiler are you using (e.g. python version or version of gcc)

ProtoCompiler 3.2.0

What did you do?

There is an issue with running pod update. So I noticed that all of my previously running workspaces result in the same error when running pod update:

[!] ERROR: Parsing unable to continue due to parsing error:
contained in the file located at /Users/.../Documents/grpc_test_081317/Podfile.lock
PODS:
  - !ProtoCompiler (3.2.0):
    - Protobuf (~> 3.0)
  - !ProtoCompiler-gRPCPlugin (1.4.2):
    - !ProtoCompiler (= 3.2.0)
    - gRPC-ProtoRPC (= 1.4.2)
  - BoringSSL (8.2):
    - BoringSSL/Implementation (= 8.2)
    - BoringSSL/Interface (= 8.2)
  - BoringSSL/Implementation (8.2):
    - BoringSSL/Interface (= 8.2)
  - BoringSSL/Interface (8.2)
  - Global (0.0.1):
    - !ProtoCompiler-gRPCPlugin (~> 1.0)
    - Global/Messages (= 0.0.1)
    - Global/Services (= 0.0.1)
  - Global/Messages (0.0.1):
    - !ProtoCompiler-gRPCPlugin (~> 1.0)
    - Protobuf
  - Global/Services (0.0.1):
    - !ProtoCompiler-gRPCPlugin (~> 1.0)
    - Global/Messages
    - gRPC-ProtoRPC
  - gRPC (1.4.2):
    - gRPC-Core (= 1.4.2)
    - gRPC-RxLibrary (= 1.4.2)
  - gRPC-Core (1.4.2):
    - gRPC-Core/Implementation (= 1.4.2)
    - gRPC-Core/Interface (= 1.4.2)
  - gRPC-Core/Implementation (1.4.2):
    - BoringSSL (~> 8.0)
    - gRPC-Core/Interface (= 1.4.2)
    - nanopb (~> 0.3)
  - gRPC-Core/Interface (1.4.2)
  - gRPC-ProtoRPC (1.4.2):
    - gRPC (= 1.4.2)
    - gRPC-RxLibrary (= 1.4.2)
    - Protobuf (~> 3.0)
  - gRPC-RxLibrary (1.4.2)
  - nanopb (0.3.8):
    - nanopb/decode (= 0.3.8)
    - nanopb/encode (= 0.3.8)
  - nanopb/decode (0.3.8)
  - nanopb/encode (0.3.8)
  - Protobuf (3.3.0)

DEPENDENCIES:
  - Global (from `.`)

EXTERNAL SOURCES:
  Global:
    :path: .

SPEC CHECKSUMS:
  !ProtoCompiler: b66c7c0c1d911ad1490dcbfce30e1508739d8309
  !ProtoCompiler-gRPCPlugin: 892d2bfa38a797c026ead6c8aba6df99081407c9
  BoringSSL: 4135ae556ee2b82ee85477c39ba917a3dd5424ba
  Global: 0469a39d48a9b3548f751f9dd3d56e9f3e386256
  gRPC: 74b57d3c8a9366e09493828e0a1d27f6d69a79fd
  gRPC-Core: 642d29e59e5490374622b0629c2dd1c4c111775c
  gRPC-ProtoRPC: 675ef3d484c06967ed2a5f5ee0e510a3756f755e
  gRPC-RxLibrary: 7a25c5c25282669a82d1783d7e8a036f53e8ef27
  nanopb: 5601e6bca2dbf1ed831b519092ec110f66982ca3
  Protobuf: d582fecf68201eac3d79ed61369ef45734394b9c

PODFILE CHECKSUM: 43d72c97fe8940bce10f202cf95faeee63ec5ce9

COCOAPODS: 1.3.1

I have even setup a brand new test project. The setup allows everything to install fine as follows:

Installing !ProtoCompiler (3.2.0)
Installing !ProtoCompiler-gRPCPlugin (1.4.2)
Installing BoringSSL (8.2)
Installing Global (0.0.1)
Installing Protobuf (3.3.0)
Installing gRPC (1.4.2)
Installing gRPC-Core (1.4.2)
Installing gRPC-ProtoRPC (1.4.2)
Installing gRPC-RxLibrary (1.4.2)
Installing nanopb (0.3.8)
Generating Pods project
Integrating client project

[!] Please close any current Xcode sessions and use `grpc_test_081317.xcworkspace` for this project from now on.
Sending stats
Pod installation complete! There is 1 dependency from the Podfile and 10 total pods installed.

My podspec is Global.podspec and my proto file is global.proto.

But as soon as I run pod update, I get the same parsing error. I have tried deintegrating podfiles from all the previous project and completely rebuilding but still the same error occurs. When I run pod install after the initial install, I get the same error:

[!] ERROR: Parsing unable to continue due to parsing error:
contained in the file located at /Users/.../Documents/grpc_test_081317/Podfile.lock
PODS:
  - !ProtoCompiler (3.2.0):
    - Protobuf (~> 3.0)
  - !ProtoCompiler-gRPCPlugin (1.4.2):
    - !ProtoCompiler (= 3.2.0)
    - gRPC-ProtoRPC (= 1.4.2)
  - BoringSSL (8.2):
    - BoringSSL/Implementation (= 8.2)
    - BoringSSL/Interface (= 8.2)
  - BoringSSL/Implementation (8.2):
    - BoringSSL/Interface (= 8.2)
  - BoringSSL/Interface (8.2)
  - Global (0.0.1):
    - !ProtoCompiler-gRPCPlugin (~> 1.0)
    - Global/Messages (= 0.0.1)
    - Global/Services (= 0.0.1)
  - Global/Messages (0.0.1):
    - !ProtoCompiler-gRPCPlugin (~> 1.0)
    - Protobuf
  - Global/Services (0.0.1):
    - !ProtoCompiler-gRPCPlugin (~> 1.0)
    - Global/Messages
    - gRPC-ProtoRPC
  - gRPC (1.4.2):
    - gRPC-Core (= 1.4.2)
    - gRPC-RxLibrary (= 1.4.2)
  - gRPC-Core (1.4.2):
    - gRPC-Core/Implementation (= 1.4.2)
    - gRPC-Core/Interface (= 1.4.2)
  - gRPC-Core/Implementation (1.4.2):
    - BoringSSL (~> 8.0)
    - gRPC-Core/Interface (= 1.4.2)
    - nanopb (~> 0.3)
  - gRPC-Core/Interface (1.4.2)
  - gRPC-ProtoRPC (1.4.2):
    - gRPC (= 1.4.2)
    - gRPC-RxLibrary (= 1.4.2)
    - Protobuf (~> 3.0)
  - gRPC-RxLibrary (1.4.2)
  - nanopb (0.3.8):
    - nanopb/decode (= 0.3.8)
    - nanopb/encode (= 0.3.8)
  - nanopb/decode (0.3.8)
  - nanopb/encode (0.3.8)
  - Protobuf (3.3.0)

DEPENDENCIES:
  - Global (from `.`)

EXTERNAL SOURCES:
  Global:
    :path: .

SPEC CHECKSUMS:
  !ProtoCompiler: b66c7c0c1d911ad1490dcbfce30e1508739d8309
  !ProtoCompiler-gRPCPlugin: 892d2bfa38a797c026ead6c8aba6df99081407c9
  BoringSSL: 4135ae556ee2b82ee85477c39ba917a3dd5424ba
  Global: 0469a39d48a9b3548f751f9dd3d56e9f3e386256
  gRPC: 74b57d3c8a9366e09493828e0a1d27f6d69a79fd
  gRPC-Core: 642d29e59e5490374622b0629c2dd1c4c111775c
  gRPC-ProtoRPC: 675ef3d484c06967ed2a5f5ee0e510a3756f755e
  gRPC-RxLibrary: 7a25c5c25282669a82d1783d7e8a036f53e8ef27
  nanopb: 5601e6bca2dbf1ed831b519092ec110f66982ca3
  Protobuf: d582fecf68201eac3d79ed61369ef45734394b9c

PODFILE CHECKSUM: 43d72c97fe8940bce10f202cf95faeee63ec5ce9

COCOAPODS: 1.3.1

So this has locked me out of updating all projects using GRPC. I have also tried solutions like the following but the same error still returns:

sudo rm -fr ~/.cocoapods/repos/master
sudo gem uninstall cocoapods
sudo gem update
sudo gem instal cocoapods
pod setup

What did you expect to see?

A regular pod update as was the case before.

What did you see instead?

The errors outlined.

Anything else we should know about your project / environment?

Xcode 8.3.3
Cocoapods 1.3.1

The text was updated successfully, but these errors were encountered:

a75c6 · 2017-08-14T05:12:54Z

Using pod spec lint shows the following error:

- ERROR | [iOS] unknown: Encountered an unknown error (/bin/bash -c set -e mkdir -p ./Pods/Global
./Pods/!ProtoCompiler/protoc --plugin=protoc-gen-grpc=./Pods/!ProtoCompiler-gRPCPlugin/grpc_objective_c_plugin 
--objc_out=./Pods/Global --grpc_out=./Pods/Global -I . -I ./Pods/!ProtoCompiler ./*.proto
/bin/bash: line 3: ./Pods/!ProtoCompiler/protoc: No such file or directory
)

a75c6 · 2017-08-14T08:41:56Z

I have tried reinstalling protobuf from source so that I have a clean install and receive the following when I run protoc --version:

libprotoc 3.3.0

So after doing that and starting a clean project with the Podspec as found here, I still get the following error when running pod spec lint before running pod install:

set -e
mkdir -p ./Pods/Global
./Pods/!ProtoCompiler/protoc         --plugin=protoc-gen-grpc=./Pods/!ProtoCompiler-gRPCPlugin/grpc_objective_c_plugin         --objc_out=./Pods/Global         --grpc_out=./Pods/Global         -I .         -I ./Pods/!ProtoCompiler         ./*.proto

/bin/bash: line 3: ./Pods/!ProtoCompiler/protoc: No such file or directory
) during validation.

Analyzed 1 podspec.

So what I was testing there was whether there was an error when with the podspec even before I ran pod install. Regardless of the error, I am still able to run a clean pod install only to receive an error on pod update.

sibinlutoken · 2017-08-14T23:29:16Z

I have the same issue. It happen only if I include the !ProtoCompiler as a pod in the Podfile

a75c6 · 2017-08-15T10:48:10Z

@sibinlutoken Interesting. Do you have a workaround that you are currently using?

a75c6 · 2017-08-15T10:50:11Z

@jcanizales Any suggestions regarding this?

sibinlutoken · 2017-08-15T13:47:00Z

@namsoila there are three work around:
1: using cocoapods version 1.2.1
2: manually run a script to add "" around !protocompiler in Podfile.lock and manfest.lock.( Which is the cause of the parser error)
3. Point cocoapods-core to SHA.

Im using cocoapods 1.2.1 to work around.

a75c6 · 2017-08-17T06:26:59Z

@sibinlutoken Thanks for sharing!

a75c6 · 2017-08-17T10:05:00Z

@sibinlutoken Thanks! Using 1.2.1 and it is updating.

sudo gem install cocoapods-deintegrate cocoapods-clean
pod deintegrate
pod clean
rm Podfile
sudo gem uninstall cocoapods
sudo gem install cocoapods -v 1.2.1

Then was able to do install and update.

derpoliuk · 2018-01-22T21:26:32Z

@dgquintas, @ctiller

It is still an issue to install with CocoaPods v1.4.0. Is there any way to update .podspec files without !? I guess it's the cause of the problem with CocoaPods.

muxi · 2018-01-22T21:37:49Z

Cocoapods did not put the patch in 1.4.0; they are targeting at 1.5. We are unable to remove the ! because those pods are supposed to be installed before others. They are aware of the issue and is working on it.

derpoliuk · 2018-01-22T21:40:55Z

@muxi thank you for update! I did find a bunch of issues in https://github.com/CocoaPods/CocoaPods/ connected to issue with ! after posting my comment.

ghost · 2018-01-23T11:33:21Z

May I know if this issue with ! fixed or not ?

muxi · 2018-01-23T17:41:28Z

@Sidhdarth no so far. Tracking issue is CocoaPods/CocoaPods#7302

samskiter · 2018-02-03T00:54:13Z

Ok for my own sanity, the workaround involves editing TWO files. Podfile.lock AND Pods/Manifest.lock

The edits should look like this in both:

PODS:
  - "!ProtoCompiler (3.4.0)":
    - Protobuf (~> 3.0)
  - "!ProtoCompiler-gRPCPlugin (1.6.5)":
    - "!ProtoCompiler (= 3.4.0)"
    - gRPC-ProtoRPC (= 1.6.5)

DEPENDENCIES:
  - "!ProtoCompiler-gRPCPlugin (= 1.6.5)"
  [...]
SPEC CHECKSUMS:
  "!ProtoCompiler": 07d0c441bc00e7f01e84debf7c53794683fbca7c
  "!ProtoCompiler-gRPCPlugin": dfc8eead3e132b22750b0ec7f5fe4774ef98362a
  [...]

This is a dupe or in some way related to CocoaPods/CocoaPods#6980 CocoaPods/CocoaPods#6925 and CocoaPods/CocoaPods#6955 (so I can find my way back to this issue)

phlippieb · 2018-02-22T07:40:41Z

@muxi

We are unable to remove the ! because those pods are supposed to be installed before others.

I know it's ugly, but would it work if the pods were renamed to something like AAA-ProtoCompiler?

njovy · 2018-03-06T15:52:41Z

@samskiter Could you highlight which part did you edit to avoid this error? I'm using 1.10.0. Thank you in advance.

phlippieb · 2018-03-06T16:18:50Z

@njovy I believe @samskiter added quotes ("...") around the parts that start with exclamation marks.

muxi · 2018-03-06T17:55:01Z

I know it's ugly, but would it work if the pods were renamed to something like AAA-ProtoCompiler?

@phlippieb Yes that would work but we would really prefer not to do it because it breaks the versioning of those pods. We still prefer to wait for the patch from Cocoapods.

samskiter · 2018-03-07T12:38:12Z

@phlippieb is right. You need to add quotes around the relevant parts in both files. after the pod install runs, the lock file will be reverted so this isn't a permanent fix :(

muxi · 2018-03-07T19:03:15Z

An easier way is to remove Pods/ and Podfile.lock before pod install

phlippieb · 2018-03-08T08:22:39Z

An easier way is to remove Pods/ and Podfile.lock before pod install

@muxi Wouldn't that cause every pod install to act like a pod update though?

phlippieb · 2018-03-08T12:09:26Z

You can try to add the quotes to the files using sed. I hacked together the following command which seems to do the right things for my lockfile, but I don't actually use this, so use at your own risk.

gsed '/\!/ s/\(\!\)\(.*\)\(:\|$\)\(.*\)/"\1\2"\3\4/'

It doesn't work with the builtin MacOS sed; you have to install and use GNU sed. Hence gsed.

Or you could just revert to CocoaPods 1.2.1 or earlier:

sudo gem install cocoapods -v 1.2.1

But note that those early versions have their own issues, for example if you use the Permissions pod, well, good luck to ya.

njovy · 2018-03-08T16:59:46Z

@phlippieb Thank you for the gsed command! Now I can pod update.

  gsed -i.bak '/\!/ s/\(\!\)\(.*\)\(:\|$\)\(.*\)/"\1\2"\3\4/' Podfile.lock Pods/Manifest.lock

samskiter · 2018-04-12T15:23:57Z

The tracking bug was closed with this fix which went into 1.5.0. I've just installed and tested this out on our project and it seemed to work! We can now run 'pod install' 2 times in a row! :)

phlippieb · 2018-04-13T11:10:48Z

Confirmed, it's fixed 👍

Mingriweiji-github · 2018-06-29T12:10:19Z

I can fix by this :

rm -rf Pods
rm Podfile.lock
pod install

phlippieb · 2018-06-30T10:29:56Z

@Mingriweiji-github Yes, that's what was suggested a few posts up, but that would cause every pod install to act as a pod update, so you're gonna have to make sure the updated pods don't break anything every time you do this (unless your Podfile strictly specifies the version of each pod to use, in which case you will have to maintain that more carefully). Anyway, as pointed out above, this is fixed in cocoapods 1.5; can't you just use that?

nicolasnoble assigned nicolasnoble and muxi and unassigned nicolasnoble Aug 17, 2017

This was referenced Aug 23, 2017

Rename Proto-related podspecs #12277

Closed

pod install fails in the second run when a dependency has "!" symbol in its name CocoaPods/CocoaPods#6980

Closed

ajayghodadra mentioned this issue Nov 29, 2017

Any new pod is not able to install, update, delete, after I integrated google's speech framework in my app GoogleCloudPlatform/ios-docs-samples#66

Open

dgquintas added the disposition/to close label Dec 11, 2017

ctiller closed this as completed Dec 11, 2017

lock bot locked as resolved and limited conversation to collaborators Sep 28, 2018

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Cocoapods pod update: Parsing unable to continue due to parsing error #12172

Cocoapods pod update: Parsing unable to continue due to parsing error #12172

a75c6 commented Aug 14, 2017 •

edited

a75c6 commented Aug 14, 2017

a75c6 commented Aug 14, 2017

sibinlutoken commented Aug 14, 2017

a75c6 commented Aug 15, 2017

a75c6 commented Aug 15, 2017

sibinlutoken commented Aug 15, 2017

a75c6 commented Aug 17, 2017

a75c6 commented Aug 17, 2017

derpoliuk commented Jan 22, 2018

muxi commented Jan 22, 2018

derpoliuk commented Jan 22, 2018

ghost commented Jan 23, 2018 •

edited by ghost

muxi commented Jan 23, 2018 •

edited

samskiter commented Feb 3, 2018

phlippieb commented Feb 22, 2018

njovy commented Mar 6, 2018 •

edited

phlippieb commented Mar 6, 2018

muxi commented Mar 6, 2018 •

edited

samskiter commented Mar 7, 2018

muxi commented Mar 7, 2018

phlippieb commented Mar 8, 2018 •

edited

phlippieb commented Mar 8, 2018

njovy commented Mar 8, 2018 •

edited

samskiter commented Apr 12, 2018 •

edited

phlippieb commented Apr 13, 2018

Mingriweiji-github commented Jun 29, 2018

phlippieb commented Jun 30, 2018

Cocoapods pod update: Parsing unable to continue due to parsing error #12172

Cocoapods pod update: Parsing unable to continue due to parsing error #12172

Comments

a75c6 commented Aug 14, 2017 • edited

Should this be an issue in the gRPC issue tracker?

What version of gRPC and what language are you using?

What operating system (Linux, Windows, …) and version?

What runtime / compiler are you using (e.g. python version or version of gcc)

What did you do?

What did you expect to see?

What did you see instead?

Anything else we should know about your project / environment?

a75c6 commented Aug 14, 2017

a75c6 commented Aug 14, 2017

sibinlutoken commented Aug 14, 2017

a75c6 commented Aug 15, 2017

a75c6 commented Aug 15, 2017

sibinlutoken commented Aug 15, 2017

a75c6 commented Aug 17, 2017

a75c6 commented Aug 17, 2017

derpoliuk commented Jan 22, 2018

muxi commented Jan 22, 2018

derpoliuk commented Jan 22, 2018

ghost commented Jan 23, 2018 • edited by ghost

muxi commented Jan 23, 2018 • edited

samskiter commented Feb 3, 2018

phlippieb commented Feb 22, 2018

njovy commented Mar 6, 2018 • edited

phlippieb commented Mar 6, 2018

muxi commented Mar 6, 2018 • edited

samskiter commented Mar 7, 2018

muxi commented Mar 7, 2018

phlippieb commented Mar 8, 2018 • edited

phlippieb commented Mar 8, 2018

njovy commented Mar 8, 2018 • edited

samskiter commented Apr 12, 2018 • edited

phlippieb commented Apr 13, 2018

Mingriweiji-github commented Jun 29, 2018

phlippieb commented Jun 30, 2018

a75c6 commented Aug 14, 2017 •

edited

ghost commented Jan 23, 2018 •

edited by ghost

muxi commented Jan 23, 2018 •

edited

njovy commented Mar 6, 2018 •

edited

muxi commented Mar 6, 2018 •

edited

phlippieb commented Mar 8, 2018 •

edited

njovy commented Mar 8, 2018 •

edited

samskiter commented Apr 12, 2018 •

edited