<?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/5e585a88cf30461f9902d9b12fc8e802&quot; frameborder=&quot;0&quot; width=&quot;2560&quot; height=&quot;1920&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1920</height><width>2560</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1920</thumbnail_height><thumbnail_width>2560</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/5e585a88cf30461f9902d9b12fc8e802-00001.gif</thumbnail_url><duration>161.89999999999995</duration><title>Google Auth Problem: Troubleshooting and Recommendations</title><description>Hey there, this is Tyler with member stack. I&apos;ve looked into the Google auth problem you&apos;re experiencing on Login. It seems that some of the data being sent back after a user logs in with Google is improperly formatted on your website. I believe the issue lies in a new line break in the custom field, which contains special characters and escaped quotes. To resolve this, I recommend removing the slash N and, if necessary, dynamically building the script with the member ID on page load. If you have any questions, feel free to reach out.</description></oembed>