We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The app shouldn't crash.
There are Sentry events (2 in 23.4, 1 in 23.5 so far) for a crash when opening the privacy screen, but I couldn't reproduce it.
I couldn't reproduce this when navigating to Me > App Settings > Privacy Settings.
Based on the error message UIViewController is missing its initial trait collection populated during initialization, I thought it might be similar to #17228 (see https://stackoverflow.com/questions/69092599/xcode-13-beta-5-error-uiviewcontroller-is-missing-its-initial-trait-collection), but there's no Obj-C code in the stack trace so this might be different.
UIViewController is missing its initial trait collection populated during initialization
The text was updated successfully, but these errors were encountered:
Sentry issue: JETPACK-IOS-WRM
Sorry, something went wrong.
This screen is removed in 24.9 – see #23154
Successfully merging a pull request may close this issue.
Expected behavior
The app shouldn't crash.
Actual behavior
There are Sentry events (2 in 23.4, 1 in 23.5 so far) for a crash when opening the privacy screen, but I couldn't reproduce it.
Steps to reproduce the behavior
I couldn't reproduce this when navigating to Me > App Settings > Privacy Settings.
Tested on iPhone 11, iOS 17.1, Jetpack iOS 23.5
Additional info
Based on the error message
UIViewController is missing its initial trait collection populated during initialization
, I thought it might be similar to #17228 (see https://stackoverflow.com/questions/69092599/xcode-13-beta-5-error-uiviewcontroller-is-missing-its-initial-trait-collection), but there's no Obj-C code in the stack trace so this might be different.The text was updated successfully, but these errors were encountered: