This isn’t sustainable.<p>Software developers can’t build on a foundation that is constantly, capriciously shifting. This on top of the App Store's already-onerous restrictions and the fact that it’s the only practical way to get your software on one of the world's largest computing platforms has already engendered a deep antipathy [1] among Apple developers, and there are no signs it’s getting better. Something has to give.<p>1. <a href="https://news.ycombinator.com/item?id=23580762" rel="nofollow">https://news.ycombinator.com/item?id=23580762</a>
Hi, Saagar from the iSH team here. We received a call from someone who runs App Review at Apple earlier this evening. They apologized for our review experience, telling us that they've accepted our appeal and that they will not be removing iSH from sale tomorrow. We'll work out the details with them in the coming days.<p>A huge thanks to all of you for your support of iSH!
Apple clearly does not want you to have a general-purpose computer:<p><a href="https://boingboing.net/2012/01/10/lockdown.html" rel="nofollow">https://boingboing.net/2012/01/10/lockdown.html</a><p>Everything is done with "security" as an excuse because it's hard to argue against[1], but I think people are slowly starting to see through that. Apple wants to control every aspect of your life, and if you let it, it will. I wonder whether those who work at Apple and are responsible for doing such things really understand the implications, and whether they agree with it...<p>[1] Except with that classic Franklin quote.
As beautiful and polished as iOS is it is policies like these that keep me on Android.<p>I wish iSH the best of luck, but I will stick with Termux (<a href="https://termux.com/" rel="nofollow">https://termux.com/</a>) on Android for now.
These are linked in the post, but I'm pulling them out as a top-level comment so you can focus your discussion on those.<p>Theodore on how the App Review process could be improved: <a href="https://tbodt.com/2020/11/08/app-review-experiences.html" rel="nofollow">https://tbodt.com/2020/11/08/app-review-experiences.html</a><p>Ramblings I wrote on why I believe the guideline iSH was pulled under was incorrectly applied and needs to be rewritten: <a href="https://saagarjha.com/blog/2020/11/08/fixing-section-2-5-2/" rel="nofollow">https://saagarjha.com/blog/2020/11/08/fixing-section-2-5-2/</a><p>Related, a-Shell got a similar notice: <a href="https://twitter.com/a_shell_ios/status/1325526061099196416" rel="nofollow">https://twitter.com/a_shell_ios/status/1325526061099196416</a>
Yet another example of apple's ongoing control freakery. I wonder how many incidents will be required before those who rush to defend them every time get it?<p>Apple tolerate app store developers as a necessary evil. If they could develop all of their own apps they would.<p>As with suppliers, as with stores, as with everything they would gladly prefer to do it all themselves and give zero access or share the slightest collaboration with anybody.<p>They are utterly ruthless in this regard and will continue to be for as long as they exist. This includes doing bad and nasty things as well as those the apologists can more readily rationalise.<p>I am a little surprised anybody takes risks in this arena. Of course for $$$ apps that trivially fulfil apple's arbitrary rules (for now) the potential payout justifies it but for free/open source apps why risk the pain?<p>For a company that happily generates colossal margins by using the effectively slave labour of a totalitarian state which puts people in concentration camps and disappears political opponents them being unethical/inconsistent in the app store seems very unsurprising. Even in western countries they happily bankrupt suppliers after poaching all their staff. Yet there appears to be shock when they do things considerably less evil... Strange to me.
> Soon after we released iSH without apk, we found users who had figured out a way to get apk back using wget and were posting about this throughout the internet. We suspect this was the reason why our rejection notice mentioned wget specifically<p>As the writer of one of the links in that sentence, I almost feel bad for making the post I did. Almost. If I hadn't someone else would have, clearly. I'm not some super hacker that discovered a hidden backdoor here.<p>It's frustrating, to say the least, that Apple won't let me do what I want with hardware I own. Yep, I know it's a long standing issue, and I'm not the first one to have this gripe, but this sort of nonsense is why I'm moving away from the Apple ecosystem. Once you piss off your power users, I wonder if the ecosystem will survive for long.<p>Then again, maybe I'm just having a "get off my lawn" moment, and Apple is on the right path. I'm not clairvoyant, I just want to have a nice Mosh client that can run a Python script to find an IP and open a firewall hole. But nope, that's evil scripting, I guess.
This is one thing that I hate the most about IOS. I like the polished look and the usability. To be completely honest, I don't need to have a shell running on my phone. I'm not going to write a shell script to automate anything on the tiny screen of my iPhone 8. iSh is an emulator anyway! But, like many other curious users, I don't want to lose the ability to do it. Especially when the hardware is a lot more capable that what the OS supports. I understand that Apple does it for "security" purposes!! They should at least enable this on iPad OS. May be warn the users about the "perils" of "foreign code'! I've been using iSH since the TestFlight days. I played around and downloaded packages. Even downloaded Perl! Now that's gone. I can sideload it using Xcode, but not everyone has a Mac to do it.
>The nature of iSH meant that this problem was fundamental, as users can always add back functionality that we remove.<p>That's the point, isn't it? When I had an iphone, I always understood that there are no local terminal apps because apple banned them. They shifted the rules slightly since then to make it easier to make apps for teaching programming, but the goal was never to make generic dev environments. When I heard about this app, I assumed there had been a fairly fundamental change in the sorts of apps apple allowed. It seems like no such change occurred - apple just didn't notice what the app was doing until after it was released.<p>Good on the iSH people for giving it a shot. I doubt they'll break through the apple wall, but there's always a chance.
Don’t build software for Apple devices. It’s a pretty straightforward solution.<p>Apple has shown time and again that they’ll crush your project/business in an instant without recourse or a second thought.<p>Nothing on the App Store, regardless of whether it complies with Apple’s policies currently or not, has any guarantee it won’t be disappeared tomorrow for non-compliance when the wind blows in a different direction (like any number of parental control apps prior to Screen Time).
This year I build qoob, an app to interact with an IOT electric scooter parking. In August I had the MVP ready, we build 2 prototypes and could save and charge scooters of all voltages in office halls.<p>The project is not my main job, so time is precious.<p>I was asked to create a new functionality: Allow companies to buy and borrow e-scooters between company employees.<p>But what happened is that I had to implement Apple Login, since FB and Google did work already.<p>Who should I take care off? Apple or the customer/users?
Is it optimal to prioritize the Apple Login, that nobody requested?<p>I don't care about monopoly persse, I'm concerned because it doesn't let me be user-centric, consumer-centric.<p>(and I can't leave apple, because I can't leave my users)
There are at least two reasons that Apple tries to prevent tools like iSH. In order of what I suspect is their motivation:<p>1. Users can be foolish or even tricked into installing apps and entering commands. If iSH provided a possible attack vector, these kinds of users would get bitten (and they would complain about weak Apple security). As Apple really does seem to be making a strong effort on security (and privacy, it appears?), losing a few useful apps and a few users is worth the trade.<p>2. This is a bit more of a stretch, but for various reasons Apple wants to control the macos/ios development process. Whether it's to force developers to own Mac computers (when xcode could probably run quite well on iPad Pro...), or to perhaps guarantee a more consistent outcome (which ultimately should affect the users in a positive way, or at least a less negative way), Apple wants to control the process.
I will say it again. The one thing Apple will try to defend is the concept of an app/container. I wrote a similar comment supporting their actions with video game streaming platforms the other day[1]. Any app that creates some kind of a wedge into another kind of app/container ecosystem is not going to fly. I do believe this will get solved by having a store within a store model. It just means all the packages/apps that are run from within the other platform will need to have some kind of listing/metadata shared and controllable in some fashion by Apple. The interesting thing will be the relationship with devs. Does Apple need to have a direct one or not?<p>1. <a href="https://news.ycombinator.com/item?id=25022746" rel="nofollow">https://news.ycombinator.com/item?id=25022746</a>
"we received a call from Apple"<p>is this a literal statement where some human from Apple called on the telephone to speak to someone about this situation, or is this a phrase that actually means they received an email notification about the situation? I ask because it seems well outside the norm of no-human contact regarding support from FAANG companies.
Cant imagine how Apple would let this through in the first place but makes sense they would pull it.<p>I grabbed a copy after reading this and very nice work by the developers but easy to see how an app that lets me install other apps on ios would be banned.
To me it appears they admit that iSH allows scripting (ummm, obviously), and that scripting is against Apple’s policy (as we all know). From one of their articles: “Soon after we released iSH without apk, we found users who had figured out a way to get apk back using wget and were posting about this throughout the internet”.<p>They argue that Apple’s policy should be changed to allow scripting: <a href="https://saagarjha.com/blog/2020/11/08/fixing-section-2-5-2/" rel="nofollow">https://saagarjha.com/blog/2020/11/08/fixing-section-2-5-2/</a><p>It looks to me that Apple’s main reason for not allowing scripting is to prevent an app from deploying other apps within itself (preventing any competition with the app store), with a secondary reason being security for users (harder to argue against).<p>I can’t see Apple ever allowing a shell app into the store, as that would turn your iDevice into a general purpose computer.
Apple is walking a fine line here.<p>I understand on one hand Apple wants to prevent Epic from installing their own competing app store on iOS, and they also probably don't want to be sued by Nintendo for hosting emulators (even if emulators are probably legal.) It's pretty obvious that a) it's Apple's walled garden so they can mostly do what they want, b) the vast majority of iOS apps are games and c) other game platforms are similarly restrictive.<p>On the other hand, Apple probably doesn't want to kill Scriptable or Pythonista (and I don't want them to either.) One of the nicest features of iOS (and macOS) is that you can use scripting apps and languages to construct workflows that use multiple apps, access the internet, etc.. Scriptable and Pythonista are also useful as personal programming and learning platforms.<p>Good luck I guess.
Update from tbodt on the iSH Discord:<p><i>@everyone We got a call this evening from someone who runs App Review. They apologized for the experience we had, then told us they've accepted our appeal and won't be removing iSH from the store tomorrow. We'll stay in contact with them to work out details. Thanks everyone for your support!</i>
I've been following iSH for a while and was very happy when it finally came out of beta. iOS needs a good shell and iSH seemed perfect. I actually thought this will fit into apple's strategy of marketing ipad as a replacement for Laptop
iSH is awesome. I've been using the beta for about a year (or more) and have provided some feedback to Theodore a few times. This eventuality was almost certain because of the App Store restrictions that have been in place since before the iSH project was launched. In this way, Apple sucks. They have complete control over what an app can and cannot do. There is no alternative (besides jailbreaking) to the Apple App Store for iOS apps. This is part of the deal that you should know about when you buy an iOS product.
> Advanced users are welcome to build iSH themselves—it’s free and open source and always will be!<p>I mean, the app store fiasco sucks, but at the same time if you're advanced enough to want a command line on an iDevice you're probably advanced enough to do 'git clone', hit the build button in XCode, and do a local install. It's grade school level of difficulty.<p>Ideally they'd offer a release that you can build and install locally that's full featured and is wholly unfettered by concerns about app store policies.
Is Apple really expecting developers to port their tools to the arm macs with their iOS policies (that I’m sure they are salivating to establish for macOS).<p>Good luck to them and their iOS developer minions.
> Precompiled builds of iSH (distributed as IPA files) will remain available [...] for jailbroken users.<p>Is there any reason to use iSH over the native system shell when jailbroken?
I’ve been all in on Apple for about 15 years, but have been slowly moving away as it gets harder to use their products for development and power usage.<p>Got a windows laptop recently, and the developer experience is much better than Mac OS which surprised me. Thinking about getting a surface pro to replace my iPad for traveling.<p>Edit: the only thing that keeps me on the iPhone right now is that their hardware (chips in particular) are so much better.
There is no point fighting Apple. Companies spend resources on Apple moving goal posts and focus on artificial problems. Once companies stop supporting Apple products, users will switch to better platforms or Apple will change their ways. I made sure everyone I know is informed about Apple shady practices and knows to avoid their products.
#unpopularopinion: If someone wants an Android experience they should buy an Android phone where iSH functionality is basically built it. iSH is cool, but they were skirting the rules and everyone knows it. This isn’t shocking, and there were bound to be hiccups on the fringes of the rules like this.<p>If you want a phone for just getting the normal stuff done in a curated world, then pick iOS as that’s what they are trying to do. If you want a phone/device that is wide open to play with, extend, and hack on in a basically open manner, then pick Android as that’s what they are trying to do.<p>What seems like a waste of time is to pick one side and then complain about it not being enough like the other side. Pick your flavor, the world offers both. And then quit whining if the other side is more successful by some metric... Make your chosen side better or switch.
I don't understand how this was permitted in the first place. Everything about this is against the app store guidelines. Unfortunately I don't see how you can have this be compliant at all.
> Consistent enforcement of Apple’s incorrect interpretation would require the removal of all scripting apps, including many of the most popular applications in the App Store and some of Apple’s own applications.<p>The problem with "consistent enforcement" is<p>1) the guidelines are purposefully vague<p>2) there are reports of unwritten internal rules that are different from the public rules<p>3) I suspect that the amount of revenue that a company brings through their app also affects how rules are applied<p>But, it's their platform and they can do whatever the hell the way with no (legal) consequences at all.
Any applications that is (by accident <a href="http://beza1e1.tuxen.de/articles/accidentally_turing_complete.html" rel="nofollow">http://beza1e1.tuxen.de/articles/accidentally_turing_complet...</a> ) turing complete is not allowed on AppStore?
Call me crazy, but I'll bet this has something to do with youtube-dl and the RIAA DMCA takedown. Apple probably got wind that you could install youtube-dl on iSH and "infringe" on copyright.
Apple won't allow you to run youtube-dl on your iOS device. Section 2.5.2 is just the excuse. If 2.5.2 didn't cover it, they'd make up another rule to do so.<p>Apple isn't going to let people sidestep copyright on iOS. It doesn't matter whether youtube-dl or curl or wget have legitimate uses. If they can be used to sidestep copyright, Apple will ban them.<p>I'm an Apple user. This pisses me off too.
<i>Google lets banks remotely disable phones</i> [0]: 114 points in 11 hours<p><i>Google lets apps prevent users from taking screenshots</i> [1]: 315 points in 14 hours<p>Devs on HN shrug it off when an app screws over users, but they take to pitchforks when an app is removed.<p>There's also a heavy bias in favor of Google and against Apple on HN, but Apple does nothing nearly as hostile to <i>users</i>, and so millions of people will continue to happily give their money to Apple.<p>Only user-hostile developers fail to understand this and clamor for Apple's restrictions to be weakened so they can prey more freely upon users.<p>[0] <a href="https://news.ycombinator.com/item?id=25026050" rel="nofollow">https://news.ycombinator.com/item?id=25026050</a><p>[1] <a href="https://news.ycombinator.com/item?id=25025066" rel="nofollow">https://news.ycombinator.com/item?id=25025066</a>
The practice of rigging app store removals as a means of increasing launch-hype is becoming an increasingly utilized marketing technique for apps. The "Hey" e-mail app successfully used this tactic recently. This marketing technique is a form of social engineering and fraud that spurs artificial discourse regarding well-known legal hurdles affecting apps. App developers then re-publish a compliant app that capitalizes on the very marketplace that the app developer and their pool of new users claim some deep-seated issue with. The old switcheroo!