It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 11 years ago.
I needed to use location in background mode so that I can track if the user has entered into a region or not. But my app was rejected with the following message:
Additionally, we found that your app uses a background mode but does not include
functionality that requires that mode to run persistently. This behavior is not
in compliance with the App Store Review Guidelines.
We noticed your app declares support for location in the UIBackgroundModes key in your Info.plist but does not include features that require persistent location.
It would be appropriate to add features that require location updates while the app is in the background or remove the "location" setting from the UIBackgroundModes key.
Can anybody help me out; am I missing something?
Is location tracking necessary for the described functionality of your app?
Did you clearly describe the location tracking feature in your app's description?
Did you test your app to make sure that Location services actually still runs without quiting and without errors when your app is in background mode for an extended period of time?
If this functionality needs to be enabled by the user, did you explain how to do so in the review notes?
ADDED:
Can a user in Cupertino tell by the app's behavior that Location services was running in the background?
"I needed to use location in background mode so that I can track if the user has entered into a region or not."
From the rejection, either Apple didn't accept your view that you needed this functionality (i.e. it was unnecessary for the functioning of your app), or that you had failed to actually implement this. I wonder if it is the latter. If your app does nothing with the background notifications of location change, and would have operated exactly the same if it just got a location update when it is re-launched, then it does not need to be running in the background. Could that be the issue?
Related
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 9 years ago.
Nowadays I am thinking about a mobile application (specially for iPhone) and trying to build it for personal use and of course will allow to others too. I want to develop such application, suppose I have iPhone device.
My iPhone get missed call in the absence of me and in that that case suppose I missed some urgent call and I really did not want to miss them. So that my device should have automatically sent messages to them all that I could not receive those calls in due to my absence and message would be like "I am unavailable right now, please call me back or wait for my call".
So all that was the idea of mine I want to develop such mobile application, I would keep each think in my mind like don't send unnecessary reply even not needed. I'll look to the UI part also. That's why I am studying AddressBook frame and all related tutorial, and gathering all required thing to go ahead. But before going ahead on coding part.
Apple doesn't have any public (developer-accessible) API's that allow what you are trying to do (either sending a SMS or a voice mail response back to somebody saying "I'm not available" or "I will be available in 2 hours").
Nor would Apple likely allow an app like this onto the app store if you wanted to sell or make it available to other people aside from your personal device, as apps that interface with phone functionality may violate some countries' privacy laws, not to mention Apple's own privacy guidelines.
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 10 years ago.
My application is being rejected for the following Reason, Since its my first App. What Change should i made to proceed.Please provide me some solution?
10.1: Apps must comply with all terms and conditions explained in the Apple iPhone Human Interface Guidelines and the Apple iPad Human Interface Guidelines
We found that your app includes a UI control for quitting the app. This is not in compliance with the iOS Human Interface Guidelines, as required by the App Store Review Guidelines.
Always Be Prepared to Stop
iOS applications stop when people press the Home button to open a different application or use a device feature, such as the phone.
In particular, people don’t tap an application close button or select Quit from a menu. To provide a good stopping experience, an iOS application should:
Save user data as soon as possible and as often as reasonable because an exit or terminate notification can arrive at any time.
Save the current state when stopping, at the finest level of detail possible so that people don’t lose their context when they start the application again. For example, if your app displays scrolling data, save the current scroll position."
It would be appropriate to remove any mechanisms for quitting your app.
Do not provide buttons or options for exiting from your application.
If you do so apple will reject your application.
Also if you call exit(0) from your application at certain point, apple will take it as a crash.
So never do it, your app will be rejected.
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 10 years ago.
I wanted to get some clear "real world" info on what kinda backend is required when running a newsstand app.
The app i intend to make should have the following features.
Issues, each issue with a bunch of articles.
An Issue can be "Free" or "Paid" depending on how its "Pushed"
Auto subscriptions
Push notifications
Data collection - getting some stats from the users.
I currently have no server, in this case, whats the server requirement? All i want is a print magazine kinda app, essentially a PDF. Is it possible to let Apple host the data with current issues.
Another question besides the server is, how are these Issues packaged? Forexample if its a text file or a pdf?
Any direction would be great
Taking your points in turn:
I currently have no server, in this case, whats the server requirement? All i want is a print magazine kinda app, essentially a PDF. Is it possible to let Apple host the data with current issues.
Apple does not provide hosting for newsstand content. You need your own server for this. It needs to hold the issues, and usually also respond to requests from your app about available and new issues.
Another question besides the server is, how are these Issues packaged? Forexample if its a text file or a pdf?
They are packaged however you like - you tell the newsstand framework which asset(s) need downloading for a particular issue (based on the response youve given about the issues above) Typically you'd bundle it all together in a zip file and unpack / process it on the device when the download is completed.
It's important to note that newsstand is not much more than a framework to enable backgrounded downloads and notifications, and to maintain a library of assets in your app's caches directory. The content and its display is entirely up to you, the developer.
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 10 years ago.
I want to create an iPhone app that would restrict incoming calls and SMS from a given phone number.
The phone would not ring or light up the screen. It simply would not do
anything when a call was received from that number. Also, in the recent call list, the number should not show up. When user opens my app, it would show the black list numbers.
Is this possible to develop, and will Apple approve this?
Nope, you can't interfere with calls or SMSes in any way.
There is absolutely no way to do this and still be accepted in the App Store. No API provided by Apple can do anything like this. I don't know what more I can say to answer this.
Maybe Core Telephony would help you take a different approach. Even some things that you can do with that could prevent your app from being accepted into the App Store.
First, I don't think it's even possible to intercept an incoming call. All processes have a priority assigned to them, and phone calls are one of the highest (more so than standard apps), so an app can't interrupt a higher priority process.
Secondly, it's not possible for an app was able to intercept an incoming call (or SMS), as that's a major security flaw. Your app can only access the contents of its sandbox (and some shared directories, such as photos).
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 11 years ago.
I would like to track (run some code - or invoke function) when the user get an incoming call.
for example: for every call the user receive I want to save the number, and check something during or before the call is answered (with a background process..)
Until now without the background processing I couldn't find a way to do this. But I'm still not sure it is possible.
Anyone with information about the new sdk 4 can help me?
You can register for notifications using CTTelephony and your app will NOT terminate while the call is in progress. Control is returned to the app at the conclusion of the call and then you can get the phone number.
All of this is useless for apps to be published in the App Store until Apple approves use of the CTTelephony API.
There is nothing in the published material that would suggest that there's any change. The seven types of multitasking listed were:
Background Audio
Voice Over IP
Location Services
Push Notifications
Local Notifications
Task Completion
Fast App Switching
Intercepting normal cell calls doesn't really fit into any of those categories.