2ndbeam/fluffychat-fork
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

chore: set main isolate port even earlier

Browse source
This commit is contained in:
Christian Kußowski 2025-11-11 16:24:51 +01:00
commit ae11d5b47f
No known key found for this signature in database
GPG key ID: E067ECD60F1A0652
1 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

10
lib/main.dart
View file

@ -18,11 +18,6 @@ import 'widgets/fluffy_chat_app.dart';
ReceivePort? mainIsolateReceivePort; ReceivePort? mainIsolateReceivePort;
void main() async { void main() async {
// Our background push shared isolate accesses flutter-internal things very early in the startup proccess
// To make sure that the parts of flutter needed are started up already, we need to ensure that the
// widget bindings are initialized already.
WidgetsFlutterBinding.ensureInitialized();
if (PlatformInfos.isAndroid) { if (PlatformInfos.isAndroid) {
final port = mainIsolateReceivePort = ReceivePort(); final port = mainIsolateReceivePort = ReceivePort();
IsolateNameServer.registerPortWithName( IsolateNameServer.registerPortWithName(
@ -31,6 +26,11 @@ void main() async {
); );
} }
// Our background push shared isolate accesses flutter-internal things very early in the startup proccess
// To make sure that the parts of flutter needed are started up already, we need to ensure that the
// widget bindings are initialized already.
WidgetsFlutterBinding.ensureInitialized();
final store = await AppSettings.init(); final store = await AppSettings.init();
Logs().i('Welcome to ${AppSettings.applicationName.value} <3'); Logs().i('Welcome to ${AppSettings.applicationName.value} <3');