[MUSIC PLAYING]
FRANK VAN PUFFELEN: Welcome to Firebase Release Notes
for June, where we'll look at updates from the past month.
And we have some very interesting deep dives today,
so let's dig in right away.
The Firebase Command Line Interface
recently added support for more regions to more features.
First off, the CLI can now emulate
Cloud Functions in all us-central1 and europe-west1
regions, instead of just the default ones.
We also added asia-southeast1 as a valid Realtime Database
location.
And finally, we added europe-central2 to the Firebase
extensions template so that any new extensions you create
can also run it in this region.
And keep in mind, CLI releases come with native binaries,
so you can quickly get started by using the native installer
for Windows, Mac, and Linux.
If you develop for iOS or other Apple platforms,
you're probably aware of the Codable API.
By implementing the Codable protocol,
you can make your data types compatible
with external representations, which
is great for encoding and decoding
data from, say, a database.
As teammate Peter says, friends don't
let friends map their data manually.
Use a Codable instead.
Well, thanks to GitHub user mortonbekditlevsen,
we now have preliminary Codable support for the Realtime
Database in our iOS SDK.
This means that instead of writing your own code to map
between JSON properties in the database
and fields in your data types, you
can now implement a Codable once and then leave it to the SDK
to do the mapping for you.
To get the support, upgrade to version 8.1
or later over to Firebase SDK for iOS
and add the new Firebase database Swift dash beta
product in Swift Package Manager.
A few weeks ago, GitHub user alexsilvacodes
alerted us that their iOS app was rejected from the App Store
because a Firebase SDK in it used an API method that
was made private in iOS 15 and then started
being flagged since WWDC.
Well, thanks to their clear report,
we were able to fix the issue and publish an updated
version of the iOS SDKs on the same day that it was reported.
So thank you, Alex, for helping us fix this issue.
And for everyone else, keep on reporting
the issues you encounter, because as you can see,
it really matters.
Crashlytics makes reporting crashes
in your apps easy and seamless.
The Crashlytics SDK now can be used in all Apple operating
systems, so you can continue to develop with confidence.
In December, we released full support
for Apple Silicon Macs running iOS and Mac OS
apps, either natively or through the Rosetta 2 emulation layer.
And now, thanks to GitHub user jostster,
the Crashlytics SDK also runs from watchOS,
reporting common crashes and non-fatal issues there, too.
And to make it easier to focus on crashes
from these platforms, we're expanding the device
filtering options in the Firebase console.
Check the blog post I linked below for more details.
With the Firebase Emulator Suite,
you can develop apps locally on your development machine
without ever hitting your real Firebase
projects on the server.
Now this affects many of our APIs and most of our SDKs,
and we just made an update to the Go Admin SDK.
When your app uses Firebase Authentication in the Emulator,
you get a slightly different ID token
than ones issued by the real Firebase Auth Service.
Now, the Emulator does this deliberately,
so that its ID tokens are never accepted by a Firebase service
in production.
However, what if you have a use case where
you need to send the ID tokens to your own backend servers
and then verify them there with the Admin SDK?
Well, with this release, you can now
run the Admin Go SDK in Emulator mode,
by setting an emulator URL as an environment variable.
And in this mode, the Admin SDK is then
able to verify the emulator-issued ID tokens,
so you can locally test your application use case
end to end.
And even better, the Admin SDK doesn't even
need to download public keys to verify in this scenario,
so that it, too, can work completely offline.
Those were all the updates we have time for today.
If you liked it, give this video Like,
or Subscribe to the channel below.
My name is Frank, or Puf, and I'll
see you on a future episode on Firebase Release Notes."
[MUSIC PLAYING]