›_ Claude Code Issues
Claude Code Issues / #70144

[iPadOS] App crashes when opening any session in Code tab (v1.260618.0) — main-thread stack overflow in SwiftUI

Open 💬 26 comments Opened Jun 22, 2026 by swd-ks

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

After updating to 1.260618.0 from the App Store, tapping ANY session in the
Code tab (new or archived) crashes the app instantly. Chat and Cowork tabs
work fine. 100% reproducible. Clean state (reinstall / re-login) does not help.

Crash analysis (symbolicated .ips): main-thread stack overflow, not memory or network.

  • EXC_BAD_ACCESS (SIGSEGV), KERN_PROTECTION_FAILURE at 0x16b603ff8 (inside Stack Guard region)
  • "Could not determine thread index for stack guard region"
  • Faulting thread 0 (com.apple.main-thread), original stack length 175 frames
  • Recursive cycle: AG::Graph::update_attribute -> AGGraphGetValue ->

swift_getTypeByMangledName -> __swift_instantiateGenericMetadata ->
_swift_getKeyPath -> "type metadata completion for WritableKeyPath / ReferenceWritableKeyPath"
SwiftUI session-screen view body recursively re-evaluates through KeyPath generic
metadata instantiation and blows the main-thread stack.
Incident ID: 1BEDF679-BC74-4E84-B728-260360419E73

What Should Happen?

Tapping a session in the Code tab opens it normally without crashing the app.

Error Messages/Logs

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_PROTECTION_FAILURE at 0x000000016b603ff8
Termination reason: "Could not determine thread index for stack guard region"
Faulting thread: 0 (com.apple.main-thread)

Fault address 0x16b603ff8 is inside the Stack Guard region (0x16b600000-0x16b604000),
stack directly above it -> main-thread stack overflow.

Recursive cycle (original stack length 175 frames):
  AG::Graph::update_attribute -> AGGraphGetValue
  -> swift_getTypeByMangledName
  -> __swift_instantiateGenericMetadata
  -> _swift_getKeyPath
  -> type metadata completion function for WritableKeyPath / ReferenceWritableKeyPath
  -> (repeats until stack guard hit)

App version: 1.260618.0 (27777773659)
Device: iPad Pro 11" M2 (iPad14,3)
OS: iPadOS 26.5 (23F77)
Incident ID: 1BEDF679-BC74-4E84-B728-260360419E73

Steps to Reproduce

  1. Update the Claude iOS/iPadOS app to 1.260618.0 from the App Store.
  2. Open the app (launches fine; Chat and Cowork tabs work).
  3. Go to the Code tab.
  4. Tap any session, new or archived.
  5. App crashes instantly. 100% reproducible, every session.

Note: not reproducible via claude.ai/code in Safari on the same device,
which points to the native SwiftUI session screen rather than backend data.
Reinstall and re-login do not help (deterministic, build-specific).

Claude Model

_No response_

Is this a regression?

Yes, this worked in a previous version

Last Working Version

1.260611.1

Claude Code Version

N/A (iOS/iPadOS Claude app, not CLI). App version: 1.260618.0 (build 27777773659)

Platform

Other

Operating System

Other

Terminal/Shell

Non-interactive/CI environment

Additional Information

NOTE: This is the iOS/iPadOS Claude app, not the Claude Code CLI. The CLI-oriented
dropdowns (Terminal/Shell, OS, Claude Code Version, Platform) are filled with
closest-available placeholders. Actual environment: iPad Pro M2, iPadOS 26.5, app 1.260618.0.

View original on GitHub ↗

26 Comments

behrndt · 23 days ago

Confirming on the stable App Store build (not beta): same crash on both iPhone and iPad.

Both devices worked fine until today's app update — immediately after updating, opening or starting any Code session crashes the app instantly. Chat and Cowork tabs are unaffected, and claude.ai/code in a browser works normally against the same sessions. Backend is a Linux VM running claude remote-control sessions.

Reinstalling the app and rebooting the device do not help (consistent with the SwiftUI main-thread stack overflow analysis above — it's the client build, not local state or the backend). Clean independent repro.

BillVerhelle · 23 days ago

Same crash on iPhone, not just iPadOS — and I'm on the exact build this issue flags.

  • Claude Code iOS app version: v1.260618.0 (27777773659) — the same build identified here (last good: 1.260611.1).
  • Device / OS: iPhone running iOS 27.0 Beta 2 (released 2026-06-22).
  • Symptom: App crashes instantly when tapping any session in the Code tab (the session shows a green/active indicator). The crash happens immediately, before the session screen renders.
  • Persistence: 100% reproducible. Restarting the iPhone and force-quitting/relaunching the app did not help.
  • Other tabs: Chat/Cowork tabs open normally — only the Code-tab session view crashes.
  • Session is healthy server-side: the same session opens and runs fine from the desktop CLI and from claude.ai/code in mobile Safari, so this is purely the iOS app's session-screen rendering.

So this reproduces on iPhone (iOS 27.0 Beta 2) as well as iPadOS — same build, same Code-tab session-open crash.

atrusniak-ruz · 23 days ago

I am having the exact same issue iOS app 1.260618.0 hard-crashes opening a Remote Control session — main-thread
▎ stack overflow in Swift KeyPath metadata. iPhone 16 Pro Max, iOS 26.5 (23F77),
▎ CLI 2.1.186 (also repro'd on 2.1.183). Repro: tap any Remote Control session →
▎ instant crash, no UI. Crash: EXC_BAD_ACCESS/SIGSEGV on main thread,
▎ KERN_PROTECTION_FAILURE in the Stack Guard region; ~48 frames of unbounded
▎ recursion in libswiftCore (swift_getTypeByMangledName → decodeMangledType →
▎ createBoundGenericType → _swift_getGenericMetadata → type metadata completion
▎ function for KeyPath/WritableKeyPath, repeating). Started with build 1.260618.0;
▎ 20+ identical crashes in one afternoon. Crash log attached.

darabo · 23 days ago

Can confirm this is also the case for me, on both the iPhone 15 Pro Max and 17 Pro Max. Any attempt to open a session results in the app crashing. Claude Code on the mobile browser works fine.

MichaelRDionne · 23 days ago

I confirm for me as well

jqff4sthn2-oss · 23 days ago

Confirmed. Same

mimeeq-neal · 23 days ago

Also, I have the same. I also just tried to update Claude desktop, open and close it, restart MacBooks, and restart iPhones. It continuously crashes.

shotstars · 23 days ago

Comfirm. just happened after update Claude app version：1.260618.0 (27777773659)

kondrashink · 23 days ago

also confirm

josegtmonteiro · 23 days ago

+1 with same issue

adamjohnschlosser · 23 days ago

I can also confirm on iPhone 17 Pro running iOS 26.5.1 - no issues with Claude app (Claude 1.14271.0 (c8f4d8)) on MacBook running macOS 26.5.1

vishaltanksale · 23 days ago

I'm also facing same issue on iPhone with iOS26.4 and Claude app v 1.260618.0

denpy · 23 days ago

Same crash on iPhone with iOS 26.5 and Claude app version 1.260618.0.

HypocritePro · 23 days ago

Some boat on all iOS devices, an older iPad on the previous release still works. All Claude updated crash the app 100% of the time.

HenrikAberg · 23 days ago

I have the exakt same issue on iPhone 15 PRO, iOS 26.5.

!image

kingassune · 23 days ago

Some boat on all iOS devices, an older iPad on the previous release still works. All Claude updated crash the app 100% of the time.

ShahrumAmiri · 23 days ago

Same issue here on iPhone

adrians5j · 23 days ago

Iphone - same issue 🥲

moby3012 · 23 days ago

Same issue since last update. Also iOS, Iphone.

darabo · 23 days ago

Today's update seems to have fixed the issue for me. Remote sessions also work once again without the app crashing.

Hann9f · 23 days ago

Update fixed the bug today !

behrndt · 23 days ago

Newest Update fixed it for me too 👍

BillVerhelle · 22 days ago

Confirming the latest app build resolves this on iPhone (iOS 27.0 Beta 2) as well — opening sessions in the Code tab no longer crashes. (Was on the affected 1.260618.0; updated and it's fixed.) Thanks for the quick turnaround.

HypocritePro · 22 days ago

Looks like the build they pushed this afternoon fixes it, and it's back up and working on our devices

adamjohnschlosser · 22 days ago

Can confirm the latest build pushed this afternoon fixed the issue

Nice job Claude!

vishaltanksale · 22 days ago

It got fixed in latest update. Thanks Team Anthropic for quick turnaround!