search

protocolbuffers / protobuf

Protocol Buffers - Google's data interchange format
http://protobuf.dev
Other
65.68k stars 15.5k forks source link

'Protobuf/GPBAny.pbobjc.h' file not found #7688

Closed kumareshsaran closed 2 years ago

kumareshsaran commented 4 years ago

**What version of protobuf and what

Screenshot 2020-07-07 at 12 55 31 PM

language are you using?** Coaco pod Version: 1.9.3 Language: Swift

What operating system (Linux, Windows, ...) and version? Mac OS:10.15.4 (Catalina)

I was got error after installing the pod 'Firebase/Crashlytics' and pod 'Firebase/Analytics'.

Here is my pod File `
use_frameworks!

Comment this line if you're not using Swift and don't want to use dynamic frameworks

pod 'AFNetworking' pod 'BFTask-Extras' pod 'Mantle' pod 'JSONKit' pod 'MBProgressHUD'

pod 'Protobuf', :inhibit_warnings => true

pod 'FBSDKCoreKit'

pod 'FBSDKLoginKit'

pod 'FBSDKShareKit'

pod 'FacebookLogin'

pod 'TwitterKit' pod 'TwitterCore'

pod 'CryptoSwift'

pod 'CryptoSwift', :git => "https://github.com/krzyzanowskim/CryptoSwift.git", :branch => "develop"

pod 'AWSCognito'

pod 'AWSCore'

pod 'AWSCognitoIdentityProvider'

#

pod 'AWSSNS'

pod 'AWSS3'

pod 'AWSLambda'

pod 'AWSCognito', '2.4.16' pod 'AWSCognitoIdentityProvider', '2.4.16' pod 'AWSCore', '2.4.16' pod 'AWSLambda', '2.4.16' pod 'AWSS3', '2.4.16' pod 'AWSSNS', '2.4.16'

pod 'GooglePlaces' pod 'GoogleSignIn'

pod 'Stripe', '~> 15.0.2'

pod 'CardIO'

pod 'OpenCV', '3.3.1'

pod 'Firebase/Core'

pod 'Firebase/Crash'

pod 'Firebase/Performance' pod 'Firebase/RemoteConfig'

pod 'Fabric'

pod 'Crashlytics' pod 'FittedSheets'

pod 'KWStepper'

pod 'TLPhotoPicker' pod 'Alamofire' pod 'SwiftyJSON' pod 'Starscream'#, '~> 4.0.0' pod 'RSMasterTableViewKit' pod "ESPullToRefresh" pod "SwiftRater"

pod 'Firebase/Crashlytics'

pod 'Firebase/Analytics'

Here is my Podlock file:

`PODS:

DEPENDENCIES:

PODFILE CHECKSUM: 21af66348d0a09abea8ffbb59f10fb9d3fdb93e5

COCOAPODS: 1.9.3 `

thomasvl commented 4 years ago

Please try doing a clean and deleting derived data. If it repeats, check the directory in the second error bubble to see what headers are actually there.

@paulb777 fyi.

kumareshsaran commented 4 years ago

Hi @thomasvl I tried above you mentioned but it's not clearing error.

thomasvl commented 4 years ago

btw - in your report what does Protobuf: 2793fcd0622a00b546c60e7cbbcc493e043e9bb9 mean? I don't see that commit in this repo.

thomasvl commented 4 years ago

@paulb777 what is the intent of the FirebaseABTesting podspec's Protobuf dependency? It has two qualifiers:

https://github.com/CocoaPods/Specs/blob/master/Specs/d/c/1/FirebaseABTesting/3.3.0/FirebaseABTesting.podspec.json#L45-L48

Doesn't that first entry force it to say on a 3.9.x entry, meaning you won't get anything newer? i.e. - the 3.12.x with the fixes around this issues?

paulb777 commented 4 years ago

@thomasvl The double qualifier indicates a requirement of greater than 3.9.2, but not allowing a major version update. From the Protobuf line in the Podfile.lock, you can see that 3.12.0 is chosen in this case.

This issue is almost certainly the result of stale Xcode and/or CocoaPods state since this configuration has worked for many people over the last several months.

@kumareshsaran What is your Xcode version?

kumareshsaran commented 4 years ago

@paulb777 My Xcode Version: Version 11.4.1 (11E503a)

kumareshsaran commented 4 years ago

Hi I am still facing this issue.could you tell me what is exact solution

thomasvl commented 4 years ago

Can you extract from your setup a sample project that shows things getting into this state? At the moment, you seem to be the only report like this, so it isn't clear what is causing it.

Vaisakhk commented 4 years ago

@thomasvl Me also facing the same issue. "check the directory in the second error bubble to see what headers are actually there". Please find the attachment for the headers in that second bubble path

Screen Shot 2020-08-10 at 10 38 43 PM
thomasvl commented 4 years ago

We still need someone to help provide a repo case for this to really be able to offer any more help. So far, we haven't had a good indicator on how to repo this to help take a look.

emrcftci commented 3 years ago

Still have the issue

deannagarcia commented 2 years ago

Closing this thread because of a lack of a reproduction case. If anyone is still experiencing this error and can give us a simple case to reproduce, please reopen!