A public link was created for a room, and an email requested.
Email was input and magic link received, but opening the magic link leads to this crash report.
Then after submitting the crash report Heybase asks for the client to log into Heybase (the client does not have a Heybase account so would be confused at this point.
Hi Heybase any news on this, it is pretty essential to have this other links can be shared without us knowing who is looking at them. Thanks
New bulk API’s are under work along with improved custom domain implementation there are lots of new feature lined up for the next release. Request you to hold on till next week. Thanks!
Hi
I eventually chased using the online chat because I was not getting a response for weeks.
The response was the normal answer where you are just so grateful you finally got a reply, but it doesn’t help- ‘it doesn’t work how we want, we are changing the way this works…’
My issue with this response is that if they already knew that public links isn’t working as it should, they should tell their clients and disable it. And, also let us know when it will be returning. Rather than wait for it to be an issue for our clients.
I like the simplicity of Heybase, my clients do as well.
But, I really really wish the regression/QA testing was better, their communication was a lot better. Because of this, I have to test every link before it is sent out which means I can only use it for a handful of clients at the moment.
Hi @Mazumdr, I accept we haven’t been able to respond properly and magic links have been a long-standing issue we tried to get it resolved without our API vendor multiple times but are finally doing it in-house to fix it for good.
