Project Overview
Kamana Store is a multi-franchise eCommerce platform powered by Flutter and Laravel, supporting product discovery, franchise store selection, shopping carts, and online checkout.
I worked on maintaining and improving the existing application, investigating Flutter and iOS build issues, and preparing an updated release for Apple's App Store.
The project required careful debugging and release preparation to preserve existing functionality while resolving compatibility and compilation problems.
Project Status: iOS App Store Update in Progress
My Role: Full Stack Developer – Flutter, Laravel & Release Engineering
Technology: Flutter, Dart, Laravel, Xcode, CocoaPods, Git, GitHub, TestFlight
The Challenge
Preparing an iOS update for an existing multi-franchise application introduced several technical challenges.
The main issues included Xcode signing warnings, provisioning profile configuration, iOS deployment target compatibility, and Flutter compilation errors preventing the release archive.
Development was also split between a Linux environment and a Mac used for iOS builds, requiring better coordination and code synchronization.
The objective was to resolve release-blocking issues without disrupting the existing shopping experience.
My Contributions
1. iOS Signing & Configuration
Investigated Apple Developer certificates, provisioning profiles, Bundle Identifier settings, and Xcode signing configurations.
Verified the existing distribution setup and preserved the application's registered identity instead of introducing unnecessary certificate or signing changes.
2. Flutter Compilation Fixes
Identified three Dart compilation errors affecting the flash-deal and checkout address screens.
The affected functions declared a Container return type while attempting to return SizedBox widgets.
Corrected the return types to Widget, resolving the identified type incompatibilities without changing the existing UI or checkout logic.
Validation results:
-
3 compilation issues addressed.
-
2 Flutter files modified.
-
94 relevant Flutter tests passed.
-
0 errors in targeted Dart analysis.
-
Existing UI and navigation logic preserved.
The changes have passed local validation. A successful iOS release archive remains pending.
3. iOS Compatibility Investigation
Investigated deployment target compatibility between the Flutter application, CocoaPods dependencies, and the installed Xcode toolchain.
Separated actual compilation failures from dependency warnings and avoided unnecessary package upgrades.
4. Development Workflow Improvement
Prepared a Git-based update workflow to replace repeated ZIP downloads.
This approach is intended to improve synchronization between Linux development and macOS release environments.
Final verification of the Mac-side Git setup remains pending.
Technical Results
| Area | Outcome |
|---|---|
| Flutter compilation | 3 reported issues addressed |
| Code changes | 2 files modified |
| Automated testing | 94 tests passed |
| Dart analysis | 0 targeted errors |
| iOS signing | Configuration reviewed |
| Release archive | Pending |
| TestFlight testing | Pending |
| App Store update | Pending |
Current Outcome
The initial iOS release investigation identified three specific Flutter compilation issues, which were addressed through minimal code changes.
The fixes passed 94 relevant automated tests without requiring changes to existing checkout behavior or application business logic.
The project has progressed from general Xcode build failures to a more clearly defined release preparation process.
The updated iOS application is now awaiting successful archive generation and TestFlight validation.
Next Phase
The remaining release activities include:
-
Generate and upload the updated iOS build.
-
Verify login and existing user sessions.
-
Test franchise selection and product availability.
-
Validate cart, checkout, and payment workflows.
-
Complete TestFlight acceptance testing.
-
Submit the verified application for Apple's review.
Conclusion
This project demonstrates my approach to maintaining existing mobile applications through focused debugging, minimal code changes, automated testing, and structured release preparation.
Rather than introducing broad changes, I prioritized identifying actual build failures and preserving the established multi-franchise eCommerce experience.
Status: Ongoing — Final App Store release results will be added after successful TestFlight testing and publication.
