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

App crashes when opened with VoiceOver if the initial page is Home #19609

Closed
ovitrif opened this issue Nov 16, 2022 · 0 comments · Fixed by #19751
Closed

App crashes when opened with VoiceOver if the initial page is Home #19609

ovitrif opened this issue Nov 16, 2022 · 0 comments · Fixed by #19751
Assignees
Labels

Comments

@ovitrif
Copy link
Contributor

ovitrif commented Nov 16, 2022

Expected behavior

The app should not crash when opened with VoiceOver, since normally it's optimized for Accessibility and VoiceOver.

Actual behavior

When VoiceOver is enabled and the WordPress or Jetpack app is opened, if the initial page is Home (not Menu!) , it crashes.

The same happens if the initial page is Menu and the user attempts to open Home (though not always, I could reproduce the persistent crash in Landscape orientation).

Steps to reproduce the behavior

The issue reproduces both on WordPress or Jetpack app if the repro steps are followed:

  1. Make sure initial page is set to Home
    • Open app (log in if needed)
    • tap MeApp SettingsInitial Screen
    • Make sure Home is selected or select it otherwise.
  2. Close the app
  3. Enable VoiceOver on your device
  4. Try to open the app
  5. Notice the app crashes.
    There is no way to recover from this issue with VoiceOver enabled.
CrashOnVoiceOverLaunchHome.mp4

P.S. I set the priority to Medium since users can never open the app in this scenario with VoiceOver enabled. Feel free to update this if it's more suited for Low.

Tested on iPhone 11 Pro Max, iOS 16.1, WPiOS & JPiOS 21.2.0.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants