New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Apple binary rejected because of "Username cannot be empty" #2537
Comments
@shawnlauzon - Are you using aws-amplify package only, or aws-amplify-angular as well? |
Both:
|
@shawnlauzon - Ok but you made your own authentication component? |
No I didn't; this is the authentication component that comes with aws-amplify-angular.
|
The popup is from |
Ah, I see. We will investigate. |
@shawnlauzon Did you manage to get any console output or anything for this error? |
I sent this to Apple:
And without asking for anything else, they approved the app! I'm guessing that they tested the app manually and it worked, but they didn't send us any details. So I'm not sure what else to do with this issue. I'm happy to keep it open if you're still looking into it. |
@shawnlauzon thanks for the update! We have also been unable to reproduce this. So we'll close this for now if something comes up with it again please feel free to reopen it. |
@shawnlauzon You sir are a life saver! I've been struggling with Apple on this issue for months. I was unable to reproduce it and they kept kicking it back. I was just able to reproduce the problem on my iOS device by copying the username and password to notepad and copy pasting into the login page of my screen. It was 100% reproducible. I was in fact running into two problems... I didn't know they were directly attributed to this "bug"?
Copying and pasting seems to cause problems. I can duplicate this problem on my Android build as well, so it doesn't seem to be related to ios specifically, but the Amplify Authentication framework/gui somehow. I'm posting this here in the hopes it helps someone else. I also have another thread I'll cross reference. |
OMG I can't believe someone had the same issue!! I just got reject 3 times due to this issue!!! I used the default amplify-authenticator component without modifying anything, and I still couldn't reproduce the issue.. Thank you so much! I'm going to reply to them now. |
They just approved my app one day after I told them it was a copy-paste problem! Thank you all! |
I have this same issue. I keep getting rejected as well. Even after telling them not to copy/paste |
@9dnsb I think just tell them not to copy/paste they probably ignore it. Instead, let them know that the issue is not related to your app but it’s their internal testing tool’s issue. And let them know that you can't find any information about how they do the copy/paste in the guide so you can't reproduce the issue. Take a look at shawnlauzon's reply, I think it's perfect. I mentioned all his points in my reply, and they approved it quickly. (From "In Review" to "Ready for Sale" in 5 minutes). |
I struggled with this for WAY too long using Ionic/Angular ... Sharing my final solution ...
I put AuthFix in my amplify-authenticator tag like so ....
|
This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs. Looking for a help forum? We recommend joining the Amplify Community Discord server |
Describe the bug
I have an app that uses AWS Amplify within the Ionic framework. I have submitted it to the Apple Store, and they have rejected it because the service returns "Username cannot be empty" even though the fields are set. Screenshots are below.
Unfortunately I cannot reproduce this behaviour through web or through a simulator or through a device. Does anyone have any idea what could be causing this?
To Reproduce
As I stated, I haven't been able to reproduce this myself :(
Expected behavior
If the username is not entered, then this error should be displayed. Otherwise, do not display this error.
Screenshots
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
You can turn on the debug mode to provide more info for us by setting window.LOG_LEVEL = 'DEBUG'; in your app.
The text was updated successfully, but these errors were encountered: