Below is a Markdown-formatted explanation of some challenges we encountered while building StoreEdge and how we overcame them:

Challenge 1: Handling File Uploads – "Multipart: Boundary not found" Error

One significant hurdle was with the image upload functionality. When sending images to the backend using Axios and Multer, we encountered the following error:

Error: Multipart: Boundary not found

What Happened

• Cause:
  We manually set the

  Content-Type

  header to

  "multipart/form-data"

  in our Axios request. This prevented Axios from appending the necessary boundary parameter, which is required for the server (via Multer/Busboy) to correctly parse the multipart data.

How We Solved It

• Investigation:
  We inspected the request headers and realized that manually setting the header was interfering with Axios’s automatic configuration.
• Solution:
  We removed the explicit

  Content-Type

  header. When you pass a

  FormData

  object to Axios, it automatically sets the correct header (including the boundary).

// Before: Manually setting Content-Type causes errors
const response = await axios.post(
  `${import.meta.VITE_BACKEND_BASE_URL}/api/products/create`,
  formData,
  {
    headers: {
      "Content-Type": "multipart/form-data"
    }
  }
);
// After: Allow Axios to set the header automatically
const response = await axios.post(
  `${import.meta.VITE_BACKEND_BASE_URL}/api/products/create`,
  formData
);
---
### Challenge 2: Integrating SMS Gateway for Partial Payment Reminders
Another challenge was ensuring that SMS reminders were sent reliably when a customer created a partly paid bill.
#### What Happened
- **Issue:**  
  We noticed delays and inconsistent delivery of SMS messages, which sometimes resulted in customers not receiving timely payment reminders.

in app we faced challenge on managing the state of the billing screen containing no of widgets and models.