Maniphest T248435

Crash after Smart Invert
Closed, InvalidPublic
Actions

Assigned To

Authored By

	• MattCleinman
	Mar 25 2020, 12:04 AM

Tags

Referenced Files

	F31700632: crashlog.crash
	Mar 25 2020, 12:04 AM

	F31700631: feedback.json
	Mar 25 2020, 12:04 AM

Subscribers

• MattCleinman

Description

Found when investigating https://phabricator.wikimedia.org/T235197

Wikipedia app was open.W as in dark mode on iOS.
Went to Settings, turned on Smart Invert.
Reopened Wikipedia app, and it crashed.

Logs attached.

feedback.json746 BDownload

crashlog.crash83 KBDownload

Related Objects

Mentioned In: T235197: Smart Invert problem with iOS 13
Mentioned Here: T235197: Smart Invert problem with iOS 13

Event Timeline

• MattCleinman created this task.Mar 25 2020, 12:04 AM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMar 25 2020, 12:04 AM

LGoto triaged this task as Low priority.Mar 30 2020, 6:53 PM

LGoto moved this task from Needs Triage to Bug Backlog on the Wikipedia-iOS-App-Backlog board.

LGoto added a project: iOS-app-v6.6.1-Penguin-On-A-Luge.

• JMinor moved this task from Tasks from Product Backlog to Needs Engineering Sync on the iOS-app-v6.6.1-Penguin-On-A-Luge board.May 6 2020, 9:14 PM

• Dmantena claimed this task.May 19 2020, 4:31 PM

• Dmantena moved this task from Needs Engineering Sync to Doing on the iOS-app-v6.6.1-Penguin-On-A-Luge board.

• Dmantena mentioned this in T235197: Smart Invert problem with iOS 13.May 19 2020, 5:43 PM

Hey @MattCleinman – any chance you still run into this issue? Been trying to repro as part of investigating https://phabricator.wikimedia.org/T235197 with our recent master builds/iOS 13.4.1 but have so far come up empty. Been using both Smart Invert and the Classic Invert. Just wanted to be sure I wasn't missing something obvious.

@Dmantena While I promise you I didn't file this Phab ticket until I replicated it a couple times, I also cannot replicate this. You're not missing anything. Thanks for checking - and feel free to close out.

@MattCleinman Cool - thank you for checking again! I'm glad at some point in history some commit fixed this.

Haven't been able to reproduce – closing.