Permissions

Most permissions are handled on demand: the first time you use a feature, the OS
prompts. When you need to know a permission’s state up front, or ask for it with
your own context (an onboarding screen, a “why we need this” explainer), use the
permission API. Results come back on the nb:permission Livewire event with a
normalized status, so iOS and Android read the same way.

Use a NativeBlade\Config\Permission constant for the permission name.

Check and request

use NativeBlade\Config\Permission;
use NativeBlade\Facades\NativeBlade;

// Silent: never shows a prompt.
return NativeBlade::checkPermission(Permission::LOCATION)->toResponse();

// Shows the OS prompt when the permission has not been decided yet.
return NativeBlade::requestPermission(Permission::CAMERA)->toResponse();

The outcome arrives on the nb:permission event:

use Livewire\Attributes\On;

#[On('nb:permission')]
public function onPermission(string $name, string $status)
{
    // $name:   the permission you asked about
    // $status: 'granted' | 'denied' | 'prompt' | 'unsupported'
    if ($name === 'camera' && $status === 'denied') {
        $this->showEnableCameraHint = true;
    }
}

Status values

Coverage

Each permission resolves through a plugin that already exposes it, so the backing
plugin must be enabled. Anything else returns unsupported.

Other constants (MICROPHONE, CONTACTS, CALENDAR, PHOTOS, …) return
unsupported until a plugin backs them.

Open the app settings

After a denied the app usually cannot prompt again, so the natural next step is
to send the user to the OS settings page for the app with
NativeBlade::openAppSettings(). See App Settings for the
full details.

Notes

• Declaring a permission (so it appears in the manifest / Info.plist) is separate
  from asking for it at runtime. See Plugins for declaring the
  permissions your app ships with.
• requestPermission shows the system dialog only when the state is prompt. If
  it is already granted or denied, no dialog appears and you get the current
  status back.