Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jetpack App Crash When Trying to Publish #21218

Closed
thabotswana opened this issue Aug 1, 2023 · 2 comments
Closed

Jetpack App Crash When Trying to Publish #21218

thabotswana opened this issue Aug 1, 2023 · 2 comments

Comments

@thabotswana
Copy link

A user reported that when they tap "Publish" in the app, it crashes.

I found a Sentry report with the following error:

NSInternalInconsistencyException: Invalid update: invalid number of items in section 0. The number of items contained in an existing section after the update (6101) must be equal to the number of items contained in that section before the update (9), plus or minus the number of items inserted or deleted from that section (0 inserted, 0 deleted) and plus or minus the number of items moved into or out of that section (0 moved in, 0 moved out). Collection view: <UICollectionView: 0x1058aa200; frame = (0 0; 430 807); clipsToBounds = YES; gestureRecognizers = <NSArray: 0x283e1afa0>; backgroundColor = <UIDynamicProviderColor: 0x283130ac0; provider = <__NSMallocBlock__: 0x283f366d0>>; layer = <CALayer: 0x2837f8f20>; contentOffset: {0, -56}; contentSize: {430, 428}; adjustedContentInset: {56, 0, 34, 0}; layout: <UICollectionViewFlowLayout: 0x104421420>; dataSource: <WPMediaPickerViewController: 0x10588da00>>

User/device details

Ticket link: 6595660-zen
App version: 22.8.0.3
Device model: iPhone15,3
OS version: iOS 16.6
Type of site: Jetpack

@peril-wordpress-mobile
Copy link

Fails
🚫

Please add a type label to this issue. e.g. '[Type] Enhancement'

🚫 Please add a feature label to this issue. e.g. 'Stats'

Generated by 🚫 dangerJS

@kean
Copy link
Contributor

kean commented Aug 1, 2023

Thanks for the report, @thabotswana. The team is currently investigating this crash, which is being tracked in the following issue #21102. I'm going to close this one as a duplicate. Thanks for the additional context.

@kean kean closed this as completed Aug 1, 2023
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

No branches or pull requests

2 participants