starred/Bark

Fork 0

mirror of https://github.com/Finb/Bark.git synced 2026-04-25 22:15:52 +03:00

[GH-ISSUE #297] Feature Request: Add Message Recall Functionality #259

New issue

Closed

opened 2026-03-03 11:42:00 +03:00 by kerem · 8 comments

kerem commented

2026-03-03 11:42:00 +03:00

Owner

Originally created by @Konano on GitHub (Apr 3, 2025).
Original GitHub issue: https://github.com/Finb/Bark/issues/297

Some instant messaging apps automatically retract read message notifications.

I also want to retract some outdated notification messages. As far as I know, the current feature does not support this operation. Is it possible to develop this new feature?

Originally created by @Konano on GitHub (Apr 3, 2025). Original GitHub issue: https://github.com/Finb/Bark/issues/297 Some instant messaging apps automatically retract read message notifications. I also want to retract some outdated notification messages. As far as I know, the current feature does not support this operation. Is it possible to develop this new feature?

kerem

2026-03-03 11:42:00 +03:00

closed this issue
added the
in progress
label

kerem commented

2026-03-03 11:42:01 +03:00

Author

Owner

@Finb commented on GitHub (Jul 17, 2025):

1903797c8d

Added id parameter: using the same ID will update the previously sent notification.
Added delete parameter: when set to “1” and used with id, it will delete the corresponding notification.

@Finb commented on GitHub (Jul 17, 2025): 1903797c8d48c9ad7f1c9a0e178a3a138726b3f1 Added `id` parameter: using the same ID will update the previously sent notification. Added `delete` parameter: when set to “`1`” and used with id, it will delete the corresponding notification.

kerem commented

2026-03-03 11:42:01 +03:00

Author

Owner

@Konano commented on GitHub (Jul 17, 2025):

Soooooooooooooo happy to see this issue resolved! Thank you, @Finb!

@Konano commented on GitHub (Jul 17, 2025): Soooooooooooooo happy to see this issue resolved! Thank you, @Finb!

kerem commented

2026-03-03 11:42:01 +03:00

Author

Owner

@Konano commented on GitHub (Jul 23, 2025):

An unintended behavior has been found: when a notification is deleted, the id it was using is invalid and cannot be used again.

@Konano commented on GitHub (Jul 23, 2025): An unintended behavior has been found: when a notification is deleted, the `id` it was using is invalid and cannot be used again.

kerem commented

2026-03-03 11:42:02 +03:00

Author

Owner

@Finb commented on GitHub (Jul 24, 2025):

Can’t repro, works fine for me.

@Finb commented on GitHub (Jul 24, 2025): Can’t repro, works fine for me.

kerem commented

2026-03-03 11:42:02 +03:00

Author

Owner

@Konano commented on GitHub (Jul 24, 2025):

Couldn't reproduce it again, I guess my previous code was wrong. Now it works as expected.

@Konano commented on GitHub (Jul 24, 2025): Couldn't reproduce it again, I guess my previous code was wrong. Now it works as expected.

kerem commented

2026-03-03 11:42:02 +03:00

Author

Owner

@Konano commented on GitHub (Dec 4, 2025):

It seems this feature is not working again. The server returned {"code":200,"message":"success","timestamp":1764858722}, but the client did not receive any recall notification.

@Konano commented on GitHub (Dec 4, 2025): It seems this feature is not working again. The server returned `{"code":200,"message":"success","timestamp":1764858722}`, but the client did not receive any recall notification.

kerem commented

2026-03-03 11:42:02 +03:00

Author

Owner

@Konano commented on GitHub (Dec 4, 2025):

It seems this feature is not working again. The server returned {"code":200,"message":"success","timestamp":1764858722}, but the client did not receive any recall notification.

Then I found that simply opening Bark manually solved the problem. It was likely because I hadn't opened Bark since restarting iOS, which caused the issue.

@Konano commented on GitHub (Dec 4, 2025): > It seems this feature is not working again. The server returned `{"code":200,"message":"success","timestamp":1764858722}`, but the client did not receive any recall notification. Then I found that simply opening Bark manually solved the problem. It was likely because I hadn't opened Bark since restarting iOS, which caused the issue.

kerem commented

2026-03-03 11:42:02 +03:00

Author

Owner

@sunvc commented on GitHub (Dec 4, 2025):

It seems this feature is not working again. The server returned {"code":200,"message":"success","timestamp":1764858722}, but the client did not receive any recall notification.这项功能似乎又出问题了。服务器返回了 {"code":200,"message":"success","timestamp":1764858722} ，但客户端没有收到任何召回通知。

Then I found that simply opening Bark manually solved the problem. It was likely because I hadn't opened Bark since restarting iOS, which caused the issue.后来我发现，只要手动打开 Bark 就能解决问题。这很可能是因为我重启 iOS 后就没打开过 Bark，而重启 iOS 正是导致问题的原因。

It is necessary to enable the app backend refresh

@sunvc commented on GitHub (Dec 4, 2025): > > It seems this feature is not working again. The server returned `{"code":200,"message":"success","timestamp":1764858722}`, but the client did not receive any recall notification.这项功能似乎又出问题了。服务器返回了 `{"code":200,"message":"success","timestamp":1764858722}` ，但客户端没有收到任何召回通知。 > > Then I found that simply opening Bark manually solved the problem. It was likely because I hadn't opened Bark since restarting iOS, which caused the issue.后来我发现，只要手动打开 Bark 就能解决问题。这很可能是因为我重启 iOS 后就没打开过 Bark，而重启 iOS 正是导致问题的原因。 It is necessary to enable the app backend refresh