pull down to refresh

Does this happen when you do post or when you visit the post page?

Can’t post at all.

Strange. I could post my ramblings just yesterday.

I tried to use this drop down menu but it sent me to the error page

reply
117 sats \ 16 replies \ @sox 5 Jan

I've been trying to reproduce this for the most part of the last 30 minutes, but can't. Now a sad thing is that the copy button doesn't work in the something went wrong page, and I'm gonna get it fixed, so I think it could be something simple as cache acting up.

Can you verify if this happens also on

  • PWA
  • Desktop
  • Incognito navigation

If all of these work, with your account, then it may very well be a cache issue and you can clear website data on Settings -> Apps -> Safari. Make sure to target stacker.news when clearing data!

reply

I get the same problem on desktop and mobile. Clearing site cache didn't seem to change anything.

reply
2143 sats \ 7 replies \ @optimism 5 Jan

Do you have muted territories?

reply
100 sats \ 5 replies \ @sox 5 Jan

This is gold! Muted territories insert objects in the subs array, this is the culprit.

I'll open a GitHub issue right away, thank you so much!

reply

Of course! And thank you! 🙏

(Edit: confirmed that this is it)

reply
100 sats \ 3 replies \ @sox 5 Jan

Yep! I didn't consider muted territories at all (I don't mute anyone), here's the issue https://github.com/stackernews/stacker.news/issues/2743

reply

I mute because wild-west. I could reconsider that again and flip the strategy (no mute, only downzap, wild-west off) with all the recent changes, but people seem to be more offended by downzap than by mute.

Bingo

reply
11 sats \ 0 replies \ @sox 5 Jan

Got it, I'll keep investigating 🫡

reply

I can repro. Error log:

Error: Minified React error #31; visit https://reactjs.org/docs/error-decoder.html?invariant=31&args[]=object%20with%20keys%20%7Blabel%2C%20items%7D for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    at lE (https://a.stacker.news/_next/static/chunks/framework-c6ee5607585ef091.js:1:47898)
    at o (https://a.stacker.news/_next/static/chunks/framework-c6ee5607585ef091.js:1:52891)
    at uu (https://a.stacker.news/_next/static/chunks/framework-c6ee5607585ef091.js:1:71158)
    at i (https://a.stacker.news/_next/static/chunks/framework-c6ee5607585ef091.js:1:121283)
    at oO (https://a.stacker.news/_next/static/chunks/framework-c6ee5607585ef091.js:1:99117)
    at https://a.stacker.news/_next/static/chunks/framework-c6ee5607585ef091.js:1:98984
    at oF (https://a.stacker.news/_next/static/chunks/framework-c6ee5607585ef091.js:1:98991)
    at ox (https://a.stacker.news/_next/static/chunks/framework-c6ee5607585ef091.js:1:95743)
    at oC (https://a.stacker.news/_next/static/chunks/framework-c6ee5607585ef091.js:1:96132)
    at r8 (https://a.stacker.news/_next/static/chunks/framework-c6ee5607585ef091.js:1:44909)

[..]

The error #31 is:

Objects are not valid as a React child (found: object with keys {label, items}). If you meant to render a collection of children, use an array instead.
reply

How did you manage to reproduce the error message?

reply

On Brave Desktop the error button works (and otherwise I could have gone into dev console)

reply

I see!

Thanks for finding a solution to my problem!

reply

The solution is pending, just helping triage.

reply

Thanks for trying so hard and taking such a valiant interest in my case!

I cleared my cache but still couldn’t post. I now see that muted territories are the problem.

Thank you again

reply