XcodesOrg / XcodesOrg/xcodes

unable to authenticate with Apple ID using hardware two-factor key (Yubikey)

Open
#279 8 comments 20 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Swift
Stars
4.8k
Forks
182
Avg merge
2d 12h
Merged PRs (30d)
1

Description

Running xcodes 1.3.0 on Ventura 13.2.1, getting a login error with my Apple ID. It is configured to use a hardware key for authentication.

xcodes install 14.3 Beta 2 --experimental-unxip
Apple ID: <my_apple_id@mail.com>
Apple ID Password: xxxxxx
The operation couldn’t be completed. (DecodingError.keyNotFound(CodingKeys(stringValue: "securityCode", intValue: nil), Swift.DecodingError.Context(codingPath: [], debugDescription: "No value associated with key CodingKeys(stringValue: \"securityCode\", intValue: nil) (\"securityCode\").", underlyingError: nil)))
The operation couldn’t be completed. (DecodingError.keyNotFound(CodingKeys(stringValue: "securityCode", intValue: nil), Swift.DecodingError.Context(codingPath: [], debugDescription: "No value associated with key CodingKeys(stringValue: \"securityCode\", intValue: nil) (\"securityCode\").", underlyingError: nil)))

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing xcodes install 14.3 Beta 2 --experimental-unxip with an Apple ID protected by a YubiKey on the reported macOS setup. Trace the authentication response that produces the missing securityCode error and compare it with the expected hardware-key flow. Done means the login completes without the decoding failure and the Xcode installation proceeds.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, swift
Domain
authentication, cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.