> These docs cover Nitro Cookies 1.3.0. List APIs, scoped deletion, and normalized errors are available from 1.3.0. Check the installation guide and release history when upgrading from an earlier version.

# Delete one cookie scope

Use the `clearCookie` APIs when multiple cookies share a name.
Supply the original name, domain, and path to avoid selecting a sibling cookie.

## Apple: retain the stored identity

```ts
import NitroCookies from "react-native-nitro-cookies";

const url = "https://api.example.com/admin";
const cookies = await NitroCookies.getList(url);
const target = cookies.find(
  (cookie) => cookie.name === "session" && cookie.path === "/admin",
);

if (target?.path) {
  await NitroCookies.clearCookie(url, {
    name: target.name,
    domain: target.domain,
    path: target.path,
  });
}
```

List results preserve Apple's stored domain, including its leading dot. Pass that representation back unchanged.
Pass `true` to both asynchronous calls when working with the iOS WebKit store.
Deleting a missing identity succeeds without changing another cookie.

## Android: retain the original write scope

Android URL lists cannot recover stored domains or paths. Keep those fields when writing:

```ts
const url = "https://api.example.com/admin";
const scope = { name: "session", domain: "api.example.com", path: "/admin" };

await NitroCookies.set(url, {
  ...scope,
  value: "server-issued-token",
  secure: true,
});
await NitroCookies.clearCookie(url, scope);
```

An explicit domain emits a Domain attribute, with or without a leading dot.
Existing Android `set` also emits a Domain attribute when it defaults a missing domain to the URL host.
Retain that domain for deletion; do not infer a host-only scope from an omitted `set` argument.

Omit the deletion domain only for a cookie actually stored as host-only, such as a raw Set-Cookie header without Domain.
Use HTTPS for Secure cookies.

## Completion and validation

On Android, `clearCookieSync` submits an expiration write without acknowledgment.
`clearCookie` waits for write acceptance. Neither method can report whether the cookie existed.
Apple deletion resolves after the selected store operation.

The selector requires a valid cookie name, an absolute path, and a compatible domain.
Invalid selectors fail before mutation. See [delete cookies](https://l2hyunwoo.github.io/react-native-nitro-cookies/reference/deletion.md) and [errors](https://l2hyunwoo.github.io/react-native-nitro-cookies/reference/errors.md).

## Log out without clearing unrelated domains

Retain every cookie identity used by the login flow, including cookies with the same name at different paths.
On Apple, retain the chosen store too. On Android, record the original write scopes because reads cannot reconstruct them.

```ts
import NitroCookies, {
  type CookieIdentifier,
} from "react-native-nitro-cookies";

const url = "https://api.example.com/account";
const identities: CookieIdentifier[] = [
  { name: "session", domain: "api.example.com", path: "/" },
  { name: "session", domain: "api.example.com", path: "/account" },
];

for (const identity of identities) {
  await NitroCookies.clearCookie(url, identity);
}
```

This example deletes only the supplied identities from the default store.
For an iOS WebKit login, pass `true` as the third argument of each `clearCookie` call.
Use a compatible URL for each domain; a single URL cannot select unrelated domains.

`clearAll` clears the entire selected store, including unrelated domains. Reserve it for a deliberate full-store reset.
Local cookie deletion does not revoke a server session or remove credentials held by another store or HTTP client.
Complete server logout and any client-specific cleanup according to your app's authentication flow.