There is a race condition in the root navigatior's initialization. It's possible that it's initialized a touch too late and SDK users who try to navigate to a conference end up stuck in the connecting screen because the navigator is null. This PR waits for it to be initilized by very unorthodox means, it's a horrible hack which we need to undo, but for that we need to break appart the inheritance relationship between App.{web,native}, AbstractApp and BaseApp because it's very inflexible. The flags are now initialized very early so the naviggator sees if the welcome page is enabled or not.master
|
||
28 | 28 |
|
29 | 29 |
|
30 | 30 |
|
31 |
|
|
32 |
|
|
33 |
|
|
34 |
|
|
35 |
|
|
36 | 31 |
|
37 | 32 |
|
38 | 33 |
|
|
||
100 | 95 |
|
101 | 96 |
|
102 | 97 |
|
98 |
|
|
99 |
|
|
100 |
|
|
101 |
|
|
103 | 102 |
|
104 | 103 |
|
105 | 104 |
|
106 | 105 |
|
107 | 106 |
|
108 |
|
|
109 |
|
|
107 |
|
|
108 |
|
|
109 |
|
|
110 |
|
|
111 |
|
|
112 |
|
|
113 |
|
|
114 |
|
|
115 |
|
|
116 |
|
|
117 |
|
|
118 |
|
|
119 |
|
|
120 |
|
|
121 |
|
|
122 |
|
|
110 | 123 |
|
111 | 124 |
|
112 | 125 |
|
|
||
1 |
|
|
2 |
|
|
3 |
|
|
4 |
|
|
5 |
|
|
6 |
|
|
7 |
|
|
8 |
|
|
9 |
|
|
10 |
|
|
11 |
|
|
12 |
|
|
13 |
|
|
14 |
|
|
15 |
|
|
16 |
|
|
17 |
|
|
18 |
|
|
19 |
|
|
20 |
|
|
21 |
|
|
22 |
|
|
||
8 | 8 |
|
9 | 9 |
|
10 | 10 |
|
11 |
|
|
12 |
|
|
11 | 13 |
|
|
||
1 |
|
|
||
1 | 1 |
|
2 | 2 |
|
3 |
|
|
3 |
|
|
4 | 4 |
|
5 | 5 |
|
6 | 6 |
|
7 |
|
|
7 | 8 |
|
8 | 9 |
|
9 | 10 |
|
|
||
23 | 24 |
|
24 | 25 |
|
25 | 26 |
|
27 |
|
|
28 |
|
|
29 |
|
|
30 |
|
|
31 |
|
|
26 | 32 |
|
27 | 33 |
|
28 | 34 |
|
|
||
30 | 36 |
|
31 | 37 |
|
32 | 38 |
|
33 |
|
|
39 |
|
|
34 | 40 |
|
35 | 41 |
|
42 |
|
|
43 |
|
|
44 |
|
|
45 |
|
|
46 |
|
|
47 |
|
|
36 | 48 |
|
37 | 49 |
|
38 | 50 |
|
39 | 51 |
|
52 |
|
|
40 | 53 |
|
41 | 54 |
|
42 | 55 |
|
|
||
86 | 99 |
|
87 | 100 |
|
88 | 101 |
|
89 |
|