HandleURL broken in 2026r2.1, works in 2026r1.2?

Hey everyone,

I have a production iOS app with login through MS Entra that is working fine when I run in an iPad simulator with Xojo 2026r1.2, but not 2026r2.1.

After upgrading to 2026r2.1 I could no longer log in through MS Entra using our registered custom URL scheme. The login was successful on the MS side, but App.HandleURL was never called when I clicked the custom URL.

When I open the exact same project in 2026r1.2 it works and hits App.HandleURL as expected.

I thought I would check here first to see if anyone had experienced similar issues with 2026r2.1 before I file a bug report.

-Mike

My app uses quite a lot of App.HandleURL but I’m still on 2026r1.2

Thank you for reporting this.

I can’t confirm this myself, but if you’re indeed seeing this @Mike_Gibson I’d recommend crafting a small sample project and filing a report ASAP.

I can’t say for sure, but my guess is that there might be enough time for Xojo to fix for 2026r3. Otherwise, if you wait too long things might be pushed out another quarter beyond r3’s release.

I did end up reporting it.

I’m not sure how easy it will be to recreate, it depends on whether MS Entra has anything to do with it. It seems like it probably doesn’t, but I’m not sure.

Good idea to try, though. I will see if I can make a quick test in a blank app and just use a browser to hit HandleURL.

I was able to make a test project that reproduces it. I attached the repo to my issue.

If anyone wants to confirm:

The issue is #81874. I think it’s public: https://tracker.xojo.com/xojoinc/xojo/-/work_items/81874

If others are experiencing the same issue it might be good for them to know.

You’re awesome! Just tried the test project and I’m definitely NOT seeing HandleURL fire under newer Xojo versions:

Devices
iPad (10th Gen) & iPadOS 18.7.8
Simulator iPad (A16) & iPadOS 26.5

Xojo
Xojo 2026r2.1 » Fails (Device & Simulator)
Xojo 2026r2 » Fails (Device & Simulator)
Xojo 2026r1.2 » Works (Device & Simulator)

Looks like something broke in the 2026r2 build that hasn’t been fixed. Really appreciate you flagging this, creating a sample project and logging the ticket. Personally I’m not heavily invested in custom URLs in iOS these days (but have been in a past life), so I could see this being a pretty deal for yourself and others out there.

Anyone out there who uses HandleURL under iOS/iPadOS should probably give the ticket a :+1:.

Awesome, thanks for duplicating it so I know it’s not something wonky with my sim or machine.

Here’s hoping the fix is something simple that can make its way into 2026r3

Hi @Mike_Gibson

Very probably this was caused by the mandatory change to UIScene based lifecycle on iOS apps.

Thank you for pointing this out! (looking into it) :+1:

–edited–
(…and should be fixed now for the next Release)