# First attempt to access log always fails

**URL:** <https://community.ultraloq.com/t/first-attempt-to-access-log-always-fails/8772>\
**Category:** ULTRALOQ Smart Lock\
**Created:** [March 3, 2024, 4:18pm UTC](https://community.ultraloq.com/t/first-attempt-to-access-log-always-fails/8772 "2024-03-03T16:18:53Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gary2](https://avatars.discourse-cdn.com/v4/letter/g/49beb7/32.png) [@Gary2](https://community.ultraloq.com/u/Gary2)\
**Post date:** [March 3, 2024, 4:18pm UTC](https://community.ultraloq.com/t/first-attempt-to-access-log-always-fails/8772/1 "2024-03-03T16:18:53Z")

</div>

I have a u-bolt pro. When I use the app and choose the device (the only one) and choose “Log” it always reports “empty log”. If I go back to the status page, and try press “log” once more I see all the entries. Does anyone else experience this?

Firmware 02.26.0020  
App v2.1.17

---

<div class="post-metadata">

**Author:** ![Kiki](https://sea2.discourse-cdn.com/flex020/user_avatar/community.ultraloq.com/kiki/32/1917_2.png) [@Kiki](https://community.ultraloq.com/u/Kiki)\
**Post date:** [March 4, 2024, 8:59am UTC](https://community.ultraloq.com/t/first-attempt-to-access-log-always-fails/8772/2 "2024-03-04T08:59:08Z")

</div>

Thank you for your feedback. Our team will get back to you via email to resolve the issue. Please keep an eye on your inbox.🙂

---

<div class="post-metadata">

**Author:** ![Moshe](https://avatars.discourse-cdn.com/v4/letter/m/b9e5f3/32.png) [@Moshe](https://community.ultraloq.com/u/Moshe)\
**Post date:** [March 4, 2024, 3:19pm UTC](https://community.ultraloq.com/t/first-attempt-to-access-log-always-fails/8772/3 "2024-03-04T15:19:15Z")

</div>

Always. Every time I check the log it’s empty. If I refresh (pull down and let go) then the log shows up.

---

<div class="post-metadata">

**Author:** ![Taninbaum](https://avatars.discourse-cdn.com/v4/letter/t/b487fb/32.png) [@Taninbaum](https://community.ultraloq.com/u/Taninbaum)\
**Post date:** [March 4, 2024, 9:58pm UTC](https://community.ultraloq.com/t/first-attempt-to-access-log-always-fails/8772/4 "2024-03-04T21:58:40Z")

</div>

Me too. Always need to pull it down.

---

<div class="post-metadata">

**Author:** ![Greg6](https://avatars.discourse-cdn.com/v4/letter/g/d78d45/32.png) [@Greg6](https://community.ultraloq.com/u/Greg6)\
**Post date:** [March 6, 2024, 2:22pm UTC](https://community.ultraloq.com/t/first-attempt-to-access-log-always-fails/8772/5 "2024-03-06T14:22:03Z")

</div>

Yes, that seems to be expected.

---

<div class="post-metadata">

**Author:** ![Heirtzler](https://sea2.discourse-cdn.com/flex020/user_avatar/community.ultraloq.com/heirtzler/32/1508_2.png) [@Heirtzler](https://community.ultraloq.com/u/Heirtzler)\
**Post date:** [March 6, 2024, 3:44pm UTC](https://community.ultraloq.com/t/first-attempt-to-access-log-always-fails/8772/6 "2024-03-06T15:44:07Z")

</div>

I’m not sure “expected” is the word I’d use, but I rather unsurprising.

My app shows an empty log and if I pull it down it posts a dialog “lock connection failed” and power cycling the bridge does not help but restarting the app does.

There are so many app bugs it’s alpha. If you take an action too quickly the app gets confused. You can leave a screen and a second later the app shows you the screen you already left. Stuff like that.

The app does not manage its internal state and often shows incorrect info for a moment and then corrects itself. For what it’s worth, because I have built this sort of application a lot, this hints at a messy and chaotic code base, ie fix one bug and cause another scenario.