There is inconsistent behavior when AllowNewAccounts = false in the AuthProvider.Email UI between the old and new library versions.
While updating the library from version 8.x.x to 10.0.0-beta03, I encountered the following problem:
It seems that the new version of the library behaves quite differently regarding the "setAllowNewAccounts" option in AuthProvider.Email.
When using the old version, the sign-up button disappears when AllowNewAccounts is set to false.
When AllowNewAccounts is set to false using the new version of the library, the sign-up button remains visible but is always disabled. An ugly pop-up message appears as soon as the sign-in UI is displayed: "This button is currently disabled because new accounts are not allowed."
This message is not relevant to my app, which does not allow sign-up at all. It is especially problematic compared to the cleaner UI obtained with version 8.x.x of the library.

There is inconsistent behavior when AllowNewAccounts = false in the AuthProvider.Email UI between the old and new library versions.
While updating the library from version 8.x.x to 10.0.0-beta03, I encountered the following problem:
It seems that the new version of the library behaves quite differently regarding the "setAllowNewAccounts" option in AuthProvider.Email.
When using the old version, the sign-up button disappears when AllowNewAccounts is set to false.
When AllowNewAccounts is set to false using the new version of the library, the sign-up button remains visible but is always disabled. An ugly pop-up message appears as soon as the sign-in UI is displayed: "This button is currently disabled because new accounts are not allowed."
This message is not relevant to my app, which does not allow sign-up at all. It is especially problematic compared to the cleaner UI obtained with version 8.x.x of the library.