Avoid these AWS Amplify mistakes! ✋

Andrei,

My name is Mike, and I’m a Solutions Architect on the AWS Amplify team. On behalf of the team, I wanted to reach out to thank you for sharing your experience with Amplify. It’s always refreshing to have a look at Amplify from the perspective of someone new to the framework. And you raise some really good, constructive criticisms as well.

We’re still working through your feedback, but I wanted to provide a quick update regarding the bug/documentation inconsistency you discovered with respect to providing custom themes to the withAuthenticator HOC: I was able to reproduce the issue this morning and submit a fix. That PR, here (github.com/aws-amplify/amplify-js/pull/7925), is now merged, if you want to check it out, and should be included in the next release.

Long story short, the documentation above (demonstrating use of an object as the second param to withAuthenticator) accurately reflects the intended function signature—unfortunately, as you noted, the implementation is broken. As it stands, the theme property is essentially ignored. The fix above corrects that. And, once, merged, theming should work as expected (i.e., as outlined in the documentation).

I am sorry that your first experience with Amplify didn’t go as smoothly as either you or I would have liked. That said, thank you, again, for the feedback! Please know that it doesn’t go unnoticed. I very much look forward to hearing more about your Amplify experiences going forward.

Welcome to the community!

Best, Mike

P.S. Feel free to hit me up in our Discord (discord.gg/SkHJ4zqb)!