Status stuck at Public (unsent) forever - Mastodon as ActivityPub type

[DetroitLibertyPenguin]

I haven't figured out a recipe to reproduce on demand, but frequently I will get status update that never actually get posted to the server.

When it gets in this state nothing seems to fix it. I have tried selecting resend, selecting either of the spinning arrow icons, the sync with intent button and edit to click send again.

About the only thing that works is edit/copy/discard/new status/paste/send.

[yvolk]

Hi @DetroitLibertyPenguin ! Please try to "Resend" the "unsent" note, and if it is still "unsent", after a a couple of minutes please go to the top menu -> "Commands in a queue" and lookup the command:

Post "Text of your note...

There will be some clue on a cause of the error.

E.g. in the below Error description we see "... Host unreachable"

[DetroitLibertyPenguin]

I've tried a few times since you replied. Maybe I'm blind but I'm not seeing that message at all

I tried changing the logging setting to debug and then the app restarted and took a lot longer to load, and do anything else but still no luck on seeing the POST error.

Sent from my Smartphone please dismiss no-so-smart-typos

---

From: Yuri Volkov @.> Sent: Sunday, May 22, 2022 12:14:29 PM To: andstatus/andstatus @.> Cc: DetroitLibertyPenguin @.>; Mention @.> Subject: Re: [andstatus/andstatus] =0AStatus stuck at Public (unsent) forever (Issue #556)

Hi @DetroitLibertyPenguinhttps://github.com/DetroitLibertyPenguin ! Please try to "Resend" the "unsent" note, and if it is still "unsent", after a a couple of minutes please go to the top menu -> "Commands in a queue" and lookup the command:

Post "Text of your note...

• there will be some clue on a cause of the error.

— Reply to this email directly, view it on GitHubhttps://github.com/andstatus/andstatus/issues/556#issuecomment-1133928045, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APSNIJZHG2LGNTVQQTW6GSTVLJMOLANCNFSM5WSEPYSQ. You are receiving this because you were mentioned.Message ID: @.***>

E; , foregroundPublic at ActivityPub, Created 40 seconds ago, executed: 1, last: 40 seconds ago, error: Hard Public at ActivityPub, Status code: NOT_FOUND; hard; Timeline was not found at [] , CommandData: {command: fetch-timeline, id: 1654225028935, foreground, account: @.***/ActivityPub, Timeline: {ActivityPub, type: public, id: 80}, created:just now, CommandResult: {error: Hard}}

[DetroitLibertyPenguin]

E; ,.txt

[DetroitLibertyPenguin]

Inadvertently closed

[DetroitLibertyPenguin]

System bug report bugreport-a51tfn-SP1A.210812.016-2022-06-02-22-58-41.tar.gz

[yvolk]

Hi @DetroitLibertyPenguin. Thank you for the info. I looked into attached "E.txt" and noticed there: "account: fuat2mb@theres.life/ActivityPub" meaning that you added your account at the https://theres.life Mastodon instance as if it is ActivityPub instance (technically: AndStatus connects to theres.life using "ActivityPub Client to Server protocol") . This could be a cause of the strange behavior. "Mastodon" instances were known to have only partial "ActivityPub" implementation. I.e. something was known to be missed or to fail at a server side. Technical details and long discussion is here: https://github.com/andstatus/andstatus/issues/499 Your story tells that Mastodon developers made some progress since my previous review, but I didn't investigate this recently. Will do this.

Meanwhile, as an alternative, please try to add another account to the AndStatus app, maybe even the same "fuat2mb@theres.life" but this time choose "Mastodon" type of social network. I think the "Mastodon type" account will work more predictably since this was tested a lot.

Note: AndStatus allows you to have two "fuat2mb@theres.life" in different "Types of social networks", but you may easily get confused, which is which. And of course, you will have message duplications... So if you get confused, you can Remove "ActivityPub" type of account and leave only "Mastodon" type.

[DetroitLibertyPenguin]

I apologize for the delay in my response.

FYI, I did change remove that account and re-add it as Mastodon as you recommend, but I did not see any signifcant change regarding my UNSENT forever issue. I did see far fewer options using that option than my other mastodon account that I have connected as ActivityPub. It appears I have seen similar failures on my other accounts, Pump.io, GNU Social, It does seem to improve if I stay on that screen until the "loading" spinner quits spinning in the lower left corner, rather than posting/replying and then quickly shifting to another screen on the app or out of the app.

[DetroitLibertyPenguin]

I went to attach additional screen shots, and i noticed that it doesn't seem like there are any such failures on the account I use most often (Friendica) since I deleted it and readded it as GNU Social rather than Activity Pub (the instance I am on supports both Ostatus and AP) for what that is worth

[yvolk]

@DetroitLibertyPenguin Some time ago I fixed background syncing so that can improve posting also... see https://github.com/andstatus/andstatus/issues/557 Regarding resending old "unsent" note: If you don't see "Resend" in the note's context menu. try "Edit" and send again from the Editor...