Downstream modulemap issue with using Firestore with Bazel rules_swift_package_manager

[jeffhodsdon]

Hiya! Sorry this is a shot in the dark downstream issue that I wonder if the issue is within here —

In short— within the .zip'ed grpcpp.xcframework release the module.modulemap contains an invalid name for the framework module.

framework module gRPC-C++ {
umbrella header "gRPC-C++-umbrella.h"
export *
module * { export * }
  link "c++"
  link "z"
}

From my understanding, the name gRPC-C++ contains invalid characters for a module name. (I guess that is why cpp is used in other places.

Somehow, this is causing an issue during a compile process that I have not go to the bottom of yet. Possibly, because Firestore is still linking to this as a ObjC dep and this is never used? CLANG_ENABLE_MODULES = NO

It's increasingly popular to use Bazel in the ios build process and would love to get this working. Any insights would be helpful. thank you!

[jeffhodsdon]

Adding context—

Name chanted to cpp other places:
https://github.com/google/grpc-binary/pull/10/files/c05d38a44099bca80dec10676e969d5d26d88fc6

Rules swift package manager first seen:
cgrindel/rules_swift_package_manager#1778

[ncooke3]

Thanks @jeffhodsdon, this should be fixable. I'll take a closer look.

[jeffhodsdon]

Thanks @jeffhodsdon, this should be fixable. I'll take a closer look.

You the best! Thank you for such a speedy reply!!

[ncooke3]

Hi @jeffhodsdon, https://github.com/google/grpc-binary/releases/tag/1.69.1 is released. This should resolve the issue. Firebase should float to pick his up when you update to the latest package versions.