{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/5e585a88cf30461f9902d9b12fc8e802\" frameborder=\"0\" width=\"2560\" height=\"1920\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1920,"width":2560,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1920,"thumbnail_width":2560,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/5e585a88cf30461f9902d9b12fc8e802-00001.gif","duration":161.89999999999995,"title":"Google Auth Problem: Troubleshooting and Recommendations","description":"Hey there, this is Tyler with member stack. I've looked into the Google auth problem you'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."}