MobileNativeFoundation / MobileNativeFoundation/rules_xcodeproj
Invalid Index Stores Warning
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 626
- Forks
- 124
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I have a project where I frequently see the following (and similar) warnings:
warning: Previous run of "import_indexstores" had output:
warning: error: invalid index store directory /var/tmp/path/to/some/module.indexstore
warning: If you believe this is a bug, please file a report here: https://github.com/MobileNativeFoundation/rules_xcodeproj/issues/new?template=bug.md
Command PhaseScriptExecution emitted errors but did not return a nonzero exit code to indicate failure
When I inspect these directories, they are always empty.
The specific module affected by the warning is nondeterministic, however the target always seems to always be a swift_library. It does not appear when building via the command line using bazel build .... I was unable to create a minimal repro, which combined with the nondeterminism makes me suspect that the project perhaps needs to be of a certain size or complexity. I do not observe any negative side effects in actually building and running the app due to these messages.
I am using rules_xcodeproj version 2.3.1. I am using rules_swift_package_manager.
This is my bazelrc:
common --enable_bzlmod
common --color=yes
build --java_runtime_version=remotejdk_17
build --tool_java_language_version=17
build --tool_java_runtime_version=remotejdk_17
test --test_output=errors
test --test_verbose_timeout_warnings
build --repo_env=BAZEL_CXXOPTS="-std=c++14"
build --cxxopt='-std=c++14'
build --host_cxxopt='-std=c++14'
build:rules_xcodeproj --apple_generate_dsym
build:rules_xcodeproj --output_groups=+dsyms
I have not otherwise changed the rules_xcodeproj flags.
Thank you!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report names no source files or tests. Start by reproducing the Xcode build with rules_xcodeproj 2.3.1 and compare it with the command-line bazel build, focusing on the nondeterministic import_indexstores warning for swift_library targets and the empty index store directories; done means identifying a reproducible cause and a verified fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100