title: Google Sign In (GSI) after 10 seconds throws a 401
body: <p>The behavior can be seen on both our <a href="https://hireproof.io/" rel="nofollow noreferrer">website</a>, and <a href="https://slack.com/" rel="nofollow noreferrer">slack</a>.  It looks like it tries to hit this endpoint:</p>
  <pre><code>curl 'https://play.google.com/log?format=json&amp;hasfast=true&amp;authuser=0' \
    -H 'authority: play.google.com' \
    -H 'accept: */*' \
    -H 'accept-language: en-US,en;q=0.9' \
    -H 'authorization: SAPISIDHASH da3120fd2c8773cb248175715b41c00a9ffc7d3c' \
    -H 'content-type: application/x-www-form-urlencoded;charset=UTF-8' \
    -H 'origin: https://accounts.google.com' \
    -H 'sec-ch-ua: &quot;Chromium&quot;;v=&quot;104&quot;, &quot; Not A;Brand&quot;;v=&quot;99&quot;, &quot;Google Chrome&quot;;v=&quot;104&quot;' \
    -H 'sec-ch-ua-mobile: ?0' \
    -H 'sec-ch-ua-platform: &quot;macOS&quot;' \
    -H 'sec-fetch-dest: empty' \
    -H 'sec-fetch-mode: cors' \
    -H 'sec-fetch-site: same-site' \
    -H 'user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/104.0.0.0 Safari/537.36' \
    -H 'x-client-data: CI+2yQEIprbJAQjEtskBCKmdygEIlKHLAQikvMwBCNS8zAE=' \
    -H 'x-goog-authuser: 0' \
    --data-raw '[[1,null,null,null,null,null,null,null,null,null,[null,null,null,null,&quot;en&quot;]],1112,[[&quot;1662800548756&quot;,null,[],null,null,null,null,&quot;[\&quot;xpq/7NvyMfFVPEXdvMHbBA\&quot;,12,false,null,\&quot;178803201798-pfac5tu091grgjs5hu9a4djeor0vqrel.apps.googleusercontent.com\&quot;,\&quot;https://hireproof.io\&quot;,[2],null,null,null,null,null,null,5,null,null,null,[1,1,1,null,3,1,1]]&quot;,null,null,12,null,null,null,-7200,null,null,null,null,[],1,null,null,null,null,null,[]]],&quot;1662800558756&quot;,[]]' \
    --compressed
  </code></pre>
  <p>The play.google.com appears to be an android endpoint for logging.  This is not causing any issues other than an annoyance that it's causing console logging an error on production.  Has anyone seen this or know a fix?</p>