FAQ
What about a blog post about that?

Just to keep things "officially".

:)

2015-08-27 10:57 GMT-03:00 Kato Richardson <wulf@firebase.com>:
Laurentiu, thanks for the ping. It's only 6a here, so it'll be a few hours
until the engineers roll into the office and start firing things up. I'll
make sure they update the thread with the latest and greatest.

☃, Kato
On Thu, Aug 27, 2015 at 5:39 AM, Laurentiu Morariu wrote:

Hi there. Is this definitely happening today? As I was doing some testing
and I don't see any changes.

On Monday, August 17, 2015 at 5:28:52 PM UTC+1, Kato Richardson wrote:

Hi again,

We've moved the date of the change for email/password and anonymous
authentication to Thursday, August 27th. This is primarily to help
developers trying to release apps to the Apple store.

To reiterate, this will not affect existing user uids, just newly
created users after the release date. This will also not affect OAuth
providers. We'll send out a separate notice before that release.

☃, Kato
On Thursday, August 6, 2015 at 11:57:20 AM UTC-7, Kato Richardson wrote:

Hi Folks! Hope you're all having a blast building apps on Firebase.


The format of the auth UIDs generated by Firebase will be changing on
Monday, August 17th. We’ll be changing from an incremental integer to a
UUID <https://en.wikipedia.org/wiki/Universally_unique_identifier>
(universally unique identifier).

This will affect the email/password and anonymous providers on the
17th, and be extended to the OAuth providers (i.e. GitHub, Facebook,
Twitter, and Google) at some undetermined time in the future. If you’re
manipulating or parsing UIDs in any way, you’ll want to update your code
and security rules before the 17th.

When new users get created after this date, you may notice that,
instead of a string like <provider>:<number>, new accounts will have a
UID assigned that looks more like f47ac10b-58cc-4372-a567-0e02b2c3d479.
You should keep in mind that the contents of these strings are an
implementation detail and not intended to be meaningful. They are only
guaranteed to be unique and unchanging for a given user.

To reiterate, this will affect new UIDs created with createUser(), but
will not affect any of your existing users’ UIDs.

Below is a quick checklist to ensure your code won't be affected by
this change. If you have additional questions, reply here or reach out to
support@firebase.com.
auth.uid.contains() or auth.uid.replace()

If you are checking auth.uid begins with, contains, or doing any sort
of matching on the contents of this string, this will break. Particularly,
if you are doing a replace on ‘:’, this will almost certainly break.

Alternatives: Use auth.provider to obtain the provider name. If you
need to access the OAuth id (e.g. facebook ID) then you can
programmatically store this in your data when a user authenticates (e.g.
authData.facebook.id where authData is the return value from any
authWith*() call).
auth.uid.length

The length of new UID strings may be radically different than existing
UIDs created before this change. If you are checking to ensure the length
is greater than zero, that should continue to work, or could simply be
replaced by a boolean (e.g. “.read”: “auth.uid”).
auth.uid == x

If you are checking that the auth.uid matches another value stored in
the data, this should continue to work perfectly. Existing users’ UIDs will
not change and newly minted UIDs will have a different format, but still
work with this approach.
How to test this change

If you want to test your existing code against the new format, this
gist <https://gist.github.com/katowulf/d533678c9196f3d92ef4>
illustrates how to create a mock authentication token that will resemble
the new UUID strings.

Have a great day,

Kato

--
You received this message because you are subscribed to the Google Groups
"Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to firebase-talk+unsubscribe@googlegroups.com.
To post to this group, send email to firebase-talk@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/firebase-talk/1cb736d1-d327-4ad3-ac51-1ea4ff1db726%40googlegroups.com
<https://groups.google.com/d/msgid/firebase-talk/1cb736d1-d327-4ad3-ac51-1ea4ff1db726%40googlegroups.com?utm_medium=email&utm_source=footer>
.

For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to firebase-talk+unsubscribe@googlegroups.com.
To post to this group, send email to firebase-talk@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/firebase-talk/CADypTEY-HzPM9Yhoa8xefk9T5U5Bv%3D68LA_qf88jg5wkCWkfFA%40mail.gmail.com
<https://groups.google.com/d/msgid/firebase-talk/CADypTEY-HzPM9Yhoa8xefk9T5U5Bv%3D68LA_qf88jg5wkCWkfFA%40mail.gmail.com?utm_medium=email&utm_source=footer>
.

For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-talk+unsubscribe@googlegroups.com.
To post to this group, send email to firebase-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/CAPUi1p1E5i4jX%3DJXSzNybFOXuX%3D64Z8_6HwK8QcgJi0sWPqrdw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Search Discussions

Discussion Posts

Previous

Follow ups

Related Discussions

People

Translate

site design / logo © 2021 Grokbase