iOS Nutrition App, Pre-Submission Bug Fixing (5 Hours, Fixed Price)

We have a calorie tracking iOS app that is nearly ready for App Store submission. Internal testing is done and the app is stable, but every so often a food entry comes back with an obviously wrong calorie count or a lookup that errors out instead of returning a result. We need someone sharp to hunt these edge cases down and fix them so the experience is clean before we submit. This is a fixed scope, roughly 5 hours of focused work. If it goes well there is more ongoing work after launch. WHAT YOU'LL DO - Stress test food entry and barcode lookups across a wide range of items (common foods, edge cases, regional products, ambiguous names) - Identify why certain foods return incorrect calorie or macro values - Find and fix cases where a lookup errors out or returns nothing - Tighten validation so impossible values (negative, zero, absurdly high) never reach the user - Confirm the fixes hold up across a fresh batch of test foods STACK - iOS front end in SwiftUI (Xcode) - Backend in Node.js / Express with a Supabase (Postgres) database - Food recognition runs through an LLM-based pipeline with a few external nutrition data sources as fallbacks IDEAL CANDIDATE - Comfortable across both Swift and Node, or at minimum strong on the backend where most of these bugs likely live - Has shipped or debugged a production iOS app before - Methodical about edge cases and good at reproducing intermittent issues - Can work independently from a short brief and a codebase WHAT DONE LOOKS LIKE A batch of test foods (including the tricky ones) all return sensible, accurate values with no errors, and the validation layer reliably catches bad data before it shows up in the UI. TO APPLY Briefly tell me about a time you tracked down an intermittent or data-quality bug in a shipped app, and what the root cause turned out to be. One or two sentences is enough. Please start your reply with the word "Plate" so I know you read this.