CodeTrial crashes when starting an interview on macOS 26 arm64

Open
#56 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
macos, rust
Domain
desktop

Research direction

Start by reproducing the crash with codetrial-aarch64-apple-darwin on macOS 26 arm64, then inspect the interview-room dispatch path reached after the room is dispatched. Investigate the NSInvalidArgumentException involving NSString and string conversion. Done means the mock interview starts normally without terminating the process on this environment.

Written by the indexing model from the issue text.

Description

Description

CodeTrial crashes when starting a mock interview on macOS 26 with Apple Silicon.

CodeTrial starts normally and the web interface is accessible at http://127.0.0.1:3000. However, after starting an interview and dispatching the interview room, the process terminates with an NSInvalidArgumentException.

Environment

  • macOS: 26.6.2
  • Architecture: arm64 (Apple Silicon)
  • CodeTrial binary: codetrial-aarch64-apple-darwin

Steps to reproduce

  1. Run codetrial-aarch64-apple-darwin.
  2. Open http://127.0.0.1:3000 in a browser.
  3. Start a mock interview.
  4. Wait for CodeTrial to dispatch the interview room.
  5. The CodeTrial process crashes immediately after the room is dispatched.

Actual behavior

The terminal shows:

codetrial dispatch room=interview-0vbuf7wc

*** Terminating app due to uncaught exception 'NSInvalidArgumentException',
reason: '+[NSString stringForAbslStringView:]: unrecognized selector sent to class 0x1f612e100'

libc++abi: terminating due to uncaught exception of type NSException
zsh: abort codetrial-aarch64-apple-darwin

Expected behavior

The interview should start normally after the room is dispatched instead of terminating the CodeTrial process.

Dominant language
Rust
Stars
54
Forks
8
Avg merge
11h 57m
Merged PRs (30d)
44

Contributor guide

No contributing guide indexed for this repository

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.

More from sysprog21/codetrial

All issues in sysprog21/codetrial

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.