I'll fix the deployment error by adding the required loading components and wrapping the search params usage in Suspense boundaries.

I've fixed the deployment error by:

1. Added loading components for all dashboard pages (loading.tsx files) that provide proper skeleton loading states

2. Wrapped search params usage in Suspense boundaries by:

   • Creating separate content components that handle the useSearchParams() hook
   • Wrapping these content components in <Suspense> with the loading components as fallbacks
   • Moving the main page components to be simple wrappers that handle the Suspense boundary
3. Maintained all existing functionality while ensuring proper loading states and avoiding the useSearchParams() error

The key changes:

• Main page components now just wrap content in <Suspense>
• Content components handle all the logic including useSearchParams()
• Loading components provide proper skeleton states for each page
• URL parameters are still properly handled and initialized from search params

This approach ensures that the deployment will succeed while maintaining all the existing functionality and providing better user experience with proper loading states.

I detected and automatically synced new changes from new-features in UNM-admin-panel.