I have developed an iOS app that uses Amazon AWS services. To Authenticate users through Amazon Cognito I am using Facebook and Google login as external identity providers. Apple just rejected my application because I'm using Facebook and Google just for login purposes and am not making extensive use of their features.
My employer wants to setup a Facebook/Google+ page for the application where the app will post on behalf of the app users. Does anyone know if this use-case would be good enough for Apple to approve the app? I would also want to know what the minimum requirements of using features are that would be acceptable for Apple. Thanks!
Related
Apple just rejected my app due to I don't offer Sign in with Apple in my app as my app allow login with Google and Linkedin, and these(sign in with Google and Linkedin) are configurable like if some user don't want this it'll be disable by Admin.
So Can I go with another try to remove this option for that user which we give to Apple for Review and also tell them its configurable and not mandatory. So will Apple accept my app ?
Thanks
Personally I do not recommend using different configurations only for the App Store review process, because you can get rejected from App Store completely for cheating on the process. Read more at:
https://developer.apple.com/app-store/review/guidelines/#introduction
If you attempt to cheat the system (for example, by trying to trick
the review process, steal user data, copy another developer’s work,
manipulate ratings or App Store discovery) your apps will be removed
from the store and you will be expelled from the Apple Developer
Program.
About Apple Sign, here is Apple guidelines regarding this feature:
4.8 Sign in with Apple
Apps that exclusively use a third-party or social login service (such
as Facebook Login, Google Sign-In, Sign in with Twitter, Sign In with
LinkedIn, Login with Amazon, or WeChat Login) to set up or
authenticate the user’s primary account with the app must also offer
Sign in with Apple as an equivalent option. A user’s primary account
is the account they establish with your app for the purposes of
identifying themselves, signing in, and accessing your features and
associated services.
Sign in with Apple is not required if:
Your app exclusively uses your company’s own account setup and
sign-in systems.
Your app is an education, enterprise, or business
app that requires the user to sign in with an existing education or
enterprise account.
Your app uses a government or industry-backed
citizen identification system or electronic ID to authenticate users.
Your app is a client for a specific third-party service and users are
required to sign in to their mail, social media, or other third-party
account directly to access their content.
Read more:
https://developer.apple.com/app-store/review/guidelines/#sign-in-with-apple
I got following email from apple
1.0.1 Binary Rejected June 16, 2015
17.2 Details We noticed that your app uses Facebook login for authentication purposes but does not include account-based features
offered
I got following attachment
From Apple
17.2 - Apps that require users to share personal information, such as email address and date of birth, in order to function will be rejected
17.2 Details
We noticed that your app uses Facebook login for authentication
purposes but does not include account-based features offered by that
site, which is not allowed on the App Store.
Next Steps
Please modify your app to include account-based features of that
social network or use your own authentication mechanism.
what is the reason behinds it.
I have study the following links
https://www.parse.com/questions/app-rejected-facebook-login-doesnt-complete
App got rejected because only using Facebook as login option?
Apple rejected app 10.6 because Facebook opens Safari to login
Apple review Guidelines says here
5.1.1 Data Collection and Storage
(ii) If your app doesn’t include significant account-based features,
let people use it without a log-in. Apps may not require users to
enter personal information to function, except when directly relevant
to the core functionality of the app or required by law. If your core
app functionality is not related to a specific social network (e.g.
Facebook, WeChat, Weibo, Twitter, etc.), you must provide access
without a login or via another mechanism. Pulling basic profile
information, sharing to the social network, or inviting friends to use
the app are not considered core app functionality.
I've a published app that has an optional login feature without any "account-based features".
I think providing a "continue as guest" option will fix the issue.
This means that your app didn't implement another feature of Facebook anywhere else in your application, if you're asking for explanation. If you make an app that just has Facebook's Log-in API, but nothing else, then your app will be rejected. Find another feature of Facebook (such as sharing or invites) that you can implement somewhere in your application, and try again.
A few possible steps you can take:
Ask App Store review people for clarification. Wait until you didn’t
get a response from them
You can make user registration optional or only prompt for it where
it actually requires
Try it.
Add note, while submitting app,the purpose of using Facebook login in resolution center without uploading new build it will be approve.
If still you face any issue then add some functionality of user login.
For Ex: Use of facebook login is for keeping all records of user in our database and also explain a bit about your app functionality why you use login feature.Hope it will help
Also check
iPhone app rejection 17.2: app requires users sign in with their Facebook accounts
We are making an app that can sell event tickets from an iOS app. Right now I have implemented Paypal and Stripe payments on my app to charge the customer.
I was asked to integrate Amazon payments on our "NATIVE iOS" app to charge the user of purchased event tickets. I found the integration instructions on the Amazon Payment site but it seems to be compatible for websites only. See https://payments.amazon.com/developer
This was written on their home page:
"Login and Pay with Amazon is the fast, easy and secure way to pay on desktop, tablet and mobile." - https://payments.amazon.com/home
Can you show me how to do it on Swift or Objective-C?
Note: This is about charging the client for payment of a product and not integrating the normal Amazon login or Amazon web services which I think is a different thing from "Amazon Payments" which should be similar to Stripe and Paypal.
From: https://payments.amazon.com/documentation/lpwa/201749840#201749840
Note: The Amazon Payments service has been designed and developed for use within a web browser only. Our Service cannot be used within a native application (including, without limitation, iOS, Android, RIM and Windows operating systems). Amazon Payments reserves the right to suspend the Payment Account of any user of our services that has implemented our Service within a native application.
Check out this resource I found some time back:
http://www.chupamobile.com/resources/amazon-mobile-payment
However, I am not one hundred percent sure you can actually integrate Amazon Payments into the iOS app natively, as there isn't an official SDK or API that you can use for Android or iOS. However what you could try to do is integrate their C# SDK into your project and then access it through your app.
Hope that helps.
We are trying to integrate Google adwords connectivity into our Marketing Analytics Web application, meaning we are creating an app that would allow small businesses to login to their AdWords accounts and manage them based on findings of our app.
The problem is that upon signing up for API Access AdWords is asking us to link 'our' adwords account to the app account as well. This does not make too much sense to us, why do we need to show our adwords account when we ourselves will not be the main users of the app. It almost seems that AdWords assumes only a couple of users will be using the API.
Is my thinking flawed here? Can anyone clarify?
Google does seem to assume that their AdWords API is used primarily for in-house reporting and account management (as well by advertising agencies managing accounts on behalf of their clients).
Even if you are building an app for general, public use, the app's Client ID, Client Secret, and Developer Token are still connected to your company's MCC account.
However, this does not cause a problem. Any AdWords account owner can authorize your app to access their data, without having to be your client.
I want to do this because I am building an app, which is going to be used within a campaign and many people will be asked to login in their twitter account, in the same device.
Instead of using the default account of the iOS device, you can use Twitter's own OAuth tokens and then handle them independently in your application.
You can see the documentation at Twitter's Developer Site