Fix initial decryption of mute lists when using amber #1177
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
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.
In the Account.kt theres a init that tries to decrypt the mute list but amber is only initialized after the creation of the accountviewmodel in the AccountScreen.kt file.
We should run what is inside the account init after setting up the external signer.
For now I just initialized the content resolver when creating the external signer
Related to this:
nostr:nevent1qqs92dtd0nue54u4887vytqmlfumgnr8ktsqq9d2wat0nsjhl7tc6jqpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygqxsv6t97wdtcctgwrxcjmqh5cjxn3fh6duzxcx4uphasjgma8h4cpsgqqqqqqsn585z8