<?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/3fbfa155c1b848a4a2b19d29873b715d&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/3fbfa155c1b848a4a2b19d29873b715d-182f743c7c1c99da.gif</thumbnail_url><duration>588.733333</duration><title>Debugging Privacy Rules and User Access Issues in Our Application 🔍</title><description>In this video, I discuss a frustrating bug related to privacy rules that prevents the current user&apos;s data from displaying correctly after logging in. Despite the user being logged in, the interested user field remains empty, indicating that the privacy rules are not being re-evaluated as expected. I explore potential workarounds, but none seem to resolve the issue, highlighting a significant security concern. I urge viewers to pay attention to these privacy settings and consider the implications for user access. Please let me know if you have any insights or suggestions on how to address this problem.</description></oembed>