bazelbuild / bazelbuild/rules_apple
Xcode14 App Store Connect watchos_application stub fat binary issue
- Dominant language
- Starlark
- Stars
- 593
- Forks
- 334
- Avg merge
- 16h 48m
- Merged PRs (30d)
- 9
Description
Hi!
After upgrading to Xcode 14, our app is rejected by App Store Connect during validation because watchos_application stub binary has more architectures than our watchOS extension. I tried a hack to strip those unnecessary architectures and our app can pass connect validation again. I am looking into a fix but it seems I can't access multi arch info for lipo in _watchos_application_impl. Is there anyway i can access all architectures in watchos_application_impl or should I create a implicit dependency with a transition on it?
Related: https://github.com/bazelbuild/rules_apple/issues/704
Contributor guide
Research direction
Start by reading _watchos_application_impl and watchos_application_impl to determine how architecture information is handled, then review related issue 704 for context. Done means a supported fix allows the watchos_application stub to pass App Store Connect validation without the manual architecture-stripping hack.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100