I have referred all question of stackoverflow but i don't found exact answer of what I want. Can we use google's direction api for drawing route ? Here in sense of does it create any problem in application submission. Will Use of this api violate any rules of google or apple that may cause application rejection ?
We looked into this for a project last year. Short summary:
If you use the Google Maps API, as provided by Apple, you are not allowed to do any kind of route-finding / mapping. This is part of the license that Google gave to Apple, and Apple gave to you. If Apple notices you doing this, they will probably reject you (they don't want to get sued by Google).
However, if you use Google Maps without Apple's code (i.e. do not use UIMapView etc), and instead go direect to Google, you may get a different license. In that case, you should be accepted - it's not longer Apple's problem, so they're happy.
(off the top of my head, the license you get direct from Google still bans using route finding)
If you embed a UIWebView, and do the route-finding directly on a Google-provided webpage, that's fine.
(but: read the license agreements carefully. The Apple/Google license is in the SDK documentation, and the Google license is easy to find on the web, just google for it)
Related
I got following message from app review team, now i am confused how to fix it and what is the problem exectly any help would be appreciated.
2.5
We found that your app uses one or more non-public APIs, which is not
in compliance with the App Store Review Guidelines. The use of
non-public APIs is not permissible because it can lead to a poor user
experience should these APIs change.
We found the following non-public API/s in your app:
currentHost
If you have defined methods in your source code with the same names as
the above-mentioned APIs, we suggest altering your method names so
that they no longer collide with Apple's private APIs to avoid your
application being flagged in future submissions.
Additionally, one or more of the above-mentioned APIs may reside in a
static library included with your application. If you do not have
access to the library's source, you may be able to search the compiled
binary using "strings" or "otool" command line tools. The "strings"
tool can output a list of the methods that the library calls and
"otool -ov" will output the Objective-C class structures and their
defined methods. These techniques can help you narrow down where the
problematic code resides.
We appreciate that you may have made the precautions in your code for
using non-public APIs, however, there is no way to accurately or
completely predict how an API may be modified and what effects those
modifications may have. For this reason, we do not permit the use of
non-public APIs in App Store apps.
If there are no alternatives for providing the functionality your app
requires, we encourage you to file an enhancement request. Or, try
working with the Apple Developer Technical Support team to explore
alternative solutions.
On occasion, there may be apps on the App Store that don't appear to
be in compliance with the App Store Review Guidelines. We work hard to
ensure that the apps on the App Store are in compliance and we try to
identify any apps currently on the App Store that may not be. It takes
time to identify these occurrences but another app being out of
compliance is not a reason for your app to be. For discrete code-level
questions, you may wish to consult with Apple Developer Technical
Support. Please be sure to:
include the complete details of your rejection issues
prepare any symbolicated crash logs, screenshots, and steps to reproduce the issues for when the DTS engineer follows up.
For information on how to symbolicate and read a crash log, please see
Tech Note TN2151 Understanding and Analyzing iPhone OS Application
Crash Reports.
If you have difficulty reproducing this issue, please try testing the
workflow as described in
https://developer.apple.com/library/ios/qa/qa1764/Testing Workflow
with Xcode's Archive feature".
any help would be appreciated.
It looks like you are using this method to get your current ip in your application. You can use other alternatives like in the link mentioned:
https://stackoverflow.com/a/6535436/1111384
You can use this to get current ip.
Hope this resolves your issue.
Does anyone know if I use the Twitter Framework will my app contain encryption?
Frameworks are not included in your app. They are in the device's firmware and are not copied into your app. So even if an iOS framework had encryption in it, it is not included in your app, you just make function or method calls to it, and are not distributing encryption software.
I think no one really answered your question directly; they were merely inferring your intent. The Twitter framework docs only mention HTTP for API requests. The Twitter docs on this say that SSL is optional though encouraged. So I'd imagine that iOS is handling user authentication via SSL in the background, but that all API requests by developers are done over HTTP using oauth. This is only speculation -- to verify you'd want to run a packet sniffer on your local network and check out the transactions when you call the framework methods.
Regarding the export controls mentioned in other comments here, I'd advise you to look at the iTunes Connect FAQ dealing with export controls within the Dev Center. Apple makes it very clear in that document that using encryption integrated into the iOS frameworks still requires you to apply for an ERN with the US Dept. of Commerce. (I won't quote it due to NDA) The other comments currently on this page are simply wishful thinking. I'm sure some developers were confused (and it is confusing), or perhaps have outright lied and have apps in the store which are violating US law. IANAL; I'll leave that choice up to you.
Having said that, there have been some exemptions added to these requirements, as outlined here.
there have been some confusion about using analytics in apps. Just to make sure I got it straight:
I want to use Google Analytics in my app to track app usage (tracking what content is being viewed basically). I'm not sending any user or device data to Google.
Firstly, I understand that Google Analytics API is completely fine to be used and doesn't violate any Apple developer agreements.
Secondly, I assume that in this case (anonymously tracking app usage - no user or device data) I am allowed to use the service without the need to say anywhere in the app that analytics is being used (so the 3.3.9. of 'iOS Developer Program License Agreement' doesn't apply here).
Can anyone confirm my assumptions or explain if they are not right?
Or better did anyone of you have your app using analytics approved even though it didn't say anywhere it is using it? ...or the opposite
I've seen plenty of forum entries on the subject none of them though clearly stating what is required by Apple and what is just recommended.
Thanks
I know you're asking about Google Analytics, but for what it's worth, I've had great success using the Flurry analytics package in my apps. It's very stable and provides a lot of great metrics. If GA doesn't work out for you, I'd say give this a try:
http://www.flurry.com/
Is this a violation of Apple app development rules? In some forums I just saw that thing. So am afraid of getting rejected by AppStore if I use the same. Help me with this please. And if I can't use Google Analytics SDK then which will be the best analytics method I could implement for my App?
This is not legal advice, but, as of right now, no apps have been rejected by Apple for using Google Analytics.
Google has released an official iOS Google Analytics SDK, and there is no record of Apple explicitly forbidding or discouraging its use.
Google Analytics is the most widely used analytics solution around, and unless your operations are based out of Germany, you likely have little to worry about.
I'm not sure about Google Analytics vs Apple rules, but if you're just looking for any way to have stats, have a look at Flurry Statistics - it's quite powerful and completely free. Also I never heard of any legal issues with it (I think you just need to inform users in your app's EULA that you collect data to make the application better).
my name is Peter and I'm with Flurry. Thanks to delirus for pointing out that we have a free service. We support iOS, Android, BlackBerry, WP7 and JavaME. Regarding iOS, we have no knowledge that any app has been rejected during the app submission process due to the inclusion of Flurry Analytics. Over 38,000 companies use Flurry Analytics. You can learn more at www.flurry.com. Thanks, Peter
Google Analytics is under scrutiny in certain regions of this planet because some people believe they are not respecting data protection laws and legislation.
So even if Apple accepts your app you run the risk of somebody filling a complaint with Apple and as result your app could be withdrawn at a later stage.
If you don't know yourself which analytic tool is best for your needs then I assume you have not really thought about what data you really require. Take a moment or two to come up with a list of requirements and then start looking for the tool best matching the needs.
As per the title. I searched all through the Apple website, and cannot find anything about it. I am not an iPhone developer member (yet) so don't have access to that stuff. I just want to develop an Android application that can talk with the FaceTime protocol.
It would be a bit silly if we all had to pay Apple just to view the FaceTime documentation to implement the protocol in our non-iOS applications.
The docs for facetime are not yet available. You're not missing anything.
Apple has been unable to release it as an open standard because of the patent battle it lost.
There is community documentation of the protocol, including this series of blog posts:
Special Look: Face Time
part 1: Introduction
part 2: SIP and Data Streams
part 3: Call Connection Initialization
At least to get started, take a look at this for the list of IETF standards used by Facetime: http://blog.imtc.org/index.php/2010/06/09/the-technology-behind-apples-facetime-standards/
Additionally, Apple has said it will be submitting Facetime as an open standard - so there should be more documentation on how all these standards glue together in Facetime. . anyone know when this will come out?
Update
You don't have to pay to test on devices as of 2015. Payment is required to deploy on the app store, get beta access and sundry other stuff as per Apple's page
Original
You don't have to pay to get the SDK, just to be able to test on devices