In the App Router you can't hand a promise to a client component - props crossing the server/client boundary have to be serializable. Since Next 15, searchParams is itself a promise, so await it inside the server component and pass the resolved values down as plain props:

// Server Component
export default async function Page({ searchParams }) {
  const params = await searchParams; // resolve the promise here
  const details = { id: params.id, name: params.name, ...params }; // plain object
  return <ClientComponent details={details} />;
}

// Client Component
'use client';
export function ClientComponent({ details }) {
  return <div>{details.id} - {details.name}</div>;
}

The reason you see id but not the other attributes is almost certainly that somewhere the raw searchParams promise (or an unresolved value derived from it) is being passed down instead of the awaited result. Resolve everything with await in the server component first. Plain objects, arrays, strings and numbers all cross the boundary fine - just avoid non-serializable values like class instances or Dates (serialize those first).

Are you trying to pass data from your server component to the client one? If so, you might need to serialize and pass those attributes through props or URL params instead of relying on the promise alone. Can you share a quick code snippet of how you're currently passing the data? That'll help figure out why the other stuff isn't making it through.