What OP means is that cDock doesn't work when SIP is enabled. So you can't both use cDock and iOS apps.
Last edited:
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.
If you disable SIP, all you iOS apps will stop working on your M1.
- Thread starter MK500
- Start date
- Sort by reaction score
What OP means is that cDock doesn't work when SIP is enabled. So you can't both use cDock and iOS apps.
I understand the definition of PC = "Personal Computer" (which is ANY computer that is "personal", which does go back to the earliest computers, like the Commodore VIC-20), but the commonly known and accepted definition is a computer that runs DOS/Windows. Anyone you ask, who knows about computers, will tell you that. That is also my choice of definition. Just like the word "gay". Tell me you can honestly ALWAYS think of the original definition, if you even know what it was. If you can't, that proves my point. The term "gay" used to mean "happy and carefree". It still CAN mean that, but... betcha not many people will THINK that's what you're saying, if you tell them, "I'm gay".
This is just re-enforces the notion that "reality" is a manufactured thing and you must have a LOT of knowledge in different areas if you really want to know "what is what".
I think Apple knows about this issue already... since iOS apps running on M1 Macs is "a big thing". However, the more people who mention it, the harder/faster Apple will need to address it. For all we know, it could be a simple oversight in the code or something more convoluted and difficult to track down.
But, in my time away from Macs, I've noticed that it seems the users are now the "beta testers". They'd rather get software out to users faster and deal with issues as they're mentioned (assuming there are enough complaints to warrant the NEED to actually fix the problem), than to take the time to make sure there are as few problems as possible before releasing to users. Kind of a Catch-22. Have people complain about issues AFTER you release the product early, or have people complain that you're taking too long to get the product to them. Hmm... tough call.
Oh, silly me, that makes sense.
Although come to think of it, what about macOS app theft? On machines without System Integrity Protection, Apple ought to be disabling macOS apps too.
Oh wait, I forgot, you can pirate macOS apps without disabling SIP. Oh well, I guess Apple will need to disable macOS apps on all Macs. Take that, thieves!
I'm sorry for picking on you! You're probably right, insofar as enumerating Apple's logic—as rediculous as it may be. My ire is with Apple.
Last edited:
This implies that if I plan to keep using cdock, I won’t be able to launch iOS apps when I get my M1 MBP.. which is a huge bummer. Maybe there’ll be an update at some point by W0lfschild to address it. But I doubt it.
While making cDock work with SIP enabled is basically impossible, it does occur to me that... because disabling SIP gives you full control over memory, the kernel, and everything else on your machine, you could potentially also modify whatever is preventing iOS apps from launching. Either patch the process, or tell it that SIP is still on, etc.
It could potentially be a great deal of work though.
Last edited:
Also cDock only needs removal of protections for the filesystem and debugging so maybe with that setup you can still run iOS apps ?
No, I have tried custom csrutil enable --without fs etc, the result is the same, no iOS apps.
From what little research I've just done (going to the cDock github page), it appears to me that cDock is a "hack". SIP is designed to protect the system (System Integrity Protection), as explained on the osxdaily link. Perhaps the reason disabling SIP causes iOS apps to not work, is because the system throws a "red flag" after disabling SIP, which then causes all "beta type features" (this is the first release of 11.0.x for M1 Macs) to stop functioning. If iOS apps have never been able to run on Big Sur (or earlier), this makes a lot more sense. Disabling SIP just throws a massive wrench into the newly installed gears (for running iOS apps) of Big Sur and this fragile process "freaks out".
If iOS apps are running inside a SIP "sandbox", of sorts, it's any wonder disabling it is causing this problem. You're freaking out the SIP Daycare Worker! "The iOS children are running amok! AAAAAAAAH!" ?
If this is the case, it's just a matter of time before Apple addresses this fragility, and disabling SIP won't cause this collapse. One can hope...
But, to expect EVERYTHING to operate "smooth as butter" on day 1 of a brand new release of Big Sur (11.0.1) on a completely new platform (M1 Macs), is expecting a bit much, methinks.
Well, I guess it was fun while it lasted. Maybe there’ll be another solution at some point.
"Hello - I'm a Mac."
"And I'm a PC"
Get a Mac - Wikipedia
...and the wikipedia article also mentions the dispute between "experts" on what a PC means. I guess some people really can't deal with the idea that language is ambiguous and context matters. Meanwhile, I await the first comparative review of the new MacBook Air vs. a large, red juicy but rather flavourless US variety of eating apple.
NB: I've previously dug out old computer magazines pre-1981 and while "Personal computer" definitely pre-dates IBM (heck, one of the magazines was called "Personal Computer World") and the abbreviation "PC" wasn't entirely unknown, it was pretty clear that it was the IBM PC that established "PC" as a household pseudo-brand name. Before that, articles tended to either use "personal computer" in full or "micro" (short for "microcomputer" and/or "microprocessor"). But then there's "PowerPC", "PCMCIA" and numerous products with names of the form "Whizzbang PC1701D". TL
NR: it's ambiguous. Deal with it.The only solid definition of Mac/Macintosh is that it is a trademark of Apple inc. and (outside of the abortive era of official Mac clones) only Mac-branded machines can officially run MacOS, which is sometimes a matter of technology, sometimes simply licensing. (MacOS has unofficially run on things like the Atari ST and Amiga in the past, albeit with hardware hacks). Macs have never been strictly MacOS, though - Apple offered their own (pre-MacOS X) Unix (A/UX) for a while and there were Linux distros - such as Yellow Dog - that ran bare-metal on PPC Macs, and BeOS was around for a while.
What is true is that Intel era Macs have, at times, been so close to... let's call it generic "Wintel PC" hardware that you could just stick in a regular Windows (or PC Linux) installation DVD into some Mac models, install it and have it run tolerably well with just the generic or downloaded 3rd party drivers (I've done that on the original Mac Pro with Windows XP). The flipside of that is that Intel-era MacOS is able to run on carefully-selected, but generic, "Wintel PC" hardware with only superficial (but clever - kudos to the Hackintosh community) software hacks. So, yeah, the Intel Macs (up until the introduction of the T2) were arguably closer to "Wintel PCs" than ever before or since.
cDock works via code injection. You can call that a hack if you want, but I think it's an important and beautiful thing about the desktop.
When Dropbox started out, it used code injection to add syncing features into Finder. It doesn't need to do that anymore, because Apple added native APIs for this stuff—but only after Dropbox paved the way by showing demand. Who knows what ideas would never have been tried if code injection were impossible? I feel very strongly that these abilities are critical.
The thing is, merely disabling SIP doesn't do anything on its own, it just tells the kernel to not prevent certain actions. So it really shouldn't be causing problems on its own—unless Apple explicitly added some sort of check.
Last edited:
One thought: are people just turning SIP on/off or are they enabling "reduced security mode" as described in the video and/or have they checked what "CSRUtil disable" actually does on M1 machines (I don't have one to try)?
Explore the new system architecture of Apple silicon Macs - WWDC20 - Videos - Apple Developer
Discover how Macs with Apple silicon will deliver modern advantages using Apple's System-on-Chip (SoC) architecture. Leveraging a unified...
...my reading of that is that "reduced security mode" disables a raft of security features including "secure boot" and enables booting of unsigned OSs (the video doesn't mention SIP at that point). It also suggests that the command-line CSRUtil enables finer control (...but I couldn't find full docs - the pre-M1 version just seems to turn SIP on/off).
If we're talking about turning off secure boot ans OS signing then disabling iOS is probably by design and any fix may be limited to a suitable "here be dragons" warning, if there aren't already enough when you switch to reduced security.
Think about it - an iPad or iPhone are locked down to the equivalent of the highest MacOS security level, with no option to turn it off (without an unofficial jailbreak). Apple would surely impose the same level of lockdown on MacOS if they thought they could get away with it - but it would not be accepted by Mac "power users" and developers - at least for Mac OS apps. But when it comes to the "bonus feature" of running iOS Apps on Mac it makes complete sense that Apple would impose the same level of security on those as they get on an iDevice.
Even the failure to re-instate iOS Apps after returning to full security mode may be a feature rather than a bug: once the Mac has been run in reduced security mode, the OS may have been compromised.
If we're just talking about SIP then this is a bit less obvious - but still, Apple may regard anything less than full security as not good enough for iOS apps.
Developers have the new option of multiple startup discs with different security modes, so the solution for a developer is to have a "dirty" startup disc for testing and a "secure" disc for other work. Which is sensible.
Yep. I was talking with the dev and he's waiting for his M1 machine to arrive, but based on the tests I've done it doesn't look good.
I mean... iOS apps are to some a bonus that they can do without, so it really is a YMMV thing.
I'm pretty sure everyone called the Commodore VIC-20 my parents and siblings bought 10-year-old me back in 1980 a Personal Computer. Can we maybe stay on topic please?
Feel free to start another thread called "Is a Mac a PC" if you want to discuss this (although there are probably already 500 such threads).
Also big thanks to my family for starting me on my career at an early age. It was a lot of money for them back then; and that purchase changed my life dramatically.
Now back to discussing SIP, ok?
Feel free to start another thread called "Is a Mac a PC" if you want to discuss this (although there are probably already 500 such threads).
Also big thanks to my family for starting me on my career at an early age. It was a lot of money for them back then; and that purchase changed my life dramatically.
Now back to discussing SIP, ok?
I can confirm that trying to run iOS apps with SIP disables results in failure. A silent failure. With this error in the console:
At least macOS could show an error message trying to launch the iOS app.
Nov 22 20:30:35 <private> com.apple.xpc.launchd[1] (application.com.innersloth.amongus[6550]): FairPlay decryption failed on binary.At least macOS could show an error message trying to launch the iOS app.
But does csrutil enable also re-allow iOS apps to work again? Or do they stay broken?
Great! From what I’ve been able to see from some other posts on this, it was implied that enabling sip again still didn’t get iOS apps working again. But wasn’t clear. This is good to know.
Wait, so, if the problem is FairPlay...
Do iTunes movies work when SIP is off on these new Macs? Can you stream Netflix in 4K?