You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When enabling the self-destruct in the Notesnook client, i'm expecting to only be able to see the monograph once.
Tho after multiple access, i can still see the monograph.
Steps to reproduce the problem
Create a note (if not done already)
Publish it as a monograph
Make it Self-Destruct (creating the monograph or updating it with self destruct is the same)
Access it
Try again and you should still be able to access it, and in the client, the monograph is still present.
Version
Client v3.1.1 | Monograph v1.2.4
Platform/OS
Windows, Linux
Relevant log output
The text was updated successfully, but these errors were encountered:
Also, the root cause of the issue is that, inside the monograph post component, you directly call api.notesnook.com instead of using the self-hosted host for the /view endpoint.
Since the self-hosted API is waiting for /view to be called to remove the monograph, and the monograph call it on api.notesnook.com, then the monograph will never be deleted on access.
What happened?
When enabling the self-destruct in the Notesnook client, i'm expecting to only be able to see the monograph once.
Tho after multiple access, i can still see the monograph.
Steps to reproduce the problem
Version
Client v3.1.1 | Monograph v1.2.4
Platform/OS
Windows, Linux
Relevant log output
The text was updated successfully, but these errors were encountered: