Live data from Hacker News

iPhone 11 Emulated on QEMU

github.com

111–120 of 152 posts

Re: iPhone 11 Emulated on QEMU

#111
post #44

Earlier quoted context omitted.

If you don't daily drive an iPhone and you don't want to buy into Apples ecosystem, why do you want to develop for their ecosystem (which of course requires $100 a year to do so)? Genuinely curious cause I see a lot of people with this sentiment, is it for work related purposes or something? Or testing of web work potentially?

For myself, it’s mostly web stuff with Safari and Safari on iOS that I’d really like to be able to test from time to time.

There's a ton of companies out there who have real iPhones, iPads etc you can rent by the minute through a web browser to test your code or web sites.

i.e.

https://www.browserstack.com/test-on-iphone

I'm just trying to find the one I use to test my emoji stuff, since Safari is the only one that displays emoji domains correctly.

Re: iPhone 11 Emulated on QEMU

#112
post #95
post #87

Earlier quoted context omitted.

Ability to install a free software distribution, side-load software, run a plethora of Linux apps through Termux, fix the screen if you happen to break it without the thing complaining about "non-genuine parts", build, run and distribute software for the device without needing to pay a third party for the privilege of doing so, hook the thing up to a keyboard and display to use it for real work, install a full firewa…

I’ve yet to see anyone distributing music only in Ogg Vorbis save for some backdoored Spotify thing.

Anyone who does will have Apple users complaining in no time.

Re: iPhone 11 Emulated on QEMU

#113

Earlier quoted context omitted.

Easy; it's the hacker. Whether the false information is publicly available is not a defense to fraud. Fraud is presenting false information (public or not) as true (in this case, that the serial number of the item belongs to you as a bona fide purchaser) and an innocent party (Apple + the consumer) relying on it to their detriment.

A serial number is not a password, it's a username, and copying it down isn't hacking.

Copying it down isn't the problem. Falsely claiming that it is associated with a machine that belongs to you is.

Re: iPhone 11 Emulated on QEMU

#114
post #75
post #20

Earlier quoted context omitted.

It's an interesting thought experiment though. Who is harming the purchasers? Apple, or the hacker copying down a publicly available piece of information?

I vote that serial number information would hands-down not be considered a "publicly available piece of information" in court. Serial numbers are generally used to corroborate ownership of an item in legal scenarios (and may count as a conditional representation of PII). Apple uses them as unique identifiers to authenticate their devices and tell them apart, and very presumably protect against various forms of fraud.…

The public-information question isn't even an issue that a court would consider in a fraud allegation. (We're not talking about theft of trade secrets here.) It's a red herring and isn't worth the effort to discuss.

Re: iPhone 11 Emulated on QEMU

#116

Earlier quoted context omitted.

Easy; it's the hacker. Whether the false information is publicly available is not a defense to fraud. Fraud is presenting false information (public or not) as true (in this case, that the serial number of the item belongs to you as a bona fide purchaser) and an innocent party (Apple + the consumer) relying on it to their detriment.

A serial number is not a password, it's a username, and copying it down isn't hacking.

[deleted]

Re: iPhone 11 Emulated on QEMU

#117
post #73

Earlier quoted context omitted.

So the question is why would I as a consumer want to buy a least common denominator app using a cross platform framework that wasn’t actually tested on real hardware?

You can always uninstall it if it's crap right? It would be available to you as a choice, and now it's simply not available.

You're showing your cards as an android person ;-)

I agree with you, but nearly everyone on apple products will not. I get a (too me very perplexing) very similar respose when I ask things like, "why would it hurt people who want an Apple curated app store experience to allow a buried setting in the settings menu that allows sideloading for the few people who want that?"

Re: iPhone 11 Emulated on QEMU

#118

Earlier quoted context omitted.

You can semi not buy into the apple ecosystem at the moment. Purchase a 2nd hand iphone and then run this Docker based OSX system: https://github.com/sickcodes/Docker-OSX It's fine for personal projects using something like usbfluxd to talk to your iphone from the docker container. I wouldn't rely on it to do commercial work.

The cheapest second hand iPhones that run the current version of iOS (but are right at the tail of any support) are on the high side of the price range of what I’ve ever spent on a new, primary phone that I expect to last me at least several years. (And although it’s not as common as the alternative, I’m hardly alone in not spending much on phones; now laptops, on the other hand—.) I don’t want to spend more on a dev…

i bought an iphone 6s for this purpose for 50€. upon mentioning this to somebody i was also given a second one with a crap battery for free

Re: iPhone 11 Emulated on QEMU

#119

For those that don’t know about it, you can find a fairly complete commercial iPhone emulator at Corellium: https://www.corellium.com/ It does essentially everything, short of hardware accelerated rendering You can even emulate it being attached directly to your Mac and use it as a cloud device from Xcode

This is a great service. I recently had to test a specific bug on iOS 11. Instead of figuring out how to download the simulator, or buy an old device, I simply created a virtual device, connected to the VPN, and built straight to the device from xcode. Like magic.

It's slow and missing some features but it's still amazing.

Re: iPhone 11 Emulated on QEMU

#120

Earlier quoted context omitted.

A serial number is not a password, it's a username, and copying it down isn't hacking.

Copying it down isn't the problem. Falsely claiming that it is associated with a machine that belongs to you is.

Tying an app to hardware identifiers (effectively dongle-based DRM) is the problem.
Post reply on HN