fix: resolve Cloudflare token verification loop in Auto-Image #216
+180
−82
Conversation
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
- Add token validation before each batch - Cache WASM token to prevent repeated verifications - Wait for token regeneration to complete before retrying - Use network interception for WASM token capture - Add x-pawtect-variant header to API requests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This is a PR to fix the issue with the Auto-Image mode. It was constantly retrying the Cloudflare bot validation thingy without much success. I also fixed the x-pawtect-variant header, which had changed. Now it does paint properly
Please note that I had never used the plugin before, so I don't have a baseline on how the experience used to be. It seems a bit rough, after sending the request to paint, an error pops up and you go into offline mode, I haven't been able to determine why, because the paint request goes through just fine. But since it did go through, after waiting a few seconds, when the map updates, you can see your painting. The charges seem to not update by themselves but nothing an F5 can't fix.
I haven't tested with multiple accounts as I only have one myself.