review without sign-in information

Question

Created Oct ’17

Replies 3

Boosts 0

Views 1.9k

Participants 3

I am trying to submit an application for a banking client. The application supports a 2-factor authentication into the user's banking account. The token that gets generated it tied to the user's bank account (cannot be used to access anything but the account), so providing 'demo' sign-in information is impossible to do with the submission process. Consequently, I unchecked the 'sign-in' information checkbox on the submission application, but recieved a rejection and request from the Reviewer asking for the sign-in information. I have tried to explain this architecture in several appeal responses, but am not getting anywhere with the Apple review process.

Has anyone else expereinced the problem of getting review approval for an application that cannot be fully demo'd like this? Is there a specific wording that the Apple review team will understand that indicates this scenario in order to pass the submission review? I've done this before for other clients with the exact same application without error, so I believe this is a random review issue I am running into (though it may be new with 11).

Thanks.

Boost

Answer 1

PBK OP

Oct ’17

Can't you create a fake username/password that responds as if the user was interacting with the bank? Alternatively, can't you create a bank account with a minimum deposit and provide App Review with those credentials?

0

Answer 2

nikitameduha OP

Nov ’20

..

0

Answer 3

nikitameduha OP

Nov ’20

I have a similar problem for a client from insurance company which uses 2-factor authorization. This is not our first client/app to face the same issue, but up until now Apple has provided an alternative in this type of situations - instead of providing a demo account, we would send a filmed video with the app being used.

... well this was possible before, but now with our latest app (for our insurance client) Apple insists on providing demo account, but it is not possible to do. We would brake law by doing it.

I guess that this situation can be applied for any app that uses secure authorization. I'm really confused, how is it possible that Apple has not planned this type of scenario. I'm confused. It seems that these type of matter are dependant on some individuals working on Apple team - their professionalim, character and mood.

1