Both of the newer versions will debug just fine using the simulator, but not on the iPad hardware.
Is this a known issue? I assume there’s nothing wrong with my Apple developer profile since 2023r2 builds without issue.
I’d really like to use the newer versions of Xojo so I can use the MobileTextField’s FocusLost event, but having on-device debugging is a must. (the app needs to support the Apple Pencil)
Some additional details:
Latest MacOS, fully updated --14.3.1 (23D60))
Latest XCode, fully updated – Version 15.2 (15C500b)
iPad is (intentionally) running iOS 16.7.5
iPad is attached to the Mac running Xojo via a USB cable (trying to debug over Wifi throws the same error)
Any tips on how to get Xojo to debug on hardware (an iPad) with newer versions than Xojo 2023r2?
Is this somehow Apple-profile/XCode issue even though everything works as expected with 2023r2?
I have had this issue sporadically with 2023r3.1 but quitting Xojo and restarting usually resolves it. I also had this issue with 2023r4 and was unable to resolve it but the good news is that it has been fixed in 2024r1 so either jump into the beta or wait for it to ship.
Are you logged in Xcode? (using your Apple Developer Account)
Have you accepted any pending update to Apple Developer contracts / agreements?
Do you have the correct combo of Certificates / Profiles for the app you intend to run?
Is the Wi-Fi enabled in the iPad? (in addition to on macOS, even if the iPad is connected via USB) Xcode 15 requires it.
Have you accepted the dialog that is shown on the iPad about “trusting this Mac”?
When you open Xcode > Devices and Simulators, is the iPad available for installing / run-debug apps on it?
You can try this:
In Xcode > Devices and Simulators click on the connected device (iPad) and select the option “Unpair Device” from the contextual menu.
Once completed, disconnect the iPad and connect it again and pair it.
Also, as pointed by @DerkJ , you can give a try to the available 2024r1 builds in the Testers channel on the Forum. We made some changes… and maybe that ones could help in your scenario.
Forgot to mention, I can still successfully debug on hardware using Xojo 2023r2, however, 2023r2 doesn’t have the FocusLost event for MobileTextField controls which is an event I could really use…
I believe i still have the same issue, i’m testing it now.
Ok the iPad i tried is and 2016 iPad Pro, that has currently maxed out at version 16.7.5 and is not capable of ipad os 17.x
Latest XCode, fully updated – Version 15.2 (15C500b)
iPad running latest iOS 17.3.1
iPad is attached to the Mac running Xojo via a USB cable (trying to debug over Wifi throws the same error)
Still seeing the “Compilation of [APP NAME] failed.” dialog when trying to debug on hardware.
This occurs with a blank/new iOS project in both the latest production and beta versions of Xojo.
The beta version has no plugins other than those included with the installer.
I’d really like to be able to debug on hardware; it’s a pretty key aspect of developing for iOS since the UX is quite different when using an actual device.
What are next steps/best practices for attempting to root cause & fix this issue?
I was able to get the latest Xojo production build debugging on my iPad (with latest iOS version)
Steps I took:
created a new “iOS App” project in Xcode with default settings
saving this app
attempting to debug this new app on hardware (my iPad) in Xcode
This caused an alert I’d never seen before to appear in Xcode saying something along the lines of:
“[iPadName] is not a registered device for this developer account, would you like to register it?” (apologies, I don’t remember the exact text of the dialog)
After this the Xcode app launched
I then attempted to debug on iPad hardware with Xojo.
This time I got an “allow debugging/trust” dialog on the iPad (again, sorry don’t remember the exact text) and hit “yes” and entered my iOS device’s passcode.
After this, I’ve been able to successfully run debug app on iPad hardware.
This all feels a bit “voodoo” but maybe someone who has a deeper understanding will be able to glean the root cause and provide more concise steps or identify a possible bug/missing case in Xojo so it can either fix the problem or better prompt the user on how to fix the issue.
I’d say the closest thing to a solution was @Tim_Parnell 's pointing out the iOS version requirement for debugging (must be iOS 17.0 or greater), so I’m marking it as the solution.
Thanks again to everyone for their suggestions & help!
Anthony