Skip to content

fix(auth, web): correct use of underlying useEmulator API, sync not async #5171

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

Merged
merged 1 commit into from
Mar 8, 2021
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -348,7 +348,7 @@ class FirebaseAuthWeb extends FirebaseAuthPlatform {
// The generic platform interface is with host and port split to
// centralize logic between android/ios native, but web takes the
// origin as a single string
await _webAuth!.useEmulator('http://$host:$port');
_webAuth!.useEmulator('http://$host:$port');
} catch (e) {
throw getFirebaseAuthException(e);
}
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -615,8 +615,7 @@ class Auth extends JsObjectWrapper<auth_interop.AuthJsImpl> {
///
/// Note: must be called before using auth methods, do not use
/// with production credentials as local connections are unencrypted
Future useEmulator(String origin) =>
handleThenable(jsObject.useEmulator(origin));
void useEmulator(String origin) => jsObject.useEmulator(origin);

/// Sets the current language to the default device/browser preference.
void useDeviceLanguage() => jsObject.useDeviceLanguage();
Expand Down