Pete
@kodehausdev
Followers
121
Following
4K
Media
86
Statuses
626
Kodehaus đĄ â Indie Dev life. Android ⢠Firebase ⢠AI experiments Shipping â Failing â Learning â Shipping again....
Joined July 2025
3 Things Everyone MUST Protect Every Day! ⣠Time ⣠Energy ⣠Attention We donât have hours to waste. We are busy ⣠Lifting ⣠Learning ⣠and Building An Elite Strategy guards all 3 with Simplicity. 𧾠1/5
17
1
33
Community feedback is gold. Day 3: adding serving-size adjustment - first feature inspired by @humbleconduit. The plan? Make every recipe fit your table size, not the other way around.. #mealFlow
2
0
8
Finally, the subscription got approved.
Itâs been 12 days since the app got approved. The subscription is still stuck on âWaiting for review.â At this point, itâs just frustrating. Youâre waiting on something that you canât control.
3
1
11
It's liberating to let go of the pressure to fit into someone else's plans or settle for mediocrity ...
2
0
8
Omg, Gemini has given me several wrong version numbers, I'm starting to think it's trolling us đ ...
0
0
6
What i learned Git bisect + UI isolation = Sherlock Holmes mode on. Some bugs look like navigation nightâmares but are really UI gremlins in disguise. Now the MealFlow app runs smoothly.. no more surprise crashes ...
0
0
1
The fix - Replace that funky <layerâlist> placeholder with a valid <vector> drawable. Boom-everything renders smoothly whether the list is empty, halfâfull, or a buffet.â¨
1
0
0
What went wrong? I was using painterResource() to load a <layerâlist> XML as a placeholder. painterResource is a bit of a picky eater-it only digests vectors (<vector>) or bitmaps (PNG/JPG). Throw it a complex <layerâlist> and it throws a hissy fit, crashing the whole app.
1
0
0
VICTORY! #MealFlow crash-on-login bug is finally squashed.. TL;DR: The app blew up only when the recipe list was populated. A sneaky line in my AsyncImage composable was the culprit-
PLOT TWIST in the #MealFlow saga! 𤯠After isolating the bug to my RecipeListScreen, I uncommented all the UI code, expecting it to crash.And it... didn't. đ¤I logged in with a brand new account (0 recipes) and it worked perfectly. I could log in and out. The UI was beautiful.
2
0
2
Funnily, no one is expecting my calls except mom.. Hey mom, just checking in.. you still want to talk to me, right? đ
1
0
2
investigation is now laser-focused. I know the crash happens somewhere inside the else block of my RecipeListContent, where it tries to show the AnimatedContent with the recipe list.The empty state works, the populated state crashes. Time to inspect every modifier and component
0
0
1
The moment of truth came when I tried to log in with my main account-one that actually has recipes saved.Result: INSTANT CRASH.I confirmed it with the new account: as soon as I saved its first recipe and logged out, it also started crashing on the next login
1
0
2
PLOT TWIST in the #MealFlow saga! 𤯠After isolating the bug to my RecipeListScreen, I uncommented all the UI code, expecting it to crash.And it... didn't. đ¤I logged in with a brand new account (0 recipes) and it worked perfectly. I could log in and out. The UI was beautiful.
The detective work on #MealFlow continues. đľď¸ââď¸ After git bisect pointed me to the commit that introduced a crash-on-login bug, I knew the problem was in my RecipeListScreen.The next step? Isolate the problem. I commented out the entire screen's content and replaced it with -
2
0
4
a single Text composable. voila screen is working. Now the real work begins. I'll start re-introducing the UI components one by one-the search bar, the animations, the LazyColumn-until the crash comes back. tedious, but it's the only way. The hunt is on!
0
0
0