Group1 INT3506

  Title : Progress and Timesheet Author  Sampurna Adhikari We are at the ending stage of our final application. Currently working on optimization and testing of the entire system.  Started documentation part of the project ie Image Evidence, Application Manual , presentation slides. 1. Sherpa Delivery Now seamlessly works 2. Stripe Handles split payment 3. Mapbox is working fine for foods markers. List View and Map View to switch New and Improved Dashboard   Weekly Report Time Sheet

Author Prajwal Poudel Student ID – 12927 This week, my friends and I completed the flow from listing to delivery. However, this week was for checking the application on the actual device. The execution and installation of the application on the real device (used Galaxy Z Flip 5) was smooth and trouble-free Work done  Execution, Installation and testing of the application on the actual device without any trouble. The location was working perfectly, showing my location precisely. I have done listing to payment delivery correspondingly, which was working perfectly fine. Current status and plans There was an issue with UI, which I have noticed and am planning to fix in the upcoming days. When I type in the password field, it doesn’t display the masked characters (like ), and instead shows blank white space. The input still works correctly, but the masking is not visible in the simulator.” A similar issue occurs on the Create Listing page. When the keyboard appears, the input text ...

 Sagar Chaudhary Student ID – 12040 Work Done Improved the Dashboard layout to make key user information easier to read and more organised. Updated the design of the Recent Activity section , ensuring food history items appear clearly with proper spacing and icons. Enhanced the visual structure for: Total Listings Total Orders My Requests Location & Map markers Fixed alignment issues between cards and made sure the dashboard scales correctly on different screen sizes. Improved icon consistency (size, color, padding) to match the overall app design. Helped test dashboard navigation between Home → Dashboard → Activity , verifying smooth transitions. Current Status Dashboard now displays cleaner cards , improved spacing, and consistent styling. Recent Activity loads correctly with updated UI and no overlapping elements. Dashboard works well on smaller and larger devices after layout refinements. No major UI bugs present; only final po...

  Title : Pickup and Dropoff Markers  Author Sampurna Adhikari After successful delivery payment the markers are shown from where the parcel is picked and when it will be dropped!

  Title : Issue Relating to Sherpa Delivery Rendering and Chat Screen Author Sampurna Adhikari Chat Screen  -> Messages were not sent and only quick messages were sent and photos were uploaded. Then again i checked some codes and then i came down to the messages being sent but as an object.  .    Sherpa Screen  📍 POST /api/sherpa/quote [SHERPA] Quote request received: {   pickup: 'Sydney NSW',   dropoff: '6 Station Road, Auburn New South Wales 2144, Australia',   lat: -33.849183,   lng: 151.034972,   vehicleType: 1 } [SHERPA] Authenticating for quote... [SHERPA] Auth success (quote). [SHERPA] Requesting quote with payload: {   pickup: 'Sydney NSW',   pickupLat: undefined,   pickupLng: undefined,   dropoff: '6 Station Road, Auburn New South Wales 2144, Australia',   lat: -33.849183,   lng: 151.034972,   vehicleType: 1 } [SHERPA] Quote success — Price: 49.65.     all the process u...

  Author Prajwal Poudel Student ID – 12927 This week's major focus was on developing and testing the Sherpa delivery integration, fixing new project setup concerns, reviewing Sherpa's payment limits, and preparing for the Stripe split-payment implementation. The majority of the work was focused on developing a standalone Sherpa application to properly test OAuth, quotation, and delivery creation operations before integrating them into the main system. This week was also spent analysing how Sherpa's billing model fits into the platform, identifying potential transaction-volume issues, and assessing how split payments will be integrated into the actual program. Work done  Created a stand-alone Sherpa testing application to validate OAuth login, quote requests, and delivery creation in an isolated environment. This configuration was used to check API behavior, evaluate documentation, and identify any restrictions before migrating the procedure to the main project. Before begin...

