Hi @Claude31 Thank you for the reply, Yes the review team said "While we notice that your app is intended for iPhone, it should be fully functional on iPad." And for the bug case, we are unable to reproduce the bug that they mentioned. They said the login button on the login page loads for a bit while submitting the form then stays unresponsive. We tested on several iPad simulators to find out the bug, but in our case there was no bug.

Hi @Claude31 Thank you for the reply, Yes the review team said "While we notice that your app is intended for iPhone, it should be fully functional on iPad." And for the bug case, we are unable to reproduce the bug that they mentioned. They said the login button on the login page loads for a bit while submitting the form then stays unresponsive. We tested on several iPad simulators to find out the bug, but in our case there was no bug.

Hi @Claude31 Thank you for the reply, Yes the review team said "While we notice that your app is intended for iPhone, it should be fully functional on iPad." And for the bag case, we are unable to reproduce the bag that they mentioned. They said the login button on the login page loads for a bit while submitting the form then stays unresponsive. We tested on several iPad simulators to find out the bag, but in our case there was no bag.

Sorry for the 3 consecutive replies, I never noticed it as there was some technical issue while posting the reply. Anyway we got reply from apple review team they said the issue is also occuring on their iPhone as well, This helped us narrow things down, and after some deeper debugging, we discovered the problem was related to Firebase token generation failing silently on certain Apple review devices.

Because our app sends the Firebase device token to the server during login, a failure to generate that token ends up sending a placeholder value ("@") instead. Our backend sees this as invalid and returns a 403, which causes the login flow to hang - exactly what the review team described.

What’s confusing is that we can’t reproduce this behavior on any of our test devices (iPhones or iPads). It seems to be happening only on their end, possibly due to stricter APNs/Firebase configurations, review environment limitations, or permission handling during testing.

Hi @App Review I contacted app store review team and they provided further bug details and the issue is sorted now. Thank you very much.