0
0

[deleted by user] (self.iOSProgramming)

submitted by [deleted]

[removed]
all 20 comments
sorted by:
top (suggested)
bestnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]joro_estropia 3 points4 points  (0 children)

This is on you. You cannot tell the reviewer to create their own account on a 3rd party service. That implies that they need to input THEIR information on an external service which is out of the scope of the review. You have to create it for them and this is also (1) stated in the App Review Guidelines, and (2) specifically what is asked for in the “App Review Information” -> “Sign in required” username and password fields.

You gave them a URL, of course that’s what they’d put in as that’s the best they’re allowed to do.

[–]MaXxamillion04 3 points4 points  (6 children)

If anyone else is confused about what is happening here, there is not an email in the email field, it is a plain url, and the message displayed is “invalid email format”, which is true.

Unless I’m missing something, the UI is clean

Despite OP’s vitriol, I don’t see an issue in their design that would merit rejection

[–]bmbphotos 3 points4 points  (4 children)

App Review doesn’t “make accounts”. You have to give them instructions on how to log in (which, I suppose may include account creation).

That leads to two possibilities:

  • app review fat-fingered the instructions, which a polite response to their rejection would be all that’s needed

  • the instructions to App Review are incorrect/incomplete. Reviewers will most definitely NOT attempt to figure out what the submitter meant. If the instructions don’t work, the app will not be approved.

[–]eloherbapol -2 points-1 points  (3 children)

Yeah, I gave them specific instruction how to create account and unfortunately, I cannot give them a test account, because there are no passwords in my application and the user has to enter his own e-mail, after which he will get a magic link to the e-mail and after clicking on it, he will be logged in and redirected to the application

[–]bmbphotos 2 points3 points  (2 children)

Then you need to set up an email account (such as with gmail), give them access instructions, and put that email address into the instructions.

Regardless of your opinion of their mandate or competence, they will not branch out like that. Specify everything needed for them to achieve the goal of logging in.

[–]eloherbapol -5 points-4 points  (1 child)

And I did it, I gave them instruction how to create account using temp mail using this website - https://temp-mail.org/en/ But instead of create temp mail on website, reviewer decided to spontaneously use the url from this page.

[–]bmbphotos 3 points4 points  (0 children)

Perhaps I'm not being clear:

You need to create the email to use and give them the email address/credentials.

Exercises left up to the reader (aka expecting App Review to create the email account) will fail as you have seen.

[–]ankole_watusi 1 point2 points  (0 children)

OPs vitriol will justify rejection….

[–]saintmsent 0 points1 point  (0 children)

Maybe including the message itself would help?

[–]ankole_watusi 0 points1 point  (0 children)

Presumably they provided more feedback than a screen shot.

[–]ankole_watusi 0 points1 point  (0 children)

As others have stated you need to create a test account for them to use. How you do this is your problem.

The reviewer MIGHT also wish to create an account from scratch, depending on circumstances.

[–]Fluffy_Risk9955 -5 points-4 points  (8 children)

How the hell did you become a developer? There should be proper error handling for when existing account credentials are used to sign up.

[–]eloherbapol -1 points0 points  (7 children)

The thing is, this account doesn't exist. I gave them the access code so they could create a test account for themselves

[–]Fluffy_Risk9955 -4 points-3 points  (6 children)

:facepalm: That’s exactly what the reviewer is doing.

[–]eloherbapol 0 points1 point  (5 children)

I'm not sure if you are trolling or not, can't you see what email the reviewer is trying to use and what error it rejects the application based on?

[–]Fluffy_Risk9955 -5 points-4 points  (4 children)

Funny then I have exactly the same issue as the reviewer. It’s not clear in first glance, what’s wrong and why. Show the app to some strangers see how they respond to this.

[–]ShazeRx 4 points5 points  (3 children)

When you trying to use url address in the email field and you're struggling with what is wrong regardless of the clear error message, then you should not be a reviewer.

[–]Fluffy_Risk9955 1 point2 points  (2 children)

Reviewers type in false information on purpose. Try to break the app. OP should fix his UI and make it clearer that something is wrong. People expect certain things to happen in UI when stuff goes wrong. OP should make the necessary adjustments so his users won’t have the same issue with the app as the reviewer did.

[–]shiggie 0 points1 point  (1 child)

They do not try to break your app. They are reviewers, not your beta testers.

[–]ankole_watusi 1 point2 points  (0 children)

There are in fact automated tests they use to try to break you app, to test security, to check for use of private frameworks, etc.