Firebase-ios-sdk: Non-portable path warnings from Protobuf pod

[OscarGorog]

Please update for Swift 5 support.

Thanks!

[google-oss-bot]

I found a few problems with this issue:

• I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
• This issue does not seem to follow the issue template. Make sure you provide all the required information.

[maksymmalyhin]

@OkiRules Thank you for your request. For most of the components Swift 5 should be supported now. Would you be able to provide examples of the issues you have with Swift 5, please?

[OscarGorog]

[paulb777]

This is an Apple issue tracked at https://openradar.appspot.com/radar?id=6091887509241856. More discussion at https://github.com/protocolbuffers/protobuf/issues/3218.

We can investigate if we can find any better workarounds. In the meantime, it's safe to ignore the warnings.

[paulb777]

I'm going to change the title since the issue is not related to Swift 5.

[paulb777]

One workaround is adding pod 'Protobuf', :inhibit_warnings => true to the Podfile.

[paulb777]

Sent https://github.com/protocolbuffers/protobuf/pull/6190

[Deni0S]

It worked, it was enough to change the letter of the folder: Pods/Protobuf/objectivec/google/protobuf (protobuf -> Protobuf)

[paulb777]

protocolbuffers/protobuf#6464 in progress to fix

[devkokodev]

I'm trying to install 'Firebase/Messaging' it install protobuf etc. I'm using swift 5, deployment ios 11 and i have this issues:

I've tried (cmd + shift + k) delete derived data, pod install, pod update, nothing solved this issue.
Any help?

[paulb777]

@devkokodev That looks like a different issue. Perhaps, something in the configuration? We'll likely need more information about reproducing to help. Please open another issue with that detail.

[BugsBunnyBR]

So, now that the PR in cocoapods is merged... all that is needed is to update the protobuf lib in this repository?
As far as I can tel https://github.com/firebase/firebase-ios-sdk/blob/master/FirebaseMessaging.podspec#L52 is the current version, right? As the version differences are not so small, I image it should be with care. @paulb777 this is something in your radar, right?

[paulb777]

@BugsBunnyBR A new Protobuf version with that PR needs to be published to CocoaPods. Please enquire in the Protobuf repo about their release plans. Firebase will automatically pick up a subsequent Protobuf minor release on a pod update.

[BugsBunnyBR]

I thought is was in this release https://github.com/protocolbuffers/protobuf/releases/tag/v3.9.1, but is looks like it is not here yet. Sorry for the misunderstanding.

[psyduck-scar4]

It worked, it was enough to change the letter of the folder: Pods/Protobuf/objectivec/google/protobuf (protobuf -> Protobuf)

thank you!!! this fixed it.

[navingp]

@OkiRules did you resolved this "Non-portable path warnings from Protobuf pod."
your help is much appreciated.

[OscarGorog]

Not yet as the new build has not been updated for Cocoapods but when it is will inform you.

[navingp]

@OkiRules Thanks for the quick reply..

[BugsBunnyBR]

I think protocolbuffers released a version with the fix
https://github.com/protocolbuffers/protobuf/releases

Can someone take a look at the update process ?

[paulb777]

@BugsBunnyBR The fix won't come until Protocol buffers releases 3.10.0. 3.9.2 was a single patch to 3.9.0 fix a crash issue (#3851).

[BugsBunnyBR]

Ohh... I looked for the 6464 PR merge tag and it was in a release... but it was for version for 3.10 RC1, I should pay more attention.

[paulb777]

Protobuf 3.10.0 has been published to CocoaPods. Doing some additional Firebase integration testing today.