Handle current Anisette v3 provisioning states - #6
Open
Xare123 wants to merge 3 commits into
Open
Conversation
This was referenced Jul 25, 2026
Closed
This file contains hidden or 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.
Summary
Update the remote Anisette v3 client for the current SideStore provisioning protocol.
EndProvisioningError, instead of failing JSON deserialization.Why
The previous result enum accepted only four variants. Current SideStore servers can return states such as
Wait,CurrentlyEndingProvisioning, andEndProvisioningError. That produced anunknown variant EndProvisioningErrorfailure during OpenBubbles setup before 2FA.Validation
git diff --checkpasses.Standalone Rust unit tests were not executed on the Windows host because the MSVC linker was unavailable. The added parsing tests should run in the repository's Rust CI.