CastCatcher Internet Radio cannot be posted to the App Store because it is transferring excessive volumes of data over the cellular network, which as outlined in the iPhone SDK Agreement section 3.3.15, is prohibited
Right. Except for the fact that every other radio app works over cell network as well AND Apple has approved THREE prior releases of CastCatcher. We’ve emailed them and are hoping to resolve this quickly. CastCatcher does not burden cell networks any more than any other radio application. Ridiculous.
EDIT: We resubmitted and Apple approved CastCatcher and it’s been on the store some time. Thanks Apple!
Is there any way users can complain/request to Apple? I use this app over my own wifi network with an iPod touch.
I’m not really sure — Maybe check if there’s an iTunes support email address?
For over a year, my dream has been to get an iPhone. But all this Apple rejecting apps non-sense is just making me and others change their mind about getting an iPhone.
I may just get an Android phone, which allows owners the freedom to decide what applications to run.
It’s a waste of a great product, which it’s being limited by Apple’s non-sense and AT&T’s greed. Even if this application takes 192kbps, how can you really call that excessive bandwidth???
You people are fool of *&^%$#@! Keep your iPhone, I don’t want it anymore!
I feel your pain man, were there any changes that might have provoked this? Did you add more high bitrate streams or anything?
Not at all. I changed the default streams, mainly because the old ones all appeared to be dead but their bit rates were all the same as the old ones (128kbps). Those streams are really just examples, though, as people use CastCatcher to listen to their favorite stations (well, that’s the intent, anyway).
OH NO!!!!
grrr wtf apple, might as well close pandora, and I heart radio too….
sounds like the big apps are throwing their money around at apple to shut out the competition….
there is a way to get “app store” suppiort through itunes…. but I’m at work and dont have intunes installed….
r7, why not limit streams to 128k? I’m sure you’ve already thrown that out to apple…idk…i miss my castcatcher…
@justin: I doubt that’s the case (big apps comment).
I thought about limiting streams to 128k while on the cell network. I was concerned about it limiting our users’ options, although 128k is probably the most you’d want to try and stream, even over 3G.
yea, I don’t know, it seems fishy….
I tried once to stream a 212k stream over 3g…no way thats happening until att gets better 3g service..
but it’s sweet to have the option, considering the iphone wifi capabilities.
digg it you guys!
http://digg.com/apple/Apple_Rejects_Radio_App_Update_Due_to
wow…R7 made giz!
http://gizmodo.com/5082341/apple-rejects-castcatcher-13-app-for-transferring-excessive-volumes-of-data
Yet another reason to jailbreak your iPhone!
Just heard about this app today and am pissed I can’t try it out now. I stream 128k audio on my iPhone all day with apps purchased from the app store. What’s the deal with this app then? Seems fishy.
Actually Apple has been kind enough to leave version 1.2 up. They did not boot it from the App Store.
You can still try radio which has similar list of stations and is still active at the iphone store.
Or just get get CastCatcher 1.2 from the App Store..haha. I’m confident Apple will help us by allowing 1.3 onto the store. We would much appreciate not advertising for others in the future, though.
on the one hand, I’m all for the whole “screw apple they suck attitude” but here’s the thing. the bandwidth rule was in the SDK. maybe it needs some clarity sure, but it is there. so anyone that might brush that rule should be asking them to define excessive.
and then work around it. seriously. anyone that has or has worked with an iphone knows that ATT is feeling some bite cause they didn’t expect so many folks to come out to buy Iphone V2. it showed them that their great network ain’t so great after all. not when you dump in a few thousand more users who all have to pay for data so they might as well use it.
app developers need to be savvy about this. they can’t just blame Apple and ATT over the issue. Put a cap on the streams that can go 3g and anything above that is either no go or wifi only. otherwise, don’t be shocked when you are rejected. and I bet there’s something in the rules that says that Apple can reject an app at any time including when an update causes the app to violate the rules. so all this complaining about how they won’t allow this update is a tad bogus. at least castcatcher got to keep the most current valid update in the store. some apps got totally trashed.
Lucas, No one wants to screw Apple — their product is good and they give us a simple means to sell our own. Clarity on policy is needed, I agree.
Gizmodo had a blog post a while back stating that AT&T wasn’t hit nearly as hard as expected so I don’t buy that, assuming their information is correct of course.
The issue (for us) wasn’t policy, but the inconsistency of the decision. Apple has since rescinded that and approved both versions 1.3 and 1.4.1. No changes to streaming code, just some fixes around playlist downloads. We’re thankful to them for that. There is merit in limiting bit rates of streams over 3G so as not to kill the network but AT&T most likely already handles that w/ traffic shaping on their end.
Not that I’m impressed a lot, but this is more than I expected when I stumpled upon a link on Delicious telling that the info is awesome. Thanks.