Flutter POS Bug & Printer Fix
Budget: $10 – $30 USD
I’m maintaining a Flutter-based mobile POS application and two issues are stopping us from rolling into production.
The first and most urgent: the app crashes right after a credit/debit card transaction is completed. It behaves normally while the customer data is entered, but as soon as the payment gateway confirms the charge the application closes.
The second: our Bluetooth receipt printer is no longer responding. Pairing succeeds at the OS level, yet nothing prints from the app and no error is thrown in the console.
What I need is a clean, reproducible fix for both problems along with a brief explanation of what caused them so we can avoid regressions later.
Deliverables
• Updated Flutter/Dart code (or a pull request) that eliminates the post-transaction crash.
• Working Bluetooth print workflow, tested from the same build of the app.
• A concise changelog or README note outlining the modifications and any package or SDK updates required.
I can supply the current source, error logs, and steps to reproduce each problem as soon as we start. If you have recent experience with Flutter, Bluetooth printing, and payment flows, you should feel right at home.
The first and most urgent: the app crashes right after a credit/debit card transaction is completed. It behaves normally while the customer data is entered, but as soon as the payment gateway confirms the charge the application closes.
The second: our Bluetooth receipt printer is no longer responding. Pairing succeeds at the OS level, yet nothing prints from the app and no error is thrown in the console.
What I need is a clean, reproducible fix for both problems along with a brief explanation of what caused them so we can avoid regressions later.
Deliverables
• Updated Flutter/Dart code (or a pull request) that eliminates the post-transaction crash.
• Working Bluetooth print workflow, tested from the same build of the app.
• A concise changelog or README note outlining the modifications and any package or SDK updates required.
I can supply the current source, error logs, and steps to reproduce each problem as soon as we start. If you have recent experience with Flutter, Bluetooth printing, and payment flows, you should feel right at home.