I doubt we are going to get much information for a while.. the people that enjoy doing stuff like this are a dying breed..
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Sideloading iOS Apps No Longer Possible on M1 Macs
- Thread starter MacRumors
- Start date
- Sort by reaction score
I doubt we are going to get much information for a while.. the people that enjoy doing stuff like this are a dying breed..
Previously installed. After this issue( 11.2) I uninstalled and attempted to reinstall using the iMazing method but still same symptoms. Launching app does what I mentioned earlier, just closes Launchpad and shows me the desktop.
I'm confused if the restriction is still in place? I've been hearing some users being able to side load in the past couple days but I've been trying to install some .ipa iOS apps and it keeps throwing me the message "This application cannot be installed because the developer did not intend for it to run on this platform". Can anyone chime in? I'm running Big Sur 11.3 public beta on a 13" MBP M1
Without an M1 Mac of my own I can't directly test, but I'm wondering if the inconsistency has to do with people who side-loaded apps before the update and people who tried to after. Maybe Apple left a bit to flip for people who had already tried that keeps them from losing anything but stops new people from doing so?
I've installed 11.3 but something is different.
I can re-install IPA files that I've previously transferred from my iPhone. I can also run these side-loaded apps without any problem.
However, I just transferred some new IPAs using iMazing (and Apple Configurator 2) but it errors during install:
"This app cannot be installed because it's integrity could not be verified."
The Console (system logs) show the following error:
"The code signature version is no longer supported"
I can re-install IPA files that I've previously transferred from my iPhone. I can also run these side-loaded apps without any problem.
However, I just transferred some new IPAs using iMazing (and Apple Configurator 2) but it errors during install:
"This app cannot be installed because it's integrity could not be verified."
The Console (system logs) show the following error:
"The code signature version is no longer supported"
Have any workarounds surfaced for this? Can't downgrade to 11.x since I'm on a M1 pro that came with 12.X.
There are advanced members of this forum who have been able to add features removed from new versions of MacOS up through Catalina, is this no longer possible because of Apple’s OS signing in order to run it on newer Macs?
I’ve been waiting for some of the MacOS Patcher team to respond, maybe I should ask them directly.
I hope they don’t get tired of fighting Apple’s trying to ‘secure the system’ and just go on to some other OS, I would still like to see a fully open source version of MacOS developed….
You think there should be a law forcing software developers to support their applications on a platform they did not design them for? That's... Entitled.
It’s not a question of support from devs, the arch supports it, if I purchased the app and I want to run it in an unsupported environment I should be able to. I run plenty of programs under WINE, it’s not supported by the developers, but they work just fine and save me some trouble with multi-booting, running full blown VMs just to boot a single app, or carrying multiple machines.
And *as* a developer most of my personal work is on Saas offerings but I also work on part of an on-prem product. We have specific OSes and flavors we support (Windows and certain distros of Linux: Ubuntu, Amazon Linux, and Fedora/RHEL right now). For those we provide Chef recipes, build support, signed packages, etc - not to mention official support channels. We don’t *stop* people from running the software on other systems though, if they purchase it and want to use it in an environment we don’t officially support why do I care? And hell, if enough people do that we may adopt it into official support because it shows us there’s a market (that’s how Amazon Linux got included semi-recently)
it hard ,e.h huawei and apple m1.So we developer not entitled to develop 10% market but still people complain how pricy product price compare cost.
Apple gives the developers the ability to say "no, I don't want to support that". I can see why a developer would not want to... saying "that's unsupported" is utterly meaningless. The Entitled will whine either way.
Android apps barely work on Chromebooks at all in practice, but it's perfectly possible for developers to block them running on Chromebooks if they want to.
I wouldn't say "barely" but some apps can be a little buggy. What would be the upside of blocking apps from Chromebook? Don't you want your apps to have exposure?
Of course as I write this I'm reminded of how sketchy apps can be with privacy opposed to using their website.
And I'm saying I wish Apple didn't and I think creating that blockage is harmful to consumers
Apple has no reason to implement support for Android apps. That is on Google, same as it was for ChromeOS and Windows.