You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setting custom claims (via Auth.setCustomUserClaims) only allows the user to pass in a Map<String, String>, while the JS equivalent (as well as the official Node.js SDK) allows any value. Isn't it meant to be Map<String, dynamic>? I'm trying to set it to {"isAdmin": true}, but it's not allowed.
The text was updated successfully, but these errors were encountered:
I could write a PR with the type change, if that would be helpful. There really shouldn't be any errors caused by this, since it is a more relaxed type of the original, and the JS functions are okay with that type anyway.
Setting custom claims (via
Auth.setCustomUserClaims
) only allows the user to pass in aMap<String, String>
, while the JS equivalent (as well as the official Node.js SDK) allows any value. Isn't it meant to beMap<String, dynamic>
? I'm trying to set it to{"isAdmin": true}
, but it's not allowed.The text was updated successfully, but these errors were encountered: