Bug Report
Happy new year!
Describe the issue:
Tapping the alternative crossposts links under a post is no longer working. “Cannot find post on <local instance> it may not have federated yet” (sorry, adding screenshots isn’t working for me currently for some reason)
However, if I expand the stacked posts from the feed and open from there they open fine (and the crossposts links are then working)
Steps to reproduce:
- Visit https://lemmy.zip/post/56121865 (a random post I was using to test)
- Click on the alternative crossposts
- I can’t check the open externally on these ones but a previous post I saw this issue on didn’t open externally either, so I think the external URL might be getting corrupted.
- Open one of the posts an alternative way. (searching for it manually should suffice)
- Go back to (1) and observe the error no longer appears.
Device Information
- App Version: 1.0.329 (329)
- Platform: android
- OS Version: V2UI35.43-12-4
Modified Settings
The following settings have been changed from defaults:
- isSwipeEnabled:
false(default:true) - isNotificationEnabled:
2(default:0) - isCommentBarAlwaysShowing:
true(default:false) - shouldAlwaysOpenInDefaultBrowser:
true(default:false) - alwaysShowInstance:
true(default:false) - alwaysTrustDomains:
true(default:false) - postTitleTextStyle:
titleLarge(default:titleMedium) - customColoursPreset:
3(default:0) - isTopBarFixed:
true(default:false) - isDraftsEnabled:
false(default:true) - shouldAlwaysDisplayAvatars:
true(default:false) - shouldHighlightNewComments:
true(default:false) - shouldStackDuplicatePosts:
true(default:false) - defaultRoute:
/community?postListingType=Subscribed&hint=Frontpage(default:null) - defaultPostSort:
New(default:Active) - applyNsfwInCommunities:
false(default:true) - postActions:
[](default:[]) - shouldCombineMarkdownImages:
false(default:true) - shouldRemembercommentPosition:
false(default:true) - shouldUseProfileBanner:
true(default:false) - shouldResolveOpenGraph:
true(default:false) - shouldLoadAllComments:
true(default:false)
Hi. This should be fixed in v331. Cheers!
Just to add, when I went to the example link, both methods to the cross-post worked fine for me. When I went to find a cross-posted post, there was just the one cross-post button and I got the same error. After opening the cross-post externally, copying the URL, and using the go to URL function, the error went away after that.



