Logs are not Populating on iOS App

Logs are not populating for me at all. I have several users set up and have unlocked using various codes, using the app and manually but nothing is logged.

image
Here is an animated video showing that the logs only display the latest action. It also doesn’t update the time the new action occurred. At the bottom you can see it fails to get the logs.

1 Like

Did the log issue still persist?

1 Like

Yes, it’s still only logging one event and saying failed to get logs.

1 Like

@Frank I pulled the app logs, see below. You can share this with the app developer. It appears that it’s just updating the logs with the same events because it happens so quickly, but the logic wasn’t implemented correctly because all logs get overwritten.

I can see that the app requests the data and gets a 201 for the latest message. So grabbing the latest message is working, but the logic to store the events in the app is not working correctly.

Jul  5 10:55:00 Erudo U-tec[13237] <Notice>: NewMessage topic = utec/lock/U-BOLT-WIFI/68:67:25:08:4D:D1/whatever/accept  mid=1
Jul  5 10:55:00 Erudo U-tec[13237] <Notice>: message 48 -- {length = 48, bytes = 0x7f1500cf 000a0000 00010000 00e8abca ... 00000000 0000004b }
Jul  5 10:55:00 Erudo U-tec[13237] <Notice>: mqtt mac = 68:67:25:08:4D:D1 data= {length = 48, bytes = 0x7f1500cf 000a0000 00010000 00e8abca ... 00000000 0000004b }
Jul  5 10:55:00 Erudo U-tec[13237] <Notice>: check sum OK
Jul  5 10:55:00 Erudo U-tec[13237] <Notice>: check sum OK
Jul  5 10:55:00
 Erudo U-tec(libnetwork.dylib)[13237] <Notice>: [C14] event: client:data_stall @70.478s
Jul  5 10:55:00 Erudo symptomsd(SymptomEvaluator)[120] <Notice>: Stall symptom detail: (symName/procName/ePid/ifIndex/interfaceType/stallType/endpoint/isFgOrBg): SYMPTOM_LIBNETCORE_DATA_STALL/U-tec/13237/12/1/1/<private>/1
Jul  5 10:55:00 Erudo symptomsd(SymptomEvaluator)[120] <Notice>: Stall symptom SYMPTOM_LIBNETCORE_DATA_STALL: U-tec has preexisting endpoint match for stall type (1) within time range on interface type (1), updating timestamp: <private>

thanks, appreciated very much

2 Likes

Same usaue. Been told, since january, new app will fix it. Of course no such thing happened. Fyi, im on samsung (android) .

I unlock everyday but only showed log for year 2021

Having the same issue, but log also showing locks/unlocks that never occurred