5 replies to this topic

[Slavik]

My app is rejected by Apple.

They said that the login page poped in safari is against the guid line, that I should note show a web site with link for purchases or subscriptions

I have explained to them that the page is for login purpose, that the use will not buy anything on it. But they insist.


The attachment is a snapshot of the replay in itunesconnect resolution center.

Since there is no basic auth api access, I wonder what shall I do then.

Is there anybody can help me with it?

Attached Files

•  67290795-A3F1-46EC-8127-6646D3C84F35.png   113.82KB   21 downloads

[AndyDent]

The new version of the SDK as of 14 June has a sample app showing how it now uses an embedded controller and doesn't launch Safari. The sample also has both iPad and iPhone storyboards

[Slavik]

Thank you.

I will try that.

[SethH]

Slavik, we're very sorry about the trouble that this is causing you. We've been working to resolve this issue, and thought that we had it taken care of. As Andy pointed out, our most recent step was to switch the authentication into an embedded web view instead of opening Safari. This will require some changes on your part, but they shouldn't be significant. Please let us know if you have any trouble updating to the latest SDK, and let us know how it goes when you resubmit.

[David Chevenement]

Dear All

thanks for the fix.
Just one question to gain time in the update process.
we did remove and replace the old sdk files in pour projects with the new ones and changed

[session authenticateWithCompletionHandler:^(NSError *error) {
by
[session authenticateWithViewController:self completionHandler:^(NSError *error) {
to use the new authentication scheme.
Looks like there nothing much to it.
Could you confirm ?

Regards,

[David Chevenement]

Dear Evernote Team

the update works great, took 2 minutes to update.
a few remarks though:
- we cannot manage the modal view controller that is presented to the user. It currently coming out with no *****le. How can we update this part, knowing that setting yourself a default *****le could be a problem, particularly if we need to handle multilingual file. Can you point to a workaround ?
- in the opened web view, you set your modal view controller style to form sheet but the login page provided by the evernote web server does not accommodate for it. It does not really good and the user have to scroll to the correct screen location for user/pwd prompt. Could you indicate a fix ? 2 possible solution: provide a dedicated iOS landing page for login or set the web view to size to fit at launch so that the web view display the entire page.


To share with others, the cancel button fires an exception error with authentication failure with error set to nil. be sure to test for this when giving user feedback about possible errors.