wordpress-mobile / wordpress-mobile/WordPress-iOS

Crash when tapping a P2 post from a comment

Open
#21,987 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

[Pri] Low [Type] Crash Notifications
Dominant language
Swift
Stars
3.9k
Forks
1.2k
Avg merge
23h 51m
Merged PRs (30d)
58

Description

We have a TestFlight user report:

I was looking at a P2 comment and clicked to see the post

Crash report via TestFlight
Exception Type:  EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Termination Reason: SIGNAL 6 Abort trap: 6
Terminating Process: Jetpack [4980]

Triggered by Thread:  0

Last Exception Backtrace:
0   CoreFoundation                	0x1b51a0870 __exceptionPreprocess + 164 (NSException.m:249)
1   libobjc.A.dylib               	0x1ad4bbc00 objc_exception_throw + 60 (objc-exception.mm:356)
2   Foundation                    	0x1b470ad18 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 188 (NSException.m:252)
3   UIKitCore                     	0x1b755d290 -[UITableView _updateVisibleCellsNow:] + 2192 (UITableView.m:3283)
4   UIKitCore                     	0x1b755d120 -[UITableView _updateVisibleCellsNow:] + 1824 (UITableView.m:3346)
5   UIKitCore                     	0x1b755c934 -[UITableView layoutSubviews] + 148 (UITableView.m:10687)
6   UIKitCore                     	0x1b730a670 -[UIView(CALayerDelegate) layoutSublayersOfLayer:] + 1528 (UIView.m:19978)
7   QuartzCore                    	0x1b67201c0 CA::Layer::layout_if_needed(CA::Transaction*) + 500 (CALayer.mm:10804)
8   QuartzCore                    	0x1b671fd48 CA::Layer::layout_and_display_if_needed(CA::Transaction*) + 144 (CALayer.mm:2596)
9   QuartzCore                    	0x1b6726278 CA::Context::commit_transaction(CA::Transaction*, double, double*) + 464 (CAContextInternal.mm:2792)
10  QuartzCore                    	0x1b671f574 CA::Transaction::commit() + 648 (CATransactionInternal.mm:432)
11  QuartzCore                    	0x1b671f21c CA::Transaction::flush_as_runloop_observer(bool) + 88 (CATransactionInternal.mm:942)
12  UIKitCore                     	0x1b7382950 _UIApplicationFlushCATransaction + 52 (UIApplication.m:3153)
13  UIKitCore                     	0x1b7382468 _UIUpdateSequenceRun + 84 (_UIUpdateSequence.mm:119)
14  UIKitCore                     	0x1b7381b58 schedulerStepScheduledMainSection + 144 (_UIUpdateScheduler.m:1037)
15  UIKitCore                     	0x1b7381c14 runloopSourceCallback + 92 (_UIUpdateScheduler.m:1186)
16  CoreFoundation                	0x1b50eb31c __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28 (CFRunLoop.c:1957)
17  CoreFoundation                	0x1b50ea598 __CFRunLoopDoSource0 + 176 (CFRunLoop.c:2001)
18  CoreFoundation                	0x1b50e8d4c __CFRunLoopDoSources0 + 244 (CFRunLoop.c:2038)
19  CoreFoundation                	0x1b50e7a88 __CFRunLoopRun + 828 (CFRunLoop.c:2955)
20  CoreFoundation                	0x1b50e7668 CFRunLoopRunSpecific + 608 (CFRunLoop.c:3420)
21  GraphicsServices              	0x1f84b25ec GSEventRunModal + 164 (GSEvent.c:2196)
22  UIKitCore                     	0x1b7504294 -[UIApplication _run] + 888 (UIApplication.m:3685)
23  UIKitCore                     	0x1b75038d0 UIApplicationMain + 340 (UIApplication.m:5270)
24  Jetpack                       	0x1021763c4 main + 224 (main.swift:7)
25  dyld                          	0x1d7b3adcc start + 2240 (dyldMain.cpp:1269)
Steps to reproduce the behavior

Not yet known

Tested on iPhone 13 Pro, iOS 17.1, Jetpack iOS 23.6 (23.6.0.0)

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

No project files, tests, or entry points are named, and the reproduction steps are not known. Start by tracing the flow from a P2 comment to its post on iPhone and inspect the UITableView crash context; done means the flow no longer crashes under the reported conditions.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios, swift
Domain
mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.