Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Apple starts rejecting apps with “hot code push” features

forums.developer.apple.com

Post reply on HN
Print view View original

21–30 of 498 posts

Re: Apple starts rejecting apps with “hot code push” features

#21

Post by eridius »

simplehuman wrote: post #13

From https://rollout.io/how-it-works/ : Does Rollout comply to Apple’s Guidelines? Yes. As per Apple’s official guidelines, Rollout.io does NOT alter binaries. ... With over 50 million devices already running our SDK, it is safe to say that Rollout complies with with Apple’s development and App Store guidelines. Ouch. Just like the company's future is in danger.

The first time I saw Rollout I was shocked it wasn't already banned by the App Store. No matter what they say, I can't imagine how they could do what they claim to do without flagrantly violating the guidelines.

Re: Apple starts rejecting apps with “hot code push” features

#22

Post by cynix »

simplehuman wrote: post #13

From https://rollout.io/how-it-works/ : Does Rollout comply to Apple’s Guidelines? Yes. As per Apple’s official guidelines, Rollout.io does NOT alter binaries. ... With over 50 million devices already running our SDK, it is safe to say that Rollout complies with with Apple’s development and App Store guidelines. Ouch. Just like the company's future is in danger.

> Rollout lets you push code-level changes to native iOS apps, without waiting on the App Store.

What did they expect when their entire business model is based on something that's literally the opposite of what the review guideline allows?

Re: Apple starts rejecting apps with “hot code push” features

#23

Post by empthought »

akhilcacharya wrote: post #7

There's a cynical part of me that thinks this is because Apple is going to announce a similar feature at WWDC

I think that's likely. Why is it a cynical part of you? Either Apple is proactive and aggressive about keeping their platform free of hackishness as a matter of routine, or their store ends up a pile of malware and crashy junk.

Re: Apple starts rejecting apps with “hot code push” features

#24

Post by obstinate »

mmmBacon wrote: post #10

Seems like people have been aware of concerns about violating the TOS with these hot patch frameworks. From April 2016 >>Rollout is aware of the concerns within the community that patching apps outside of the App Store could be a violation of Apple’s review guidelines and practices. Rollout notes both on their FAQ site and in a longer blog post that their process is in compliance. https://www.fireeye.com/blog/threat-…

A ton of games do this and it is incredibly annoying. I don't want to download an update, then have to download an update. I only wish the same restriction applied to my Android device.

Re: Apple starts rejecting apps with “hot code push” features

#26

Post by empthought »

eridius wrote: post #21
simplehuman wrote: post #13

From https://rollout.io/how-it-works/ : Does Rollout comply to Apple’s Guidelines? Yes. As per Apple’s official guidelines, Rollout.io does NOT alter binaries. ... With over 50 million devices already running our SDK, it is safe to say that Rollout complies with with Apple’s development and App Store guidelines. Ouch. Just like the company's future is in danger.

The first time I saw Rollout I was shocked it wasn't already banned by the App Store. No matter what they say, I can't imagine how they could do what they claim to do without flagrantly violating the guidelines.

It only started to matter when dumbasses started thinking that using Javascript everywhere was A-OK.

Re: Apple starts rejecting apps with “hot code push” features

#27

Post by Retra »

rocky1138 wrote: post #2

The solution is fairly simple: just stop releasing software on that platform. There are millions of customers on more open platforms, so there's really no need to support them anyway.

All of life's problems are simple when suicide is your backup plan.

Re: Apple starts rejecting apps with “hot code push” features

#28

Post by empthought »

LeoPanthera wrote: post #20
RKearney wrote: post #6

I wonder if Apple will apply this rule to everyone, which would be fair, or if they plan on letting big name developers like Facebook or Google continue to violate the rules without consequence.

They should pull the Facebook app for this. But I'll eat my hat if they do.

Their guidelines specifically say that, with prior authorization, the prohibitions do not apply.

Re: Apple starts rejecting apps with “hot code push” features

#29

Post by htormey »

avolcano wrote: post #11
htormey wrote: post #4

I wonder if this is going to hit non native code push solutions like React Native? Or if Apple are going to start cracking down on apps like Facebook, Twitter or Pinterest that do a lot of A/B testing.

This was my immediate question too. Microsoft offers a service called CodePush ( https://microsoft.github.io/code-push/ ) for React Native and Cordova apps that presumedly could get caught by this. I don't have enough mobile dev knowledge to know whether or not it uses the same APIs that were mentioned in Apple's rejection letter, though.

Yep. I use code push in several apps. It's gonna be fun times next time I need to submit an app. I think it might be safe because it doesn't push native code and rollout is all about pushing native changes.

Re: Apple starts rejecting apps with “hot code push” features

#30

Post by kyrra »

RKearney wrote: post #6

I wonder if Apple will apply this rule to everyone, which would be fair, or if they plan on letting big name developers like Facebook or Google continue to violate the rules without consequence.

Are there any sites that document Facebook or Google using hot code push on iOS?
Post reply on HN