9

I launch the Accessibility Inspector from within Xcode but it doesn't let me interact with elements in the simulator.

I relaunched Xcode, the Accessibility Inspector and simulator but it doesn't seem help.

The simulator I'm using is for iPhone 12.

Accessibility Inspector not working on iPhone 12 simulator

Any ideas?

Sara
  • 105
  • 1
  • 5
  • 1
    It hasn't been working for a while for me either... – aheze Mar 24 '22 at 23:08
  • Does it work on any of the other simulators? I suspect not. I rarely upgrade Xcode quickly and when I do I retain my old installs (by renaming them) and manually downloading the latest version. I’d suggest doing that in the future. Old version can still be downloaded from Apple. – Mike Collins Mar 25 '22 at 15:13
  • 1
    Yea... I also opened a topic on Apple's Developer forum today with the exact same issue. Accessibility Inspector is totally broken in Xcode 13.3, the only way to make it work is to go back to 13.2.1, which is quite sad if you use SPM in your project, the Package.resolved thing is not compatible between the two versions of Xcode and switching between them is a pain. – Andy Mar 25 '22 at 21:44

2 Answers2

5

I know that is very painful when something not working after updates, but my friend told me that we can use real device instead of simulator with Accessibility Inspector. It working fine, even convenient usage of real device with this app. Pick your device over here, when it is connected to Mac

enter image description here

matsotaa
  • 105
  • 5
4

Apple often seems to inadvertently break testing tools, especially the Test Recorder and Accessibility Inspector. I'd suggest you use an older version of Xcode until you have a strong need to upgrade. These can be downloaded from Apple's More Downloads page.

If you wish to retain 13.3 I'd suggest renaming it to Xcode_13_3.app prior to installing a prior version, which will install as Xcode.app.

I also highly advise against using the App Store to keep your Xcode up to date (if that's what you're doing). Instead manually download new versions via the link above and rename old versions (in case you find broken things in the new one) also as described above.

Mike Collins
  • 4,108
  • 1
  • 21
  • 28
  • 4
    This is so true and it raises a few questions about how and if Apple engineers are actually using the provided testing tools if things are broken so often... – Andy Mar 25 '22 at 21:46
  • 1
    @Andy ‍♂️I never use either of those tools. They're pretty terrible once you're handy in the debugger. Or maybe I never gave them a chance because they were always broken. – Mike Collins Mar 27 '22 at 02:44
  • 2
    I only use them for Accessibility stuff and UI testing (more like debugging UI tests) and I found Accessibility Inspector to be pretty useful. I filled a bug report via Feedback Assistant, will see if apple fixes this. – Andy Mar 27 '22 at 09:23