I like using Lens, but almost every single time I get comments on a Lens post, I can’t view them. It’ll say “3 comments” or something and then when I tap on it, it says “No comments yet.” Sometimes posting more Lenses fixes it, or just coming back later, but sometimes it does that until the Lens post expires, in which case I’ve had Patron comments (maybe questions!) that I just never got to see.
It’s happening to me right now, in fact. Here are some screenshots:
It would be GREAT if this could be fixed, obviously, and secondarily it would also be great to be able to access Lens on a desktop browser, because then at least I’d be able to check in a secondary place if the first place is somehow not working.
Just wanted to share an update. It happened again and this time I missed five comments — no idea what they said, who sent them, or if they included any questions. I sent in a support ticket and was basically told that Lens is broken and they are in the process of completely overhauling the feature “this year.”
While I’m glad this is being worked on, I personally feel that comments on Lens posts should be disabled until this feature is fixed (and said so in response to my support ticket.) To me, it feels dishonest to allow my Patrons to leave comments when there is no guarantee I will be able to see them. I will likely stop using Lens until the feature is fixed.
I’ve been dealing with this exact same issue for months! It’s incredibly frustrating for all the reasons you gave, missing comments/questions and feeling a disconnect with our patrons when they are paying us to be able to communicate with us. I agree that they should disable comments until the issue is fixed. I’d hate for anyone to think we are ignoring them or something, ya know?
One more update! I discovered that Patrons can view the comments even when I can’t, so my workaround right now is to check Lens comments on my partner’s or mom’s Patreon account. Of course this is not helpful if you don’t have easy access to someone who pledges to your Patreon, but this is the ONLY workaround I’ve been able to find!
Thank you so much for raising this issue. I can confirm that this is indeed a bug, which is when a feature or site does not respond or behave as it was intended. Unfortunately, I don’t have a hard date for when it will be resolved, but know that it is being investigated.
Since our engineering team is aware of the issue, I will be closing this thread, but please feel free to start a new one if need be, or you can always reach out to our support team here.
