Thanks, Quinn! How much should I worry about this error? It sounds scary, but is it something I can even fix?

Hmm, it works for me both in the simulator and on my iPhone running iOS 26

Thank you!

Filed FB18022139

Thank you!

I think the "X" button just doesn't work in UIKit. I have a simple tip on a UIBarButtonItem and I have a task running that monitors shouldDisplayUpdates. Nothing happens when I tap the "X". I can tap outside of the tip to dismiss it, but the "X"is totally ignored. I had to make my own custom TipViewStyle implementation to get rid of the X. My users kept trying to tap it and not getting any reaction.

These other apps are able to do all of those things, and yet they switch control to the receiving app instead of just appearing over the sending app like a share extension. How can I do the same in my app?

Thanks - I'm aware of share extensions, but they appear above the sharing app and are totally separate from the main app's data. Using a share extension is going to require breaking down my code into frameworks and also finding ways to update shared data that the share extension can use from my main app. If I can simply open the image in my app (as in the example apps I mentioned above), then all of that complexity is gone.

I'm getting this warning too, apparently from calling heicData. Do I actually need to worry about this? It sounds like it just defaults to skipping the alpha and sort of fixes the problem itself, right?

Thanks - this worked for me.

@DTS Engineer This is on iOS and iPadOS - thanks for replying.

This is on iOS and iPadOS.

@ppix That's strange - I resolved this issue by only accepting the connection that reached .ready. The other three end up .canceled

Thanks for the reply! I'd been hesitating to migrate to Network.framework but after reading your reply, I decided to give it a shot. It only took a few hours, and now this problem (and several others!) are resolved.

Has anything changed with this answer with the announcement of iOS 18? Thanks!