Connect for Lemmy App

2661 readers

1 users here now

A community for the mobile app Connect for Lemmy.

Links

founded 2 years ago

MODERATORS

[email protected]

-1

Error:language_not_allowed (self.lemmyconnect)

submitted 1 year ago by RightHandOfIkaros to c/[email protected]

5 comments fedilink hide all child comments

I am getting kinda sick of constantly not being able to post comments on seemingly random posts due to this error.

The instance is English, the post title is English, and my comment is in English. I have even logged into my instance website to change the language settings to have both "Undetermined" and "English" selected, and that still doesn't work. Not all posts have this problem, and not even posts in just one community or instance. Seems like the error is completely random.

I have to imagine this is an error specific to Connect for Lemmy, since I don't get the same error if I comment from my web browser. It seems to come from Connect for Lemmy not having an option to set the comment language when posting? Can that be corrected please?

you are viewing a single comment's thread
view the rest of the comments

[–] RightHandOfIkaros 2 points 1 year ago (1 children)

Yes, I have, I said so in the post body above.

I tried to comment on a post through the Connect app- get the language not allowed error. Commenting through web browser lets me set the language when posting- set to English- comment gets posted.

It is 100% a problem with the application not having a dropdown when posting to select language. In all honesty, the language should be detected automatically, users should not be required to set and guess the language needed to comment. But thats a Lemmy issue, not a Connect one. For now, at least including the language setting for comments would suffice.

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago)

Sorry my bad, I should have read your entire post.

What I would suggest though is to log in on the web interface and select every language (including "undertermined"), if you haven't tried already. I'm pretty sure that's what I did.

Be sure to log out / in in Connect afterwards