CheckinWithXYZ - Encountered a weird bug - space key not allowed - meme version

Hello Hive Community Members,

A couple of months ago, I used to write posts about technical stuff I got involved with while contributing to Hive — but then I stopped.

Why?

Reason One: It requires a bit of time.
Reason Two: Since English isn't my first language, it takes even more time.

But on Sunday morning here in Bharat 🇮🇳, @ecoinstant suggested that putting this kind of work on-chain is a wonderful idea — and that we should lead by example. After a motivating and insightful conversation with him, I’ve decided to resume what I used to do. Thank you so much @ecoinstant.

---

Okay, let’s jump into today’s topic.

Space Key Not Working on iPhone for CheckinWithXYZ

@starkerz messaged me directly. There was a weird space issue.
I was like, really? That sounds impossible. 😅

I immediately launched the app locally — everything worked fine...
But that was on a desktop browser, not mobile.

So I opened the iOS Simulator. Still, everything worked just fine.

---

@starkerz: Can’t enter space — it’s a weird, annoying bug
@sagarkothari88: I can’t reproduce it — not a bug
@starkerz: Shares a link
@sagarkothari88: Still can’t reproduce it — not a bug
@starkerz: I literally sent you a screenshot and post

And I’m just in full denial mode 🤣

If I can’t reproduce the bug, it doesn’t exist. 😤

So I didn’t give it much attention — considered it a minor, low-priority issue.

---

How I Ended Up Reproducing It – Testing Before Release

I had added a filter feature for admins in CheckinWithXYZ.
Deployed it. Then, for some reason, I decided to test it myself on an actual iPhone.

Boom — the bug appeared.

And I was like: faaaaaaakkk.
It was an annoying, user-breaking bug.
If I were the user, I'd be complaining loudly.

Trying to stay calm, I told myself:

It’s fine. It’s fine. It’s fine.

Just expressing my feelings through emojis/memes here 😅

---

🕵️ Investigation Time

First step: Google it.

You might call me a noob for not using AI right away.
But honestly, for fixing bugs in production, I’m a little skeptical about AI answers.
Some things I still prefer doing the old-fashioned way — from experience.

Purple links — you know what that means.
I clicked all of them. Explored every possibility.

---

Attempt 1

I used the highest-voted answer from the first StackOverflow post.
Tested locally on desktop and iOS simulator. Worked like a charm.

Deployed it. Boom 💥 — entire site down.
Just a gray screen.

Time to panic.

---

Attempt 2

So I finally asked AI what could’ve gone wrong.
It gave answers — but again, who knows if they’re right?

Didn’t want another panic attack in production.
So I cross-verified answers on StackOverflow.

Then I realized I had more SingleChildScrollView instances than I thought.

For every instance, I applied this patch:

SingleChildScrollView(
  primary: false,
  child: _some_screen_element(),
)

Tested again on desktop, iOS simulator.
Everything worked. I deployed it.

---

But after deployment... it didn’t work.
I was like: fakkkk noooo.

Let’s panic again.

But this time I stopped and asked myself:

Did I test the correct version?

I always tell @starkerz to refresh and clear the cache.
But did I do that? Answer: NO.

Cleared the cache. Reloaded.
And boom — it worked!

Finally, that weird invisible bug that wrecked the app’s user experience... was fixed.

---

💬 Have You?

Have you ever faced a weird bug in your tech stack that made you question your life choices?
Please share — would love to hear!

---

📝 Final Note

Since English isn’t my first language, I asked ChatGPT/AI to help optimize this post to make it more readable and viewer-friendly.

I hope this isn’t against any downvoting rules 🙏
But if it is, feel free to let me know and I’ll be more cautious next time.

---

🚀 My Contributions to ♦️ Hive Ecosystem

---

🙌 Support Back

❤️ Appreciate my work? Consider supporting @threespeak & @sagarkothari88! ❤️