Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Argument header not a recognized key, 'strict_include', or 'providers'. #232

Open
tinyprocessing opened this issue Mar 17, 2023 · 3 comments

Comments

@tinyprocessing
Copy link

ERROR: /Users/#####/Desktop/macosclient/Vendor/Alamofire/BUILD.bazel:219:16: in umbrella_header rule //Vendor/Alamofire:Alamofire_umbrella_header:
Traceback (most recent call last):
File "/Users/#####/Desktop/macosclient/Vendor/rules_pods/BazelExtensions/extensions.bzl", line 113, column 51, in _umbrella_header_impl
objc_provider = apple_common.new_objc_provider(
Error in new_objc_provider: Argument header not a recognized key, 'strict_include', or 'providers'.
ERROR: /Users/#####/Desktop/macosclient/Vendor/Alamofire/BUILD.bazel:219:16: Analysis of target '//Vendor/Alamofire:Alamofire_umbrella_header' failed
ERROR: Analysis of target '//IRMClient:IRMClient' failed; build aborted:
INFO: Elapsed time: 0,083s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (1 packages loaded, 42 targets configured)

@veblush
Copy link

veblush commented Apr 21, 2023

I hit the same problem. I guess this is caused by breaking changes made by Bazel and its default apple rules. Our setup is

  • Bazel 6
  • build_bazel_rules_apple 1.1.3
  • build_bazel_apple_support 1.3.1

veblush added a commit to grpc/grpc that referenced this issue Apr 21, 2023
Oops I missed important changes from
#32712. And it turned out that there
are two problems that I couldn't fix at this point.
- Windows Bazel RBE Linker Error: This may be caused by how new Bazel 6
invokes build tools chain but it's not clear. I put workaround to use
Bazel 5 by using `OVERRIDE_BAZEL_VERSION=5.4.1`
- Rule `rules_pods` to fetch CronetFramework from CocoaPod has
incompatibility with sort of built-in apple toolchain.
(bazel-xcode/PodToBUILD#232): I couldn't find
a workaround to fix this so I ended up disabling all tests depending
this target.
@jalalimehdi
Copy link

I’m dealing with the same problem as you.
How do I fix it?

XuanWang-Amos pushed a commit to XuanWang-Amos/grpc that referenced this issue May 1, 2023
Oops I missed important changes from
grpc#32712. And it turned out that there
are two problems that I couldn't fix at this point.
- Windows Bazel RBE Linker Error: This may be caused by how new Bazel 6
invokes build tools chain but it's not clear. I put workaround to use
Bazel 5 by using `OVERRIDE_BAZEL_VERSION=5.4.1`
- Rule `rules_pods` to fetch CronetFramework from CocoaPod has
incompatibility with sort of built-in apple toolchain.
(bazel-xcode/PodToBUILD#232): I couldn't find
a workaround to fix this so I ended up disabling all tests depending
this target.
wanlin31 pushed a commit to grpc/grpc that referenced this issue May 18, 2023
Oops I missed important changes from
#32712. And it turned out that there
are two problems that I couldn't fix at this point.
- Windows Bazel RBE Linker Error: This may be caused by how new Bazel 6
invokes build tools chain but it's not clear. I put workaround to use
Bazel 5 by using `OVERRIDE_BAZEL_VERSION=5.4.1`
- Rule `rules_pods` to fetch CronetFramework from CocoaPod has
incompatibility with sort of built-in apple toolchain.
(bazel-xcode/PodToBUILD#232): I couldn't find
a workaround to fix this so I ended up disabling all tests depending
this target.
@hiepthai
Copy link

This patch may provide a temporary solution to this issue.

http_archive(
    name = "rules_pods",
    urls = ["https://github.com/bazel-xcode/PodToBUILD/releases/download/4.1.0-412495/PodToBUILD.zip"],
    patches = ["//third-party:podtobuild/objc-provider.patch"],
    patch_args = ["-p1"],
)

objc-provider.patch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants