clarification about sandboxed Play services updates
This commit is contained in:
parent
1f74dd6e1d
commit
0a9d17b102
@ -590,7 +590,7 @@
|
||||
<p>Changes since the 2025032500 release:</p>
|
||||
|
||||
<ul>
|
||||
<li>Sandboxed Google Play compatibility layer: remove StatsManager from hidden services and replace that approach with stubbing out all of the methods since Play services recently introduced new code using it that's missing a null check and triggers a null pointer exception which has blocked us from pushing out the newer versions of Play services beyond our Alpha channel</li>
|
||||
<li>Sandboxed Google Play compatibility layer: remove StatsManager from hidden services and replace that approach with stubbing out all of the methods since Play services recently introduced new code using it that's missing a null check and triggers a null pointer exception which has blocked us from pushing out the newer versions of Play services beyond our App Store's Alpha channel</li>
|
||||
<li>Network Location: switch to making at most a single request to the service per position estimation by requesting up to 40 Wi-Fi APs at once</li>
|
||||
<li>Network Location: optimize making requests to the service for Wi-Fi AP data</li>
|
||||
<li>Network Location: optimize Rust JNI bindings to the point that it no longer causes a noticeable overhead without introducing unsafe code (it could be optimized further with unsafe code to cache more JNI binding work but the difference is insignificant so we don't plan to do it)</li>
|
||||
|
Loading…
x
Reference in New Issue
Block a user