[iOS 26] Be My Eyes – Be My AI Can’t Describe Screenshots

By Indra, 15 September, 2025

Forum
iOS and iPadOS

Hi everyone,
I’d like to ask if anyone else has noticed this issue after updating to iOS 26.

When I take a screenshot and then share it to Be My AI for description, I now get a message saying that it cannot access the available photo. This never happened to me on earlier versions of iOS — it only started after updating to iOS 26.

Has anyone else run into this problem with Be My AI on iOS 26?
And if so, is there any workaround?

Thanks!

Options

Comments

By Cliff on Monday, September 15, 2025 - 20:57

Yupp, have seen this behaviour in the betas of iOS 26 for a while, but haven't had the time to repport it to them yet. Really not sure if this is BeMyEyes or Apples bug... In the meantime, going to the Photos app and sharing it from the sharesheet directly from the screenshot there works fine.

By Emily Chia on Tuesday, September 16, 2025 - 01:58

yes, I’ve experienced this as well, but I’ve been on the iOS 26 beta for a while, so I’ve been experiencing this, but I haven’t tested it out yet now on the iOS 26 official release yet, but when on the beta I was experiencing it a lot, I did get it to work a few times though. I just have never gotten around to reporting it or never really thought about reporting it.

By Jessica Tegner on Tuesday, September 16, 2025 - 10:00

Hi.
We are awear of it and a fix will be coming soon.
Jessica / Be My Eyes

By Indra on Friday, September 19, 2025 - 11:46

Hello everyone,

I wanted to follow up regarding the issue I reported a few days ago with Be My Eyes / Be My AI on iOS 26. Unfortunately, the bug is still there. Each time I take a screenshot and try to share it with Be My AI, I keep getting the message: “Unable to fetch the available photo.”

It has been several days now, and honestly, it’s becoming quite frustrating. This feature is something I rely on regularly, and not being able to use it properly has a big impact.

Does anyone know if Be My Eyes is already working on a fix for this? Or perhaps if there’s any estimated timeline for when this will be resolved?

Thanks in advance for any updates or suggestions.

By Lee on Friday, September 19, 2025 - 12:46

There was a post from Jessica I think her name is from BME. They are aware of this and are working on a fix. She didn't give timescales.