5
submitted
2 weeks ago* (last edited 2 weeks ago)
by
i_am_not_a_robot@feddit.uk
to
c/lemmyconnect@lemmy.ca
Bug Report
Describe the issue: Upvoting comments that are from a crosspost give the following error:
Error: AppError(ErrorType.unknown): An unexpected error occurred: LemmyApiException: couldnt find comment
Steps to reproduce:
- Visit https://reddthat.com/post/58720048
- Scroll under the Cartoons section
- Try to upvote any comment (I haven't tried replying, might be the same issue)
Note: selecting cartoons from the crosspost list and then upvoting is working as expected. Also upvoting a comment on the original post (below comics) whilst on that page is working. Might be a caching issue?
Device Information
- App Version: 1.0.374 (374)
- Platform: android
- OS Version: V2UI35.43-12-4
Modified Settings
The following settings have been changed from defaults:
- isSwipeEnabled:
false(default:true) - isNotificationEnabled:
1(default:0) - isCommentBarAlwaysShowing:
true(default:false) - shouldAlwaysOpenInDefaultBrowser:
true(default:false) - alwaysShowInstance:
true(default:false) - alwaysTrustDomains:
true(default:false) - commentTextStyle:
bodyMedium(default:bodyLarge) - postTitleTextStyle:
titleLarge(default:titleMedium) - customColoursPreset:
3(default:0) - enableCommentNavigator:
true(default:false) - isTopBarFixed:
true(default:false) - isDraftsEnabled:
false(default:true) - shouldAlwaysDisplayAvatars:
true(default:false) - colourSurface:
4281021498(default:null) - defaultRoute:
/community?postListingType=Subscribed&hint=Frontpage(default:null) - defaultPostSort:
New(default:Active) - applyNsfwInCommunities:
false(default:true) - postActions:
[comment, save](default:[comment, save, none, crosspost]) - shouldCombineMarkdownImages:
false(default:true) - shouldRemembercommentPosition:
false(default:true) - shouldUseProfileBanner:
true(default:false) - shouldLoadAllComments:
true(default:false) - textSizeMultiplier:
1.1(default:1.0)
Hi, thanks for the report! I just pushed an update (375) to beta which should resolve this issue. It was failing to load the comments locally and falling back to loading them directly from the remote instance.