WEBVTT

1
00:00:00.000 --> 00:00:03.760
OK, so now, this is the fun part.

2
00:00:03.760 --> 00:00:07.280
We're going to go in here, make sure I'm on the right project,

3
00:00:07.280 --> 00:00:08.320
and delete this.

4
00:00:11.840 --> 00:00:12.760
66.

5
00:00:12.760 --> 00:00:14.160
You were right.

6
00:00:14.160 --> 00:00:15.120
I thought I said 60.

7
00:00:15.120 --> 00:00:15.920
We were close.

8
00:00:15.920 --> 00:00:19.960
And then this is the most boring part of this entire thing.

9
00:00:19.960 --> 00:00:22.400
And this is, if someone's watching the replay,

10
00:00:22.400 --> 00:00:24.200
you can just fast forward all this.

11
00:00:24.200 --> 00:00:26.960
Because we're going to go in here,

12
00:00:26.960 --> 00:00:29.240
and we're going to say, hey, instead of going and using

13
00:00:29.240 --> 00:00:32.000
the local API token, I want you to go

14
00:00:32.000 --> 00:00:33.920
to the authenticated user.

15
00:00:33.920 --> 00:00:37.160
And the authenticated user looks and says,

16
00:00:37.160 --> 00:00:41.760
hey, what fields it makes available?

17
00:00:41.760 --> 00:00:43.800
So anyone who's authenticated has access

18
00:00:43.800 --> 00:00:47.520
to all of these fields now, under the authenticated user.

19
00:00:47.520 --> 00:00:50.920
And it's available, as long as you're signed in,

20
00:00:50.920 --> 00:00:52.840
as long as there is an authenticated user,

21
00:00:52.840 --> 00:00:54.960
you can access all of those fields.

22
00:00:54.960 --> 00:00:58.800
And there's our tribe token we created right there.

23
00:00:59.400 --> 00:01:02.240
We just fixed one of the bugs.

24
00:01:02.240 --> 00:01:04.680
And the only thing I want to show you from this standpoint,

25
00:01:04.680 --> 00:01:06.720
and I couldn't even do this after the call,

26
00:01:06.720 --> 00:01:09.360
is we now have to go the faster way.

27
00:01:09.360 --> 00:01:11.480
Instead of me clicking authenticated,

28
00:01:11.480 --> 00:01:14.880
click tribe token, you can copy this variable.

29
00:01:14.880 --> 00:01:18.920
And then when I go to the next one, and I click this,

30
00:01:18.920 --> 00:01:22.680
I just hit the paste, confirm.

31
00:01:22.680 --> 00:01:23.680
OK.

32
00:01:23.680 --> 00:01:25.880
And then this is actually a totally different problem

33
00:01:25.880 --> 00:01:29.080
it's having, which now that we've opened it,

34
00:01:29.080 --> 00:01:30.160
I'll come back to that one.

35
00:01:30.160 --> 00:01:32.440
But click on this.

36
00:01:32.440 --> 00:01:34.400
I'm going to actually just remove these.

37
00:01:34.400 --> 00:01:36.040
We don't use those anymore.

38
00:01:36.040 --> 00:01:38.920
And keep going.

39
00:01:38.920 --> 00:01:44.680
So token, click on it, paste, confirm, click out.

40
00:01:44.680 --> 00:01:47.560
Click up here, open, same thing.

41
00:01:47.560 --> 00:01:52.480
Just hit click, paste, confirm, close.

42
00:01:52.480 --> 00:01:55.640
And then, and so on and so forth.

43
00:01:56.400 --> 00:01:58.360
And the good thing about this is we reset,

44
00:01:58.360 --> 00:02:05.680
from a workflow standpoint, we reset all of the bugs.

45
00:02:05.680 --> 00:02:08.440
We spent time getting all those bugs down to zero.

46
00:02:08.440 --> 00:02:11.720
So I know for a fact that every single problem of these 62

47
00:02:11.720 --> 00:02:15.040
is related to that one token being changed.

48
00:02:15.040 --> 00:02:17.120
So that's why, at this point, it'll just

49
00:02:17.120 --> 00:02:18.920
take another 15, 20 minutes.

50
00:02:18.920 --> 00:02:20.720
I won't make you watch all of that.

51
00:02:20.720 --> 00:02:22.920
But I'll just click, literally just do this thing.

