Error: 'struct' value has no field or method 'AppleDynamicFramework'

[vorburger]

#254 revealed the following problem, which has got nothing to do with Bazel Steward per se:

$ bazelisk mod graph --depth=1

<root> (@_)
├───[email protected]
├───[email protected]
├───[email protected]
├───[email protected]
├───[email protected]
├───[email protected]
└───[email protected]


 no actions running
ERROR: Traceback (most recent call last):
        File "/home/vorburger/.cache/bazel/_bazel_vorburger/a3cf8df34f0c7a76e9926daaad9ffbf4/external/rules_apple+/apple/internal/apple_xcframework_import.bzl", line 775, column 21, in <toplevel>
                apple_common.AppleDynamicFramework,
Error: 'struct' value has no field or method 'AppleDynamicFramework'
Available attributes: Objc, XcodeProperties, XcodeVersionConfig, apple_host_system_env, apple_platform, apple_toolchain, compilation_support, dotted_version, get_apple_config, get_cpu, get_split_build_configs, get_split_prerequisites, new_objc_provider, platform, platform_type, target_apple_env
ERROR: @@bazel_tools//tools/cpp:cc_configure.bzl does not export a module extension called cc_configure_extension, yet its use is requested at https://bcr.bazel.build/modules/abseil-cpp/20240722.0/MODULE.bazel:23:29
ERROR: Error loading '@@rules_apple+//apple:apple.bzl' for module extensions, requested by https://bcr.bazel.build/modules/rules_apple/3.5.1/MODULE.bazel:27:48: at /home/vorburger/.cache/bazel/_bazel_vorburger/a3cf8df34f0c7a76e9926daaad9ffbf4/external/rules_apple+/apple/apple.bzl:27:5: initialization of module 'apple/internal/apple_xcframework_import.bzl' failed: at /home/vorburger/.cache/bazel/_bazel_vorburger/a3cf8df34f0c7a76e9926daaad9ffbf4/external/rules_apple+/apple/apple.bzl:27:5: initialization of module 'apple/internal/apple_xcframework_import.bzl' failed
ERROR: Results may be incomplete as 2 extensions failed.

I don't know even what pulls along rules_apple+ ... I'm not (directly) using it!

[vorburger]

@lukaszwawrzyk can Bazel Steward still work if such a failure occurs?

Or does this have to be fixed, first? If so, should Bazel Steward abort when this occurs, instead of logging but ignoring it?

Just wondering.

[vorburger]

I've now found (in #1146) that this error does not actually appear to cause any other problems, so it seems like it's safe to just compltely ignore (in this context).

[vorburger]

Oh, actually... no - this is probably the reason why it (Bazel Steward) failed to detect the availability of an upgrade for rules_go!

So it should be fixed. Either Bazel Steward should become more robust and work despite this, or whatever causes this ("upstream") should be fixed.