mirror of
https://github.com/bulwarkmail/native.git
synced 2026-10-31 08:06:36 +00:00
Linus Rath
82ca359df7
`index.ts` imported `App` at the top, so when an FCM data message started the headless push task in a cold process, the bundle evaluated every screen, store, catalog and icon before the task could show its notification. The headless task is still registered at the top of `index.ts`, but the root component now requires `App` when the UI first renders. A headless start therefore only evaluates the task and its own imports; a normal launch evaluates the same modules as before, one render later. Measured with `npx expo export --platform android` (modules reached through top-level requires from the entry, i.e. what a headless start evaluates): 1,516 modules, 7,238 KB -> 202 modules, 745 KB.
24 lines
1.0 KiB
TypeScript
24 lines
1.0 KiB
TypeScript
import { createElement } from 'react';
|
|
import { AppRegistry } from 'react-native';
|
|
import { registerRootComponent } from 'expo';
|
|
|
|
import { pushBackgroundTask } from './src/lib/push-background-task';
|
|
|
|
// Runs in a fresh headless JS runtime when BulwarkPushTaskService is started
|
|
// from BulwarkMessagingService on an FCM data message. Must be registered
|
|
// before the native service tries to invoke the task.
|
|
AppRegistry.registerHeadlessTask('BulwarkPushTask', () => pushBackgroundTask);
|
|
|
|
// A headless push task evaluates this file too, so App is required when the
|
|
// UI first renders instead of imported above: importing it here would load
|
|
// every screen, store and icon before the task could run.
|
|
function Root() {
|
|
const App = (require('./App') as typeof import('./App')).default;
|
|
return createElement(App);
|
|
}
|
|
|
|
// registerRootComponent calls AppRegistry.registerComponent('main', () => Root);
|
|
// It also ensures that whether you load the app in Expo Go or in a native build,
|
|
// the environment is set up appropriately
|
|
registerRootComponent(Root);
|