52
00:02:22.920 --> 00:02:25.120
I'll click on it here.

53
00:02:25.120 --> 00:02:27.160
We'll look at where there's an error.

54
00:02:27.160 --> 00:02:29.760
And this has removed field.

55
00:02:29.760 --> 00:02:31.400
So we can just remove this, because we

56
00:02:31.400 --> 00:02:32.800
don't need that anymore.

57
00:02:32.800 --> 00:02:35.720
And it's updating a local state here.

58
00:02:35.720 --> 00:02:37.520
And to be honest, we actually don't even

59
00:02:37.520 --> 00:02:41.440
need this anymore, because the user ID itself is actually

60
00:02:41.440 --> 00:02:43.480
going to be pulled as well.

61
00:02:43.480 --> 00:02:45.280
So that's the two things we want to delete.

62
00:02:45.280 --> 00:02:49.320
And it's got all these updating state stuff

63
00:02:49.320 --> 00:02:54.080
that we don't need anymore, because we don't use that.

64
00:02:54.080 --> 00:02:56.160
That's the same thing over here.

65
00:02:56.160 --> 00:02:57.360
It's got an update state.

66
00:02:57.360 --> 00:02:59.640
And all it's complaining about here is like, oh,

67
00:02:59.640 --> 00:03:03.360
we were asking it to put it into local state after this process.

68
00:03:03.360 --> 00:03:04.400
We don't need that.

69
00:03:04.400 --> 00:03:06.960
So the field has been removed, so we

70
00:03:06.960 --> 00:03:10.080
don't need to update it anymore.

71
00:03:10.080 --> 00:03:11.660
Those are the ones that are different.

72
00:03:11.660 --> 00:03:13.800
All of these other ones here are just

73
00:03:13.800 --> 00:03:17.760
that first piece, which was like pasting in the variable.

74
00:03:17.760 --> 00:03:19.760
I'm just going to skim through to see if there's anything out

75
00:03:19.760 --> 00:03:21.520
of the ordinary.

76
00:03:21.520 --> 00:03:23.980
And unfortunately, this is where it's a little bit manual.

77
00:03:23.980 --> 00:03:30.100
But it's not difficult. It's just a little painful

78
00:03:30.100 --> 00:03:31.460
to do it once.

79
00:03:31.460 --> 00:03:33.820
This is probably the biggest change we'll ever have,

80
00:03:33.820 --> 00:03:36.900
is actually where we're storing that token.

81
00:03:36.900 --> 00:03:40.620
Now it's part of the Firebase database,

82
00:03:40.620 --> 00:03:43.100
so we never need to mess with something

83
00:03:43.100 --> 00:03:45.380
this low level ever again.

84
00:03:45.380 --> 00:03:49.660
Most of it's going to be pretty simple changes.

85
00:03:49.660 --> 00:03:52.820
But this is where we just need additional manpower

86
00:03:52.820 --> 00:03:56.820
to help on this thing, just to have more people on it

87
00:03:56.820 --> 00:03:57.940
to help us.

88
00:03:57.940 --> 00:03:58.500
Definitely.

89
00:03:58.500 --> 00:03:59.820
Cool.

90
00:03:59.820 --> 00:04:00.300
Awesome.

91
00:04:00.300 --> 00:04:02.580
Were there any other questions there before we wrap this one

92
00:04:02.580 --> 00:04:03.220
up?

93
00:04:03.220 --> 00:04:07.100
Just wondering, when you're done with all the issue,

94
00:04:07.100 --> 00:04:12.420
so how is the app online?

95
00:04:12.420 --> 00:04:14.300
How does that work?

96
00:04:14.300 --> 00:04:15.420
How do we test it?

97
00:04:15.420 --> 00:04:16.260
Yeah.

98
00:04:16.260 --> 00:04:19.980
So you test it first?

99
00:04:19.980 --> 00:04:21.060
What's the process?

100
00:04:21.060 --> 00:04:25.100
Once you resolve all the issue, you just test it first.

101
00:04:25.100 --> 00:04:28.740
And then if it works well, you release the app.

102
00:04:28.740 --> 00:04:30.140
How does it work?

103
00:04:30.140 --> 00:04:30.900
OK, yeah.

104
00:04:30.900 --> 00:04:34.060
Let me stop this, and we'll do that in another.