Fixes for issues with feed loading on initial app start #940
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@micahmo Once this is merged in, I'll deploy a second pre-release version to get this change out as quickly as possible as this issue might be affecting a lot of users on varying instances! |
micahmo
approved these changes
Dec 1, 2023
|
@hjiangsu It looks like I can no longer open a community from the post card metadata. I'm running release at the moment and not near my PC so I don't have any more details. Can you repro? screen-20231202-113851.mp4 |
|
Found it and creating a PR for it now! Thanks for letting me know |
3 tasks
|
@micahmo Just released a patch for this issue on 0.2.7-3 |
|
That was fast, thanks! Works now! 😊 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Description
This PR hopefully fixes the issue where the feed does not load when first starting the app. The main change here was to reduce potential extraneous API calls to the instance when Thunder initially starts up.
I don't think there are any side-effects that are caused by these changes, but will have to keep an eye out for any further problems. (Tested switching between anonymous and logged in accounts)
Issue Being Fixed
Issue Number: N/A
Screenshots / Recordings
Checklist
semanticLabels where applicable for accessibility?