<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>jackedupjim Tracker</title>
    <link>https://community.stadia.com/ysfdd67284/tracker</link>
    <description>jackedupjim Tracker</description>
    <pubDate>Mon, 16 Jan 2023 09:22:01 GMT</pubDate>
    <dc:date>2023-01-16T09:22:01Z</dc:date>
    <item>
      <title>Re: Family Sharing</title>
      <link>https://community.stadia.com/t5/Stadia-on-TV/Family-Sharing/m-p/57458#M1024</link>
      <description>&lt;P&gt;I think this is exactly the issue, why does an account need to be temporarily added to an android device to be able to add to chromecast?&lt;/P&gt;&lt;P&gt;Again, are there any improvements to usability planned?&lt;/P&gt;&lt;P&gt;This is totally broken since when you add a child account you need to verify it using the parent account and with two factor authentication you are unable to login to do this since the phone is in the context of the new child account.&amp;nbsp; It is a total mess!&lt;/P&gt;</description>
      <pubDate>Tue, 30 Mar 2021 18:07:21 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-TV/Family-Sharing/m-p/57458#M1024</guid>
      <dc:creator>jackedupjim</dc:creator>
      <dc:date>2021-03-30T18:07:21Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to Link Stadia Controller to Chrome</title>
      <link>https://community.stadia.com/t5/Stadia-on-Chrome/Unable-to-Link-Stadia-Controller-to-Chrome/m-p/50424#M3169</link>
      <description>&lt;P&gt;I've tried incognito and it seems to work the first time but if I choose to power of controller it won't reconnect.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Jan 2021 22:09:45 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-Chrome/Unable-to-Link-Stadia-Controller-to-Chrome/m-p/50424#M3169</guid>
      <dc:creator>jackedupjim</dc:creator>
      <dc:date>2021-01-11T22:09:45Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to Link Stadia Controller to Chrome</title>
      <link>https://community.stadia.com/t5/Stadia-on-Chrome/Unable-to-Link-Stadia-Controller-to-Chrome/m-p/50384#M3164</link>
      <description>&lt;P&gt;So far I've tried&lt;/P&gt;&lt;P&gt;1) Signing out / in&lt;BR /&gt;2) Hardware reset controller&lt;BR /&gt;3) Deleting&amp;nbsp;cookies in developer tools which results in a new link code but exactly the same issue.&lt;BR /&gt;4) Factory reset controller&lt;/P&gt;&lt;P&gt;I'm not sure what I can do now apart from send it back to Google.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Jan 2021 16:56:09 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-Chrome/Unable-to-Link-Stadia-Controller-to-Chrome/m-p/50384#M3164</guid>
      <dc:creator>jackedupjim</dc:creator>
      <dc:date>2021-01-11T16:56:09Z</dc:date>
    </item>
    <item>
      <title>Unable to Link Stadia Controller to Chrome</title>
      <link>https://community.stadia.com/t5/Stadia-on-Chrome/Unable-to-Link-Stadia-Controller-to-Chrome/m-p/50373#M3163</link>
      <description>&lt;P&gt;I have a stadia controller which has been previously setup with my Stadia account.&amp;nbsp; It works using the link code on the Android app and CCU.&lt;/P&gt;&lt;P&gt;When I try to connect to stadia.google.com in a chrome browser it buzzes twice, appears solid white as if it has connected.&amp;nbsp; The browser doesn't show anything connected and the controller powers off after a short while.&lt;/P&gt;&lt;P&gt;Anyone know how to fix this?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Jan 2021 14:53:32 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-Chrome/Unable-to-Link-Stadia-Controller-to-Chrome/m-p/50373#M3163</guid>
      <dc:creator>jackedupjim</dc:creator>
      <dc:date>2021-01-11T14:53:32Z</dc:date>
    </item>
  </channel>
</rss>

