Hacker News Reader

Comment by cyberge99 | Hacker News Reader

Big Sur already supports iPad apps on M1 natively, out of the box.

You just download the iPad version from the App store and it runs automagically.

I even did a blog post about it: https://chrisbergeron.com/2021/06/16/Pushover-Desktop-Yes-on...

Didn’t apple enable a block against installing IPAs that the developer didn’t authorise to run on macs? https://appleinsider.com/articles/21/02/09/apple-again-bars-...

I think Apple has adopted a denylist instead of permitlist approach. They let all iPad and iPhone apps run unless the developer puts their app on the denylist.

No, its a whitelist. There are plenty of abandoned apps that haven't been updated in years, which I would like to run on M1, but aren't available.

Isn't that because the apps haven't been recompiled for ARM64 though?

No iPad has ever run intel, and Apple went 64 bit over half a decade ago.

Yes in 2014 they made the move. The first iPad is from 2010. So we have 4 years worth of old arm compiled apps. I don‘t understand the intel part though.

It’s a whitelist, but it’s opt-out. You have to specifically check “do not let this app run on Mac” in the App Store Connect portal.

Guys, an opt-out whitelist is per definition a blacklist.

I.e what is done explicitly defines the color. Explicit Allow (blacklist opt out) -> whitelist Explicit Deny (whitelist opt out) -> blacklist

Except that old apps that aren’t updated, are not put on the whitelist. (This is what I understand from the comments above.)

> It’s a whitelist, but it’s opt-out.

That's a blacklist.

If it's a whitelist or a blacklist is really just an implementation detail.

The key here is that the developer can choose to opt-in/out when uploading to the mac store (defaulting to opt-in), however older apps will be opt-out by default (as the developer didn't have this choice when they uploaded).

What applies to this conversation, however, is the correct use of terms and to not use the opposite, incorrect term.

Well if you want to get technical on terms, it’s probably not implemented as either a whitelist or a blacklist and is probably just a database field which was defaulted to false during the migration.

And because it’s likely implemented like that, you can either generate a whitelist or blacklist if you want, but in reality it’s highly unlikely it’s implemented as either of these things.

But regardless it seems like this whole thread is just about semantics anyway.

Since you have root couldn't you just patch the runtime to whitelist the app you want to run?

It does a server-side check.

At least one app I've tried (Logic Wiz sudoku) failed to get past the loading screen. Any insight? Not sure if it's an api that isn't implemented or a data storage issue?

Do you know how does in app purchase work in that configuration ?

Doing it the way you describe requires an Apple ID, which requires a phone number and email address, and also transmits your unchangeable hardware serial number (a supercookie) to Apple when you launch the App Store.

I believe it also requires that system integrity protection not be disabled, so any other Apple spyware in macOS (eg serial-linked APNS phone-home) cannot be disabled.

Reply on news.ycombinator.com