`useEmulator()` has been renamed to `connect<PackageName>Emulator()`

[mikehardy]

Alter auth (and perhaps other packages already converted v9 API) to new emulator APIs

It appears that the v9 APIs have moved from useEmulator to connect<PackageName>Emulator as an API convention, but I think only the database module is converted correctly at the moment

---

          `useEmulator()` has been renamed to `connectDatabaseEmulator()`. `getServerTime()` actually doesn't exist in the V9 API. I think that was left over from when I was copying over some functions from V8 (compat)

Originally posted by @exaby73 in https://github.com/invertase/react-native-firebase/pull/7136#discussion_r1295671691

[github-actions[bot]]

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

[exaby73]

Hey @mikehardy. What is the next steps for this? Let me know where I can help

[mikehardy]

Hey @exaby73 the next steps are to implement in the new API shape (connect<PackageName>Emulator() vs useEmulator) in the modular / v9 API space. Success criteria to close this issue are to do that and migrate our e2e test app calls to use them, while adding a deprecation note on the old useEmulator calls. I think that's it ?

[exaby73]

Could we make this an umbrella issue to track which packages have the new API and which don't? I'm thinking for the time being, we still use useEmulator under the hood while wrapping it with connect<PackageName>Emulator

[github-actions[bot]]

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

[cvincentcoleman]

I've been unable to connect firebase storage to my emulator that's running using useEmulator. Could this be related?

[mikehardy]

unlikely - we haven't done the work here yet, nevertheless our e2e suite uses emulator for all modules that support it (including storage) on current versions of firebase-tools and firebase-ios-sdk/firebase-android-sdk and it's working.

So, I suspect something else

[github-actions[bot]]

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

[exaby73]

Not stale

[github-actions[bot]]

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

[github-actions[bot]]

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

[github-actions[bot]]

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

[russellwheatley]

Marking this as something to fix for next breaking change.