<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/6c94b46642624de6b125fd702ca7a56d&quot; frameborder=&quot;0&quot; width=&quot;1664&quot; height=&quot;1248&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1248</height><width>1664</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1248</thumbnail_height><thumbnail_width>1664</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/6c94b46642624de6b125fd702ca7a56d-00001.gif</thumbnail_url><duration>152.39999999999995</duration><title>Potential Bug in Custom Domain Implementation</title><description>In this video, I discuss a potential bug in our custom domain implementation. I demonstrate how when we navigate to our custom domain, we do not see the &quot;Sign in with Google&quot; button, which is causing inconvenience for our employees. Additionally, I show that even after logging in, the session is not carried over to the custom domain. I would like to find a solution to this issue without having to change all the integrated links.</description></oembed>