Platform behavior
Requirements, limitations, and differences between iOS and Android.
Requirements
| Requirement | |
|---|---|
| React Native | New Architecture (the native module is a TurboModule) |
| Other dependencies | None |
| Android | minSdkVersion 24 |
| iOS | Minimum iOS version supported by your React Native version |
iOS
- Toasts are drawn with native views in an overlay
UIWindow, above modals and sheets presented by the app. - Haptics use a light
UIImpactFeedbackGenerator.
Android
- Each toast is presented in its own non-focusable dialog window, so toasts appear above React Native modals and bottom sheets and do not steal focus from inputs.
- Haptics use the activity window's haptic feedback.
- Font files linked into
assets/fontsshould use the font family name as their file name.
Limitations
Toast content is data, not JSX.
- There is no
toast.custom. Icons and buttons do not accept React elements. - Styles are limited to the keys in Styling, so they render the same on both platforms.
- A plain
toast()shows no icon. toast.loadingtoasts stay visible until they are updated or dismissed.