Tweet Token, format error
I'm not sure if it is a bug, or how I have the settings so far:
Bug description (Required)
Describe the bug you found I found a bug in Blocklet "tweet token"
Replicate the bug (Required)
Describe in detail how to reproduce the bug
- Login to "tweet token" Blocklet
- In the dashboard menu>tweet token, try to establish rules for an event of 10 ABT × 10 recipients. With and without the checkbox at the bottom or different values. I receive an error that says "SERVER return data FORMAT error".
Exception behavior (Optional)
Describe what is wrong with the program Error message
Desired behavior (Optional)
Describe what the normal behavior of the program should bbe It seemed like it was trying to bring up the delegation screen after setting a rule.
Screenshot or error message (Optional)
Post a screenshot of the error or console output
Possible solutions (Optional)
Describe the possible solutions
??
Useful links (Optional)
Provide useful links about the bug so that we can easily reproduce it
11 条回复
Also does it for NFT
May I ask what version of Tweet Token you are using, and what platform and version of DID Wallet you are using?
Currently:
Tweet Token 0.3.14
Android DID Wallet 4.19.1
I don't remember if there was an update to Tweet Token since my original post.
Okay, we will verify it.
I tried Tweet Token 0.3.14 & Android DID Wallet 4.19.1, and did not reproduce the issue mentioned above. Please try again when you have time.
within did wallet is where the error shows, when trying from firefox it still acts the same (not establishing a rule) but doesnt show the server format error message in did wallet:
This is too strange, I have prepared an environment exactly like yours, except for the network. I can complete the entire process within the DID Wallet's built-in browser. Can you try changing to a different network environment?
All I can do is switch to cellular, which I get the same result.
The tweet token app is installed on a serverless space from the launcher - not my self-hosted development environment
I was able to get the message sign request to show.
I had the access control for tweet token set to invited users only, when I switched it to accessible to all - the message sign request finally showed.
Have you already completed all the processes, right?
I hadnt finished the sign request yet as im still getting together what it is i want to use it for, which is nfts instead of tokens (still need to set up the factory).
the message request did show that it wouldve been 100abt for the example i gave, which makes sense - 10×10=100
I hadnt been getting the message sign request previously, but after switching the access control within configuration for tweet token to accessible to all - the message request was allowed through.