e30ae8ed09
- App.tsx: full navigation (Auth stack + Main tabs with 5 screens) - Auth: LoginScreen, RegisterScreen, ForgotPasswordScreen - HomeScreen: dashboard with IoT metrics, weather widget, alerts, quick actions, sensors - MapScreen: interactive map with layer toggles (6 layers) - MarketplaceScreen: categories (6), products (5), search - ChatScreen: AI chat with quick prompts (4), bot responses - ProfileScreen: user info, stats, menu (9 items), logout - AlertsScreen: alert list with severity, acknowledge - SensorsScreen: sensor list with type filters (6 types), search - ZonesScreen: zone cards with stats - SettingsScreen: language picker (FR/EN/ES/DE), privacy, about - Stores: iotStore (sensors, zones, alerts), notificationStore, uiStore + i18n - Hooks: useSensors, useAlerts, useNotifications, useLocation - Components: Card, Button, LoadingSpinner, ErrorBoundary, Header - Services: iotService, notificationService (with axios API client) - Utils: formatters (temp, AQI, noise, dates), validators (email, password, IBAN) - Theme: colors.ts with full design system (Blue Ocean palette) - Ditto: fixed MongoDB connection, new JWT secrets, official gateway image
44 lines
1.9 KiB
JavaScript
44 lines
1.9 KiB
JavaScript
import { EventEmitter, Platform } from 'expo-modules-core';
|
|
import PushTokenManager from './PushTokenManager';
|
|
// Web uses SyntheticEventEmitter
|
|
const tokenEmitter = new EventEmitter(PushTokenManager);
|
|
const newTokenEventName = 'onDevicePushToken';
|
|
/**
|
|
* In rare situations, a push token may be changed by the push notification service while the app is running.
|
|
* When a token is rolled, the old one becomes invalid and sending notifications to it will fail.
|
|
* A push token listener will let you handle this situation gracefully by registering the new token with your backend right away.
|
|
* @param listener A function accepting a push token as an argument, it will be called whenever the push token changes.
|
|
* @return A [`Subscription`](#subscription) object represents the subscription of the provided listener.
|
|
* @header fetch
|
|
* @example Registering a push token listener using a React hook.
|
|
* ```jsx
|
|
* import React from 'react';
|
|
* import * as Notifications from 'expo-notifications';
|
|
*
|
|
* import { registerDevicePushTokenAsync } from '../api';
|
|
*
|
|
* export default function App() {
|
|
* React.useEffect(() => {
|
|
* const subscription = Notifications.addPushTokenListener(registerDevicePushTokenAsync);
|
|
* return () => subscription.remove();
|
|
* }, []);
|
|
*
|
|
* return (
|
|
* // Your app content
|
|
* );
|
|
* }
|
|
* ```
|
|
*/
|
|
export function addPushTokenListener(listener) {
|
|
const wrappingListener = ({ devicePushToken }) => listener({ data: devicePushToken, type: Platform.OS });
|
|
return tokenEmitter.addListener(newTokenEventName, wrappingListener);
|
|
}
|
|
/**
|
|
* Removes a push token subscription returned by an `addPushTokenListener` call.
|
|
* @param subscription A subscription returned by `addPushTokenListener` method.
|
|
* @header fetch
|
|
*/
|
|
export function removePushTokenSubscription(subscription) {
|
|
tokenEmitter.removeSubscription(subscription);
|
|
}
|
|
//# sourceMappingURL=TokenEmitter.js.map
|