Skip to content
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

KittyPunch and PunchSwap must be listed as one word, not two Eg: “KittyPunch” not “Kitty Punch”... #587

Open
instabug bot opened this issue Nov 25, 2024 · 0 comments
Assignees

Comments

@instabug
Copy link

instabug bot commented Nov 25, 2024

📋 Bug Details

KittyPunch and PunchSwap must be listed as one word, not two

Eg: “KittyPunch” not “Kitty Punch”

key value
Reported At 2024-11-25 18:18:25 UTC
Email [email protected]
Categories Suggest an improvement
App Version 2.2.11 (7)
Session Duration 33
Device iPhone 13 Pro, iOS 17.6.1
Display 390x844 (@3x)
Location Vancouver, Canada (en-CA)

👉 View Full Bug Report on Instabug 👈


📉 Session Profiler

Here is what the app was doing right before the bug was reported:

Key Value
CPU Load 3.4%
Used Memory 2.4% - 0.07/3.0 GB
Used Storage 96.9% - 230.92/238.3 GB
Connectivity WiFi
Battery 85% - unplugged
Orientation portrait

Find all the changes that happened in the parameters mentioned above during the last 60 seconds before the bug was reported here: 👉 View Full Session Profiler 👈


🔎 Logs

Network Log

This bug report has 4 failed (4xx, 5xx or no response) requests. Here are some of them:

18:14:27 400 POST https://rest-mainnet.onflow.org/v1/scripts?block_height=sealed
18:14:27 400 POST https://rest-mainnet.onflow.org/v1/scripts?block_height=sealed
18:14:27 400 POST https://rest-mainnet.onflow.org/v1/scripts?block_height=sealed

Find all the network requests with more details about each one, its duration, method, URL, headers, and response here: 👉 View Detailed Network Logs 👈


📷 Images

image attachment


⚠️ Looking for More Details?

  1. User Steps: enable them to get the most out of your plan and see every action users take before reporting a bug.
  2. User Events: start capturing custom User Events to send them along with each report. Find all the details in the docs.
  3. Instabug Log: start adding Instabug logs to see them right inside each report you receive. Find all the details in the docs.
  4. Console Log: when enabled you will see them right inside each report you receive. Find all the details in the docs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant