Xojo iOS on-device debugging appears broken (again) with iOS 17

Well i don’t know them, those that don’t know.

Well I was able to find fixes for Delphi and Flutter, and of course there was no problem with SwiftUI. Still waiting for Xojo to find a solution…

They have a solution. The case is marked fixed and we just need to wait for the next beat/release.

@DerkJ do you have this working yet in the latest Xojo build? @Javier_Menendez (who has been very helpful, so thank you Javier! :slightly_smiling_face:) says that I’m the only one who has reported an issue building/deploying to device with iOS 17/Xcode 15.

1 Like

Sorry for the double-post but just in case anyone has the same issue I want to post the solution for my situation and shout out to our most valued MVP @Jeremie_L :rocket: :star: who gave me an awesome tip to try Greg O’Lone’s :mage: :magic_wand: fantastic Profile Triage utility. Can you tell I’m excited about solving this? :joy:

I had an invalid certificate for some reason. Weirdly it either happened with the Xcode 14 to Xcode 15 upgrade or at around the same time so I was misdirected on the cause due to the coincidence. Once I connected my developer account, Greg’s utility highlighted the problem and his helpful docs gave me the solution, which was just to regenerate the invalid certificate and allow Greg’s utility to refresh/download it.

I hope this helps anyone else in the same boat and now I shall go and get my update out. :grin:

Edit: In my haste to celebrate the solution I hit the Post button too soon and didn’t acknowledge the helpful and responsive support I received from @Javier_Menendez on this issue too. It’s great to deal with a company where you can get so close to the metal and receive help directly from the developers themselves.

6 Likes

Yes on the latest build i have it working again.

Glad you managed to solve it, @Jason_Tait! :wink:

1 Like

Honestly, I’ve never been able to debug with wildcard profiles — I’ve got to make a new, explicit, profile for each app I experiment (I actually just reuse a few).

Is a general issue with wildcards resolved, or is there an open report for it?

From time ago Apple discourages the use of AppleID with wildcard identifiers. In addition, these only should be used (if you want to) for those cases where there are no Capabilities involved.

as for this issue, i did not have any wildcard identifiers. So this issue was something different at least in my case. Xojo did seem to fix the case.

Yes no wildcard identifiers here either as I use quite a few entitlements. This issue did not seem related to wildcard identifiers.

Yeah, we know it was a different issue; this comment was kind of “note aside” about creating/dealing with Application Identifiers creation on the Apple Developers website. :+1:

1 Like