Title : Progress and  TimeSheet Author Sampurna Adhikari This week I was able to successfully implement AI Recommendations and made some minor improvement on the overall user experience within the app visually. The main task for me this week was along with Prajwal worked on the Sherpa Delivery Quote and calling it into the Frontend.  After some feedback from Kriss on Friday, I targeted the Chat Screen and improved some ui elements with implementing the AI from backend to detect any foul languages or self harm messages from being sent. The AI Automatically flags any words and immediately alerts the user. Attach Photos Quick Messages  Some of the features Previous Issue Currently fixing the Sherpa Quote issue and majority of the errors are fixed. Plans for Next Week Figure the Sherpa Payment System(Usage Limits) Proper Tracking Screen for Sherpa Testing the entire App.   Weekly Report Time Sheet

 Sagar Chaudhary Student ID – 12040 Work Done Reviewed and tested the Chat Screen UI to ensure messages appear clearly and consistently for both Senders and Receivers. Ensured messages display in the correct alignment: Right side = My messages Left side = Other user messages Verified smooth scroll behaviour, checking that new messages automatically scroll into view without glitches. Tested message sending and receiving flows after request approval, confirming chat only unlocks once the food request is accepted. Checked the chat layout across multiple devices to ensure proper spacing, padding, and responsive design. Updated UI consistency issues such as timestamp placement and bubble spacing. Current Status Chat screen is with stable message delivery on both sides. UI alignment issues have been resolved and messages now appear clean and readable. Scrolling behaviour works smoothly without sudden jumps or cut-off messages. Chat becomes availabl...

  Author Sampurna Adhikari Using Open AP from backend to filter all the chats and blocking from sending inappropriate messages.  Its gonna check every word used in the chat room and then alert if suspicious word is detected. For extra safety i have also flagged some of the word inas well. As some of the words (curse words) are not flagged as risk.

  Title: Issue Loading Sherpa Delivery Quote Author Sampurna Adhikari From below log i can confirm the correct quote for the delivery is created but then the Front End which is CheckoutScreen.js is not being updated and is always falling back to the default 20km fee Sherpa Order History -> I cancelled the Order but the price is correct  POST /api/sherpa/create-delivery  [SHERPA] Create delivery request: {   pickup: '123 kings street',   pickupLat: null,   pickupLng: null,   dropoff: 'Auburn, New South Wales, Australia',   lat: -33.854885,   lng: 151.0247,   vehicleType: 1,   foodTitle: 'Momo',   receiverName: 'Sri ',   receiverPhone: '1234567899'  [SHERPA] Authenticating for delivery creation...  [SHERPA] Auth success (delivery). [SHERPA] Getting quote before creating delivery… [SHERPA] Got quote for delivery creation: 47.15 [SHERPA] Sending delivery payload: {   pickup_address: '123 kings street',  ...

  Title : AI Recommendations Author Sampurna Adhikari AI Recommendation can be turned on with the Toggle on the home screen. it reads the data of users, their location and allergens and then displays the recommended food to them on a new lists of the available food.  

   Title : Dashboard Issue  Author Sampurna Adhikari Both the Food Donor and Food Receiver have access to the Dashboard where Active Listings, Completed Orders and Active Requests are shown. The issue is the Active Listings and Requests are being displayed and for the Total Spent, the amount is not being pulled.  let totalSales = 0 ; let ordersSnap = { docs : [] }; const donorStripeId = userData ?. stripeAccountId || userData ?. donorStripeId ; console . log ( " Donor Stripe ID:" , donorStripeId ); if ( donorStripeId ) { try { ordersSnap = await getDocs ( query ( collection ( db , "orders" ), where ( "donorStripeId" , "==" , donorStripeId ), orderBy ( "createdAt" , "desc" ) ) ); console . log ( ` Orders found: ${ ordersSnap ...

  Title : Plan for the Week Author Sampurna Adhikari Fix Sherpa Delivery Payment Split Testing  Dashboard Chart. 

    Title : Payment Split when a users pickups a food works Author Sampurna Adhikari -> When a users checkout with the Pickup option, the total fees is being split between the Food Lister, Platform(Our Fee) and stripe fee. Logs:  When a user pays for food the backend creates a Stripe PaymentIntent which is  transfer_data.destination  is the donor stripe account which is connected via profile . application_fee_amount   which is platform’s marketplace fee and stripe automatically deducts processing fees from the connected account’s payout . here the total amount 11.17 is charged to a user paying for the food then we take 2.20 as our fee and the rest is then transfered to the donor stripe account.

 Sagar Chaudhary student id:12040 Work Done Assisted in identifying Week 9 checkout issues (free listing bug + Stripe capability error) by testing multiple request → approval → checkout scenarios. Verified the behaviour of listings during checkout, ensuring paid items don’t show as “Free Listing.” Helped test Stripe payment flow after fixes, including: Business account capability validation Food price transfer Platform fee handling Conducted UI checks across the checkout and delivery pages to ensure stable rendering after backend payment updates. Supported team with Sherpa flow testing (quote generation & distance calculation). Current Status Checkout UI is stable after fixes; paid listings now show correct price. Stripe payment flow is working with updated capability and transfer logic. Sherpa quote fetching is functional for testing distances below and above 20 km. No blocking UI bugs remaining on request → approve → checkout path. Pla...

  Author Prajwal Poudel Student ID – 12927 The primary focus of the week was to resolve build issues caused by space in the directory name, implement Stripe and delivery workflow testing, plan the AI recommendation system, and review Sherpa’s payment workflow to ensure alignment with the platform’s structure. This week also involved backend preparation and a review of documentation for upcoming development tasks. Work Done Fixed the build issue caused by the project directory having a space (“FoodNextDoor copy”), which was breaking the build process. Abandoned the older project setup due to repeated dependency problems and created a new, clean project environment to properly test Stripe integration and delivery workflow. Finalised the Stripe split payment structure where the donor receives the food cost through Stripe Connect, and the platform keeps the delivery fee plus 1% commission. Updated the Stripe payment logic using transfer_data and application_fee_amount ...

  Title : Progress Details  Author Sampurna Adhikari Stripe Payment is implemented. Sherpa On Demand Courier is also implemented and once we type in the address we get a quote and if the delivery distance is above 20km then an $19.99 applies AI Recommendation is also implemented (Open AI) To Do  Split the payment between Users(Resturants or households) , Platform fee(FoodNextDoor) and stripe fee Split payment with delivery as well.    Weekly Report Time Sheet

  Title : Issue  Author : Sampurna Adhikari -> That Routing Error was fixed. What happened was for Food Donor and Food Receiver our 2 users of the app, I wanted to seperate the TAB bar for them to make the experience more clean and hide some screens that are to required for Food Donor(ie Home and Map).  For that, i created 2 tab bars  app/(tabs_donor) and app/(tabs_receiver). and a simple role check in app/_layout.js to redirect them to respective once logged in. with almost 3 hours spent that route error just kept on coming so i had to abandon that whole part and just organize the tab bar for all the users.

  Title : Issue  Author : Sampurna Adhikari Issue 1  When a Food Donor logs in for that particular user browse food (home.js) and map(map.js) is optional and donot require to view these screens so for that to happen i created seperate tabs_donor and tabs_receiver and then on app/_layout.js a simple role check and redirecting to the respective page.  But the error is even if the login is successful the app wont redirect me to the main app. Currently working on this issue. few error logs  ERROR [Error: Screen names must be unique: index,GetStarted,Authentication,(tab_donor),(tab_receiver),ChatScreen,CheckoutScreen,createlistings,editlisting,editprofile,modal,(tab_donor),(tab_receiver)] Code: _layout.js 147 | return ( 148 | <StripeProvider publishableKey="pk_test_51SGb1FRhXrCJgpPwtDG4AG7bwo3wdLR06Se1kJwBfAKxgi6UKCZPHlw8b4ASB566csNplZSS8UBo5ltMx9E0oMUB00VNmnbncg"> > 149 | <Stack screenOptions={{ headerShown: false }}> | ...

Title : Issue Resolved  Author Sampurna Adhikari   Errors Resolved  Your destination account needs to have at least one of the following capabilities enabled: transfers, crypto_transfers, legacy_payments" This error popped when i tried to checkout and during payment to a Food Donor which is a business account. -> This error occured because when a business profile was signing up for via the stripe connect account, some of the details was not provided and it was not completed and for that reason that profile was not setup and the payment was cancelled.  Once the request for the food has been accepted and the user in time of checkout enough though the listing is paid is seeing free listing and only marketplace fee is payable.  -> This error was also resolved as i forgot to pass the price of the food when creating a request and then the price was always set as Free Listing .

  Title : Issue  Author : Sampurna Adhikari Issue 1 Once the request for the food has been accepted and the user in time of checkout enough though the listing is paid is seeing free listing and only marketplace fee is payable.  Issue 2 "Your destination account needs to have at least one of the following capabilities enabled: transfers, crypto_transfers, legacy_payments" This error popped when i tried to checkout and during payment to a Food Donor which is a business account.

Author Prajwal poudel Student ID - 12927  The primary focus of the week was to conduct device compatibility testing for the application on smaller iOS devices (especially the iPhone 13 mini), to ensure that all key interfaces. Additionally, this week involved team coordination and preliminary planning for the upcoming development task. Work done 1. Tested device compatibility on smaller iPhones, specifically the iPhone 13 Mini , to assess UI adaptability and responsiveness. 2. Encountered an issue where the sign-in form exceeded the visible screen area and the page was not scrollable , preventing users from signing in. 3. After resolving the UI issue, a new console error appeared — initially displaying “Uncaught id = 0” and incrementing (id = 1, id = 2, etc.) upon each reload. Current status and plans: 1. Implemented changes to  make the page scrollable , which  successfully resolved  the sign-in accessibility problem. 2. Verified that this console error  do...

Author: Sagar Kumar Chaudhary Student ID – 12040 Overview The primary focus of my Week 8 tasks was to improve key user interface screens, ensure stability across various request-related features, and collect image evidence for the team’s weekly progress documentation. A major portion of the work involved reviewing and testing the request workflows, food listings, and checkout screens to maintain consistent functionality across devices. Work Done 1. Request Management Improvements Reviewed and refined the Incoming Request s and My Requests screens for clarity and consistency. Ensured visibility of request statuses such as: Approved Denied Pending Helped verify the toggle behavior between the two request types to ensure smooth usability. 2. Food Listings UI Verification Checked and improved various visual elements of the Browse Food and Home Listing screens. Ensured correctness of: Food price and quantity display Available time indicators ...

Title : Issue Current and Resolution Author : Sampurna Adhikari This week i was able to run the app on IOS as well. The error was simple , Previously the Folder was named as Advanced Studio which prevented the building of the IOS, and Android handles that space but for IOS it was a different case and then when i changed the Folder to AdvancedStudio it was installed and the app ran smoothly . via npx expo run:ios  The next error was with the Stripe Onboarding for the users who are signed in. Before i was able to continue with Stripe Onboarding as a Food Donor and when i try to do the same for Food Receiver i was unable to proceed and the error was   LOG Connecting with: {"email": "sampurna009@mailinator.com", "userId": "PnDfo6QYeuemGvBF50xm1gpNNyU2"} LOG Status: 500 [React] ' Stripe Connect Error:', [Error: role is not defined] LOG Response: {"error":"role is not defined"} ERROR Stripe Connect Error: [Error: r...

Title : Progress Details and Plans  Author : Sampurna Adhikari  Current Progress and Functionality of the App: Login/Register View Profile and Edit details and change email and password Delete Account Signout Browse Foods Browse Foods using MapView for nearby foods. Create listings for both the users and edit the listings as well with all the description,title,avaliable time etc Request Food with quantity Accept the requested food or deny it and can also delete the requests. Once approved the users are able to chat with each other. Once approved the users are then able to checkout and pickup is fully functional with stripe payment. Users are able to sign up for stripe from the app itself as they are redirected to stripe onboarding url.  Weekly Report Time Sheet Plans For This Week: Sherpa API Onboarding AI Integrations and looking at different API to include on the app.   Firebase Notification Function docs

The aim for this week was to create an environment on a macOS machine to test all of the app's existing functionalities on iOS.  Because most development and testing had been done on Android, the primary goal was to ensure seamless operation and compatibility across all platforms.  Work Done: 1. Set up the Mac development environment and test the program on the iOS emulator. 2. An emulator path problem prohibited the program from launching initially. The issue was resolved by specifying the emulator path correctly, which enabled the program to launch successfully. 3. Discussed and planned the structure and functionalities for the upcoming Admin Panel (Dashboard). 4. Checked the payment system, which was integrated successfully by Sampurna. Current Status And Plans: 1. IOS testing is Successful and fully Functional. 2. Development of the Dashboard 3. Upcommig Focus Area include Sherpa Delivery and  then AI Recommendation. Toggle Weekly Report:  https://drive.google.co...

    Title : Plans for Next Week Author: Sampurna Stripe Testing and Optimizations Stripe Payment Sheet Sherpa API Documentation check Sherpa Docs