撰写的memos会消失

[billzhen870]

在打开app直接写memos时基本一定会出现这种情况，并且写好的memos直接消失。但是写好复制好，然后消失后重新粘贴就能撰写成功。 不知道是打开app第一次写的问题还是撰写时间太长的原因。不知道能不能实现报错不清空撰写栏。 除了这个bug之外的app体验很好！比手机登陆网页好用很多。我也是为了使用这个 app特地放弃了巨魔后了的16升级到17😂

[Issues-translate-bot]

Issue is not in English. It has been translated automatically.

---

Title: The memos written by me will disappear

This situation will basically occur when you open the app and write memos directly, and the written memos disappear directly. But after writing, copy, then disappear and then re-paste, the writing will be successful. I don’t know if it’s a problem with opening the app for the first time or because it takes too long to write. I don’t know if it is possible to report an error without clearing the writing column. Apart from this bug, the app experience is great! It’s much easier to use than logging in to the website via mobile phone. I also gave up trolls specifically to use this app and upgraded from 16 to 17😂

[mudkipme]

Please provide your Memos server version and the server logs when you save your memos.

[billzhen870]

Please provide your Memos server version and the server logs when you save your memos.

Apologies, I haven't been writing memos for a while, so I wasn't able to reproduce the issue until now. However, after trying again today, the error occurred once more. My memos server version is 0.22.3, but based on this issue, it might actually be version 0.22.2 (I'm not sure). The server logs with the error are as follows:

2024/10/15 18:19:01 WARN Failed to dispatch memo created webhook err="receive error code sent by webhook server, code 200, msg: success\ngithub.com/usememos/memos/plugin/webhook.Post\n\tgithub.com/usememos/memos/plugin/webhook/webhook.go:61\ngithub.com/usememos/memos/server/router/api/v1.(*APIV1Service).dispatchMemoRelatedWebhook\n\tgithub.com/usememos/memos/server/router/api/v1/memo_service.go:1122\ngithub.com/usememos/memos/server/router/api/v1.(*APIV1Service).DispatchMemoCreatedWebhook\n\tgithub.com/usememos/memos/server/router/api/v1/memo_service.go:1091\ngithub.com/usememos/memos/server/router/api/v1.(*APIV1Service).CreateMemo\n\tgithub.com/usememos/memos/server/router/api/v1/memo_service.go:80\ngithub.com/usememos/memos/proto/gen/api/v1._MemoService_CreateMemo_Handler.func1\n\tgithub.com/usememos/memos/proto/gen/api/v1/memo_service_grpc.pb.go:447\ngithub.com/usememos/memos/server/router/api/v1.(*GRPCAuthInterceptor).AuthenticationInterceptor\n\tgithub.com/usememos/memos/server/router/api/v1/acl.go:80\ngoogle.golang.org/grpc.getChainUnaryHandler.func1\n\tgoogle.golang.org/grpc@v1.65.0/server.go:1196\ngithub.com/grpc-ecosystem/go-grpc-middleware/recovery.UnaryServerInterceptor.func1\n\tgithub.com/grpc-ecosystem/go-grpc-middleware@v1.4.0/recovery/interceptors.go:33\ngoogle.golang.org/grpc.getChainUnaryHandler.func1\n\tgoogle.golang.org/grpc@v1.65.0/server.go:1196\ngithub.com/usememos/memos/server/router/api/v1.(*LoggerInterceptor).LoggerInterceptor\n\tgithub.com/usememos/memos/server/router/api/v1/logger_interceptor.go:20\ngoogle.golang.org/grpc.NewServer.chainUnaryServerInterceptors.chainUnaryInterceptors.func1\n\tgoogle.golang.org/grpc@v1.65.0/server.go:1187\ngithub.com/usememos/memos/proto/gen/api/v1._MemoService_CreateMemo_Handler\n\tgithub.com/usememos/memos/proto/gen/api/v1/memo_service_grpc.pb.go:449\ngoogle.golang.org/grpc.(*Server).processUnaryRPC\n\tgoogle.golang.org/grpc@v1.65.0/server.go:1379\ngoogle.golang.org/grpc.(*Server).handleStream\n\tgoogle.golang.org/grpc@v1.65.0/server.go:1790\ngoogle.golang.org/grpc.(*Server).serveStreams.func2.1\n\tgoogle.golang.org/grpc@v1.65.0/server.go:1029\nruntime.goexit\n\truntime/asm_amd64.s:1695\nfailed to post webhook\ngithub.com/usememos/memos/server/router/api/v1.(*APIV1Service).dispatchMemoRelatedWebhook\n\tgithub.com/usememos/memos/server/router/api/v1/memo_service.go:1123\ngithub.com/usememos/memos/server/router/api/v1.(*APIV1Service).DispatchMemoCreatedWebhook\n\tgithub.com/usememos/memos/server/router/api/v1/memo_service.go:1091\ngithub.com/usememos/memos/server/router/api/v1.(*APIV1Service).CreateMemo\n\tgithub.com/usememos/memos/server/router/api/v1/memo_service.go:80\ngithub.com/usememos/memos/proto/gen/api/v1._MemoService_CreateMemo_Handler.func1\n\tgithub.com/usememos/memos/proto/gen/api/v1/memo_service_grpc.pb.go:447\ngithub.com/usememos/memos/server/router/api/v1.(*GRPCAuthInterceptor).AuthenticationInterceptor\n\tgithub.com/usememos/memos/server/router/api/v1/acl.go:80\ngoogle.golang.org/grpc.getChainUnaryHandler.func1\n\tgoogle.golang.org/grpc@v1.65.0/server.go:1196\ngithub.com/grpc-ecosystem/go-grpc-middleware/recovery.UnaryServerInterceptor.func1\n\tgithub.com/grpc-ecosystem/go-grpc-middleware@v1.4.0/recovery/interceptors.go:33\ngoogle.golang.org/grpc.getChainUnaryHandler.func1\n\tgoogle.golang.org/grpc@v1.65.0/server.go:1196\ngithub.com/usememos/memos/server/router/api/v1.(*LoggerInterceptor).LoggerInterceptor\n\tgithub.com/usememos/memos/server/router/api/v1/logger_interceptor.go:20\ngoogle.golang.org/grpc.NewServer.chainUnaryServerInterceptors.chainUnaryInterceptors.func1\n\tgoogle.golang.org/grpc@v1.65.0/server.go:1187\ngithub.com/usememos/memos/proto/gen/api/v1._MemoService_CreateMemo_Handler\n\tgithub.com/usememos/memos/proto/gen/api/v1/memo_service_grpc.pb.go:449\ngoogle.golang.org/grpc.(*Server).processUnaryRPC\n\tgoogle.golang.org/grpc@v1.65.0/server.go:1379\ngoogle.golang.org/grpc.(*Server).handleStream\n\tgoogle.golang.org/grpc@v1.65.0/server.go:1790\ngoogle.golang.org/grpc.(*Server).serveStreams.func2.1\n\tgoogle.golang.org/grpc@v1.65.0/server.go:1029\nruntime.goexit\n\truntime/asm_amd64.s:1695"
2024/10/15 18:19:01 INFO OK method=/memos.api.v1.MemoService/CreateMemo
2024/10/15 18:19:13 INFO OK method=/memos.api.v1.MemoService/ListMemos

However, aside from encountering an error, I would prefer to resolve the issue without clearing the writing area. Usually, after the error occurs, uploading immediately can result in a successful upload. Lastly, I would like to express my sincere thanks to you and your project again, which has been incredibly helpful to me.