-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Investigate V2 Encoding not deploying correctly on Staging #646
Comments
@humansinstitute, Please assign me? |
@humansinstitute, assign me? |
Hi @humansinstitute, Please check the demo: https://www.loom.com/share/1a55f79efdf04e06a187f3cba30b7f9c Currently, the V2 pubkey is correctly encoded on the staging side. Once the changes are merged and a new release is made (e.g., https://github.com/stakwork/sphinx-tribes-frontend/releases/tag/v0.0.34 ), you can verify that the V2 pubkey is reflected correctly here: https://people-test.sphinx.chat/p/csk586cnuku6oosk3r90/workspaces Hi @elraphty, could you please release the new changes on the frontend side? |
@elraphty Am I missing something here? The PR is merged and correctly built, but when I test in staging I don't see this behaivour. Everything other bug where we've merged into main is then rebuilt and deployed on staging for testing without needing to be tagged as a release, so I don't see why this would be different? Two question:
|
Okay, I will take a look. |
@humansinstitute, I tested this on people-test.sphinx.chat, it worked for V2 users |
Follow up integration bug on #635
On Merge of #640 the Testing on Staging is failing as the copied pubkey is being returned with the corrupt style of encoding.
The text was updated successfully, but these errors were encountered: