4 ms·

Having had an application approved and then later rejected for use of private APIs (WiFinder), this really pisses me off. Inconsistency sucks, as I told the App

Having had an application approved and then later rejected for use of private APIs (WiFinder), this really pisses me off. Inconsistency sucks, as I told the AppStore reviewer I talked to on the phone. I'm fine with either nobody or everybody being able to use private APIs. But maybe I'm just not hipster enough - I'm certainly not a "life-long user of all Apple products."

credo 17y ago
yes, a consistent policy will help. At the very least, I hope Apple makes this particular api public. More importantly, I wish Apple improved their overall review process and transparency (e.g. with a queue number for app store reviews) and clear rules on what will be approved, what will be rejected etc.
potatolicious 17y ago
This triumph of the developer over Evil Apple would be a lot more compelling if the app can get past the splash screen without crashing.
- weaksauce 17y ago
  It does that to me too. My guess is that the app is trying to connect to their(knocking vid's) "master" server to setup a session and the app was not coded to gracefully handle the situation of getting arstechnica'd and it is unable to respond to the requests in a timely fashion and some killswitch gets triggered. Now they have to wait another 2 weeks and (maybe) another email to steve to fix it or wait until the equilibrium point is met where there are enough dissatisfied people quitting that will allow the other people on. Or they just programmed it too bloated and it chewed through too much memory in the outset and the iPhone killed the process. Who knows.
  - dangrover 17y ago
    Every iPhone developer has to deal with emails and reviews of this exact nature. The Apple apps/background processes eat tons of memory up over time and the phone can get in a state where it has an absurdly small amount left to run apps. Restarting fixes this. Try restarting your phone, and if that doesn't fix it, then yeah, the app sucks.
    - ryanpetrich 17y ago
      You can also kill Safari, Mail and Phone by activating the app, holding Power until the shutdown screen shows, then holding home until the app quits.

credo 17y ago

yes, a consistent policy will help. At the very least, I hope Apple makes this particular api public. More importantly, I wish Apple improved their overall review process and transparency (e.g. with a queue number for app store reviews) and clear rules on what will be approved, what will be rejected etc.

potatolicious 17y ago

This triumph of the developer over Evil Apple would be a lot more compelling if the app can get past the splash screen without crashing.

weaksauce 17y ago
It does that to me too. My guess is that the app is trying to connect to their(knocking vid's) "master" server to setup a session and the app was not coded to gracefully handle the situation of getting arstechnica'd and it is unable to respond to the requests in a timely fashion and some killswitch gets triggered. Now they have to wait another 2 weeks and (maybe) another email to steve to fix it or wait until the equilibrium point is met where there are enough dissatisfied people quitting that will allow the other people on. Or they just programmed it too bloated and it chewed through too much memory in the outset and the iPhone killed the process. Who knows.
- dangrover 17y ago
  Every iPhone developer has to deal with emails and reviews of this exact nature. The Apple apps/background processes eat tons of memory up over time and the phone can get in a state where it has an absurdly small amount left to run apps. Restarting fixes this. Try restarting your phone, and if that doesn't fix it, then yeah, the app sucks.
  - ryanpetrich 17y ago
    You can also kill Safari, Mail and Phone by activating the app, holding Power until the shutdown screen shows, then holding home until the app quits.