[MUST READ] Bug Reporting Guide

KrystalYee

BUG REPORTS.png

Help Us Improve hyperPad! 🛠️

Hey everyone!

Found a bug? Reporting it properly helps us fix issues faster and keep hyperPad running smoothly for everyone.

Follow this guide to submit an accurate and detailed bug report. 🧵

⚠️ Bug Report Rules

If a post doesn’t follow these rules, it may be removed to keep things organized.

✅ Be Clear and Concise – Keep your description short and straight to the point. No need for long explanations or guesses about the cause—just describe what’s happening. (If you have extra thoughts, use the “Additional Info” section or reply to your post later.)

✅ One Bug Per Post – If you find multiple bugs, make separate threads for each one. This helps us track and fix them properly.

✅ Double-Check Your Behaviours – Before posting, create a small test project to confirm the issue isn’t caused by how your behaviours are set up.

✅ Include a Sample Project (If Possible) – If you can, attach a simple test project that clearly shows the bug. This helps us diagnose the problem faster.

✅ Tell Us Where to Look – If you’re sharing a project file, specify where the bug happens. Mention the scene, object, or behaviour so we don’t have to dig through everything to find it.

✅ Found a Workaround? – If you’ve discovered a temporary fix, let us know! Add it in the “Additional Info” section or as a follow-up reply.

✅ Stay Engaged – If we ask for more info and don’t hear back from you for 30+ days, we’ll assume the bug is no longer an issue and move the post to the “Expired/Can’t Reproduce” section.

By sticking to this format, we can work together to fix bugs on our no code platform much faster! 🚀

Thanks for helping us improve your game dev on iPad experience! 😊

KrystalYee

How to Report a Bug 🐛🕵🏻‍♂️

Step 1: Check for Updates

Before reporting a bug, make sure you’re using the latest version of hyperPad. Updates often include bug fixes, so your issue might already be resolved.

Step 2: Gather Key Information

To help us understand and fix the bug, please include the following details in your report:

Device & OS Details:

iPad Model (e.g., iPad Pro 11” 2021)
iOS Version (e.g., iOS 17.2)
hyperPad Version: Found in the app under Settings > About

Bug Description:

Clearly explain the issue. What happened? What did you expect to happen?

Steps to Reproduce:

Provide a step-by-step guide on how to trigger the bug.

Example:

Open hyperPad and create a new project.
Add a new object and attach a behavior.
Run the game, and observe the crash.
Screenshots or Video (If Possible):
Visual evidence can help us identify the issue faster.

Project File (Optional but Helpful):

If the bug is project-specific, export and attach your project file for testing.

Step 3: Report the Bug

We recommend that you post it to the hyperPad Forum.

Post in the ""Bug Reports"" section with all gathered details.

KrystalYee

Example Bug Report 🐜

Title: Crash when duplicating objects with behaviors
Device: iPad Air 4 (2020)
iOS Version: 16.5
hyperPad Version: 1.30.2

Description: Whenever I duplicate an object with behaviors, hyperPad crashes unexpectedly. This happens consistently with specific behavior setups.

Steps to Reproduce:

Open an existing project or create a new one.
Add an object and attach a ""Move To"" behavior.
Duplicate the object multiple times.
hyperPad crashes after the 3rd duplication.
Attachments: [Video of the crash] [Project file]

KrystalYee

What Happens Next? 💭

Once reported, our team will:
1 - Review your report and attempt to reproduce the issue.
2 - Provide updates on the status of the bug fix in the forum or app update notes.
3 - Reach out if more details are needed.

Thank you for helping us improve your game dev on iPad experience with us! 🚀