I've been waiting on an iPhone app to go through the app store approval process. It's been in the queue for about two weeks now.
Apple recently added something to the dev center about reachability, pointing developers to their sample app. In my app, I'm posting to a URL on my server using HTTP - but I'm not doing a reachability check first. If the user tries to submit the request, it will eventually time out and they will see an error.
What are the chances that Apple will fail this app? I'm wondering if I should just quickly implement reachability and "reject binary" myself, submitting a new version. Might save me a couple of days if I'm just going to get rejected anyway.
Implement reachability, if your app uses the web and when there is no connectivity the app doesnt say something along the lines that "this is not working because you have no internet access" then 95 percent it will be rejected by apple
Sounds like you answered your own question to me - not handling that case is a serious UX problem you should definitely fix.
If I were expecting to deal with a reasonable, smart approval process, I would do exactly that -- fix the app to match their new documents. It's a classy move, implying you'd be a good citizen.
You may want to rely on someone who's been through the iPhone app store, though, for an answer with the right amount of cynicism.
Related
I need to create and App that will run in the background and will monitor the user's behavior in term of applications installed, opened and deleted.
i.e Application will save the information in the database that at what time user has installed/opened/deleted an application in iphone.
I wonder if its possible and Apple will allow this??
I tried to google on it but did not get anything, i know if its possible then it would be possible by multiasking only??
Can any one please help me on the same.
Brn
Not possible. Your app can only run when the user chooses to (except for a limited sub-set of tasks like VoIP, etc).
Your app can know nothing about other apps.
iOS apps are sandboxed. I wouldn't say impossible but certainly not allowed. You'd have to find a security hole to give you root access first. Oh, and notify us when you do ;).
Edit:
Maybe it wasn't clear in my post but I was at least half joking. Not sure why you want to do what you want to do. I can imagine the following scenarios:
1) Your company wants to monitor everything their users do on their phones. In that case I would either
a) lock them down and only allow app installation through a company portal (enterprise distribution is possible in iOS) OR
b) forget about iOS alltogether. Blackberry would probably be closer to what you want, although I don't really have experience with that platform. Also, its future is not sure.
2) You're trying to do something illegitimate. Because of iOS's locked down nature it won't be easy. See how few successful attacks there have been in the last years - and that's for a highly successful platform where an attack could be high paying both in terms of money and reputation.
I have read many post indicating that we can't send sms on Missed Call, but i would like to know the reason behind that.
Also there was a app called "Agile reply" for iphone but i cant find that app in the app store actually.it seems that it has been removed from the app store
I would like to develop an app like sending sms on missed call / un answered call.that app needs to be posted on "App store".my app needs to run on iOS 4.0 and 5.0
Please share your view on developing app with this kind of functionality and its possibility
why this kind of app will be rejected.
The Agile Reply app didn't send texts automatically upon a missed or unanswered call -- it just allowed you to quickly compose a message to the last number that called.
If Apple have decided they're unhappy with this sort of app, that's the end of the story. They have their reason(s), and whatever you think of those reasons, they're the gatekeeper of the app store; their say is final. Of course it might be possible to develop something like this for jailbroken devices, but that's a different story.
As for the reason that Apple didn't like the Agile Reply app: the following two reasons seem plausible to me (but are also just educated guesses on my behalf):
1) The app accessed private APIs
2) Apple thought that the app didn't offer anything new or worthy: they might have reasoned that it is easy enough to go into the built-in phone app, select the last (missed) call, and compose a message to that number, without the need for a custom app
One of my apps is in the appstore and I got a call from one of our clients saying a specific feature in the application is consitently causing the app to crash. However, I don't see any logs in iTunes Connect rightnow. Is there a delay between the app crashing and the log being submitted? If so, how long does it usually take?
Thanks,
Teja.
You'd be better asking them to send you crash reports directly. If they sync their handset using iTunes there will be a copy on their PC/Mac.
Unfortunately it seems that people are syncing their phones less and less often. (Which means they never make it into iTC.) Also, not all of them make it into iTC. Apple aggregate them but there also appears to be some level of filtering. What they do is not documented.
This blog explains what I ended up doing with my apps.
You should use a service like Crittercism - They give you real-time crash reports. You could also use something open-source like PLCrashReporter if you want to implement the server yourself.
The delay really depends on how long it takes before the user syncs their device with iTunes. I believe after that it's pretty quick.
Also it's worth noting that iTunes Connect needs a few crash reports before it displays them.
I wrote a nice app that would simplify life for many - somehow similar to these phone card apps. However, there is one private API function which I have to use to send a hash '#" in a phone call because the receiving hardware requires this. (which is understandably not allowed because of POSSIBLE abuse). But
My app does not missuse or in any way
cause damage.
Certainly the reviewers at apple don't have time to review for each single use of such functions - so therefore my app got rejected by the automated API check (so I assume). Yes I know that these issues are documented well by Apple, but I was hoping they would really "check" abuse possibilities of apps and then reject - or accept if the app is not harmfull in any way. (as happened in a similar case in appstore)
Anyway, if I don't find another solution this app will not be accepted.
What to do now?
Does it make sense to write an explanation comment when submitting to review?
Is there an alternative to send the signal of a # during a call somehow?
Is there an alternative way to sell/distribute apps? Will this affect my future apps to be submitted? What is your experience?
ps certainly, the Android version is available soon...
Thanks!
An option would be to submit it as a bug and request they "support send a hash '#" in a phone call".
You can always try the Cydia store, and probably there are other ways in the jailbreak community.
Just checked the status on one of my iPhone applications and noticed it was rejected. However, due to complications the email account I have on the account is unavailable. So, that leaves me with absolutely no clue as to why the app was rejected.
Is anyone aware of any areas on apple's site that allows you to research why a specific app was rejected? Or am I stuck waiting the 2-3 days for a response from Apple support?
I think at the Resolution Center you can get your information. Take a look at http://developer.apple.com/appstore/contact/appreviewboard/index.html
There are can be variety of reasons for rejection. Known list of possible reasons will not help you, cause you really need to know exactly why they rejected it. Sometime you don't even need to re-submit application but simply change description.
You really should have email account available when doing any AppStore related activity.
I am unaware of any area on Apple's developer connection that lists this info. If your email server has been sending all your email to /dev/null, your best bet, after you fix and test your ADC email account, might be to resubmit the exact same binary again, with an explanation in the update notes, as that could well take less time than waiting for Apple support.
To solve this issue you would need or to email them again asking for a reply on the rejection message that states the reason for it, or resubmit the app and wait for them to review and reject it again.
Be sure to setup an email account that you are able to monitor.
The review after rejection starts usually quicker than when submitting a new app or new update, and so you would have a feedback in 2 or three days, that would be the same time they would take to reply you with previous rejection reason (if it is possible).
I would go for:
Setup the email and other info.
Resubmit the app and wait for the rejection again.
Good Luck!
Here is a good list of reasons that app's have been rejected for and it explains all of them.
http://iphoneincubator.com/blog/app-store/rejections