Native Platform APIs

Find the shipped shared and iOS service APIs, permissions, and lifecycle contracts

Service namespaces live on One, including services with platform-specific operations. The camera view and widget layout helpers below use One.iOS. Hooks are named imports from one. Use each reference for the complete signature, configuration, permission behavior, event cleanup, and errors.

Shared services

One.Auth.Apple is grouped under the shared authentication namespace, but Apple authorization is an iOS operation. On Android and web, isAvailable is false and authorization calls reject.

Secure storage uses string keys and values:

import { One } from 'one'

export async function saveSession(token: string) {
  await One.SecureStore.setItem('session', token)
}

export async function readSession() {
  return One.SecureStore.getItem('session')
}

export async function clearSession() {
  await One.SecureStore.deleteItem('session')
}

A missing key reads null. SecureStore rejects on web; choose a separate web session strategy. The synchronous verbs block the JavaScript thread, so reserve them for a value needed synchronously, such as an initial session read.

More native services

These service namespaces are exported on One. Their references describe supported platforms, native configuration and unavailable operations. One.iOS.CameraView and One.iOS.WidgetUI are iOS components.

Widget and Live Activity APIs need a generated extension, App Group, and the relevant signing capabilities. Native project setup shows the configuration. Widgets render a supported serialized JSX layout, not an arbitrary React Native subtree.

Permissions and subscriptions

Configure native usage descriptions and capabilities before building the app, then request runtime permission from the corresponding API. A camera picker, camera preview, library picker, and Photos library management have different permission contracts. The system picker can select media without granting the app general library access.

A live network subscription returns an object with remove():

import { useEffect, useState } from 'react'
import { One } from 'one'

export function useConnectionType() {
  const [type, setType] = useState('unknown')

  useEffect(() => {
    const subscription = One.Network.addStateListener((state) => {
      setType(state.type)
    })
    return () => subscription.remove()
  }, [])

  return type
}

For a component that also needs the initial snapshot, use the exported useNetworkState hook. Other services can return an unsubscribe function or another handle; follow their own cleanup signature rather than assuming every service uses remove().

HTTP

Native global fetch streams response bodies and accepts React Native file parts in FormData. Use its standard request and response objects by calling the global fetch function directly. Streaming is separate from One.Network, which reports connection state.