Not upadting the permissions from the Permissions API call on init is causing the permissions cache to be filled from GUM resolve/reject logic only when there aren't any permissions updates. This may lead to unknown permission status when we can report the correct status from the initial permission API request.dev1
|
|
||
43 |
|
43 |
|
44 |
|
44 |
|
45 |
|
45 |
|
46 |
|
|
|
47 |
|
|
|
48 |
|
|
|
49 |
|
|
|
50 |
|
46 |
|
51 |
|
47 |
|
52 |
|
48 |
|
|
|
||
60 |
|
56 |
|
61 |
|
57 |
|
62 |
|
58 |
|
|
59 |
|
|
|
60 |
|
|
|
61 |
|
|
63 |
|
62 |
|
64 |
|
63 |
|
65 |
|
64 |
|
|
|
||
76 |
|
75 |
|
77 |
|
76 |
|
78 |
|
77 |
|
|
78 |
|
|
|
79 |
|
|
|
80 |
|
|
79 |
|
81 |
|
80 |
|
82 |
|
81 |
|
83 |
|
|
|
||
195 |
|
197 |
|
196 |
|
198 |
|
197 |
|
199 |
|
198 |
|
|
|
199 |
|
|
|
200 |
|
|
|
201 |
|
|
|
202 |
|
200 |
|
203 |
|
201 |
|
204 |
|
202 |
|