Apple rejecting app because of "Create Account" on login page

[James Montemagno]

I have created an app that needs my user to login. I am opening up the mobile auth page and everything works great, except that apple continues to reject the app because there is a create account on the login page. Here is my rejection notice:

• 11.13: Apps that link to external mechanisms for account creation, purchases or subscriptions to be used in the app, such as a “buy" button that goes to a web site to purchase a digital book, will be rejected

11.13

We found that your app provides access to external mechanisms for purchases or subscriptions to be used in the app, which is not in compliance with the App Store Review Guidelines.

Meetup.com - plans start at $6 a month
- all links and text "Meetup.com" need to be removed from the app description and the login screen
- any new user registration needs to be removed from the app

Is there anything we can do about this? The back button on top should be removed along with any promotional sign ups and the "don't have an count" option.

Thanks!

[Nathan Hamblen]

Could you tell us a little about the app you've made?

Nathan

On 01/25/2014 02:17 AM, James Montemagno wrote:
> I have created an app that needs my user to login. I am opening up the
> mobile auth page and everything works great, except that apple continues
> to reject the app because there is a create account on the login page.
> Here is my rejection notice:
>

> * 11.13: Apps that link to external mechanisms for account creation,

> purchases or subscriptions to be used in the app, such as a “buy"
> button that goes to a web site to purchase a digital book, will be
> rejected
>
> 11.13
>
> We found that your app provides access to external mechanisms for
> purchases or subscriptions to be used in the app, which is not in
> compliance with the App Store Review Guidelines

> <https://developer.apple.com/appstore/resources/approval/guidelines.html>.

>
> Meetup.com - plans start at $6 a month
> - all links and text "Meetup.com" need to be removed from the app
> description and the login screen
> - any new user registration needs to be removed from the app
>
> Is there anything we can do about this? The back button on top should be
> removed along with any promotional sign ups and the "don't have an
> count" option.
>
> Thanks!
>

> --
> --
> You received this message because you are subscribed to the Google
> Groups "Meetup API" group.
> To unsubscribe from this group, send email to
> meetup-api+...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/meetup-api?hl=en?hl=en
>
> ---
> You received this message because you are subscribed to the Google
> Groups "Meetup API" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to meetup-api+...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

[James Montemagno]

Sure thing!

It is a very simple app that I made over the holidays. I started a meetup here in Seattle and I found it hard to have a way to have my members check in when they arrive. I wanted to then use who was actually at the event to select winners for give aways. That is when I created "Meetup Manager", which goes out and based on the user logged in will find their meetups, events, and then display anyone that has RSVPed to the event. Then the members can find their name and check in when they arrive. I have it already published on Google Play: https://play.google.com/store/apps/details?id=com.refractored.meetupmanager

It is open sourced on GitHub: https://github.com/jamesmontemagno/MeetupManager

I also have a windows phone version in the works as well.

Thank you,

James

[James Montemagno]

The main issue happens to be the landing page that has the sign up links. Please see attached

[Nathan Hamblen]

Hi James, I tried out the app a few minutes ago. Pretty cool!

I agree that some characteristics of the oauth login screen are the main
issue. We're going to make some improvements there, Doug will keep you
posted on the progress.

Even with that, it might be to your advantage not to drop a new user
immediately into the oauth login screen. It would be clearer (both for
your users and any app stores reviers) if you have a start screen that's
descriptive of your app, which would include a button to "Log in to Meetup".

Nathan

On 01/30/2014 12:17 PM, James Montemagno wrote:
> The main issue happens to be the landing page that has the sign up
> links. Please see attached
>
>

[James Montemagno]

Nathan,

That is great news. I am glad that you liked the app. It was a really quick app I made over the holidays. I am an android guy so no issue with certification there. I know that DropBox had this issue with Apple a while ago and they made a new iOS specific oauth page that only allowed login. I have attached what it looked like. 

I will also update the text to say Login to Meetup. I like that wording a lot better.

I would love to get the app out there sooner than later so let me know how it goes. From my understanding that is the only way to actually be able to do per user auth. I know the official meetup.com app does it differently by doing it all in app. Is that publicly available?

Cheers,

James

[Nathan Hamblen]

On 01/31/2014 03:50 PM, James Montemagno wrote:
> I know the official meetup.com app does it differently by doing it all
> in app. Is that publicly available?

No, we can't provide an endpoint that would require members giving
passwords to a third party. But we'll see what we can do to improve the
oauth experience.

Nathan

[James Montemagno]

Nathan,

That makes sense to me. Hopefully you can figure out the oAuth experience even if we have to use a custom URL for iOS or pass in a specific parameter. Either of these would work great. 

In other news, the Windows Phone version just hit the store: http://www.windowsphone.com/en-us/store/app/meetup-manager-for-organizers/38ef03e9-3dfe-4150-b797-5ec9ed81b8cd

Cheers,

James

[Doug Tangren]

Hi James, 

Sorry it's taken so long but we finally pushed some fixes out for this. You should be able to suppress member registration in the oauth flow by providing a new parameter called "suppress" set to "reg". I documented it here http://www.meetup.com/meetup_api/auth/#oauth2-user-signup. The gist is that when you provide this the user is not given an option to register for a new account, essentially making the logged out view a look like a login only form. The default is to show the registration link.

Let me know if you have any other issues.

Doug Tangren
Meetup Platform Engineer

--

[James Montemagno]

Doug,

This is great to here. I will be trying this out immediatelly. So should it look like this:  https://secure.meetup.com/oauth2/authorize?suppress=reg...?

Thank you,

James 

[James Montemagno]

Doug,

I got it working! I added the suppress + reg in there and that did the trick. One thing I still noticed was that it has the < [meetup logo] on the top left which would allow them to navigate back. I will see if this is an issue for Apple and report back once I submit the app.

Best,

james

On Friday, March 14, 2014 10:41:06 AM UTC-7, Doug Tangren wrote: