Skip to content

Conversation

@MouadBenjrinija
Copy link
Contributor

Resolves tuist/tuist#6914

Short description 📝

The change introduced in this PR #865 caused the Fastlane's automatic_code_signing action to fail, although the original PR author did recommend not merging that PR until Fastlane merges the other -unfortunately forgotten- PR fastlane/fastlane#23872 (which was supposed to fix the issue from Fastlane action side). It was recommended by @fortmarek here to revert these changes.

Solution 📦

The fix is to revert the other PR's changes, by allowing empty TargetAttributes entry to be generated again. (at least until Fastlane fixes the issue from their side).

Implementation 👩‍💻👨‍💻

  • Allow empty TargetAttributes.
  • Fix unit tests (previous unit test were always successful even if the TargetAttributes was empty, because they used to point to the wrong place in the dictionary - always resulting nil - )

@fortmarek fortmarek changed the title fix: Allow empty PBXProject.TargetAttributes fix: allow empty PBXProject.TargetAttributes Apr 7, 2025
@fortmarek fortmarek merged commit e3cbc98 into tuist:main Apr 7, 2025
6 of 7 checks passed
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

Successfully merging this pull request may close these issues.

Tuist + Fastlane - automatic_code_signing issue - missing TargetAttributes

2 participants