After packaging the iOS application, I installed it on Apple's physical machine, but when it ran, it showed that it was not supported.

[mymane1433223]

I don't know what to do, do I need to use xcode or other tools?

[mhsmith]

How exactly did you install it, and what exactly happened? Please post logs if you have any, or screenshots of any on-screen messages.

[mymane1433223]

I first packaged my project using Beeware and compressed the generated. app file into a folder named Payload. zip and changed the extension to. ipa. I signed the software with my Apple ID using iTools (website i4. cn) (which recognized it as an IPA software and successfully parsed its icon, indicating that the package as. ipa may be correct). Then, I installed the signed software on my iPad 9 using this tool, with the system version being iOS 26. The following is what it displays when running the softwar

[mymane1433223]

I think it's possible that Beeware's iOS packaging doesn't support iOS 26 yet

[mhsmith]

Google translation:

So it sounds more like the OS version than the architecture. Unfortunately I don't know what would cause this. @freakboy3742: any ideas?

[freakboy3742]

I haven’t done any testing with iOS 26 (and the related Xcode versions) yet. I’d be surprised if there are any incompatible changes, but it’s possible there might be.

However, the process you’ve described to get the app onto your phone (manually creating your own zip and renaming it to IPA) sounds much more likely to be the source of the problem. Apple provides tools in Xcode to build IPAs and ship them to your phone. That is the process that BeeWare supports as well. If you get this “wrong architecture” failure using Xcode or Briefcase, using the processes that Briefcase documents, then that’s a bug we can investigate. But if you’re having problems with your own hand-rolled packaging infrastructure, then you’re responsible for diagnosing the source of those problems.

[mhsmith]

Apple provides tools in Xcode to build IPAs and ship them to your phone. That is the process that BeeWare supports as well. If you get this “wrong architecture” failure using Xcode or Briefcase, using the processes that Briefcase documents, then that’s a bug we can investigate.

Actually I can't find any instructions in the Briefcase documentation for installing on a physical iOS device. The best I can find is a GitHub issue (#860). Just a few days ago Stan created an issue suggesting we migrate this to the documentation and add a message in the UI linking to it (#2364).

[freakboy3742]

That’s fair - and yes we should document this (or fix the underlying issue of deploying to device from the command line). But it’s also fair to say that we don’t support “roll your own” IPA construction mechanisms.