0

I’m experiencing an issue where my Flutter app works fine on most devices, but on some Android devices and emulators, it gets stuck on the icon/logo screen during the first launch.

Details from my logs:

[IMPORTANT:flutter/shell/platform/android/android_context_gl_impeller.cc(104)] Using the Impeller rendering backend (OpenGLES)
D/com.llfbandit.app_links: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] ... }
D/FLTFireContextHolder: received application context.
I/Choreographer: Skipped XXX frames! The application may be doing too much work on its main thread.

Observations:

  • GetX controllers are initialized only after the icon/logo screen.
  • Firebase Crashlytics and Firebase Core are initialized.
  • The issue occurs mostly on emulators with x86_64 architecture or older devices.
    On other devices, the app launches normally.
  • Disabling Impeller seems to fix the issue on some emulators.

My main.dart looks like this:

void main() async {
  WidgetsFlutterBinding.ensureInitialized();

  await Firebase.initializeApp();

  FlutterError.onError = FirebaseCrashlytics.instance.recordFlutterFatalError;

  runApp(const MyApp());
}

Plugins used that run at startup:

  • Firebase Core / Crashlytics / Messaging
  • AppLinks
  • GetX

What I’ve tried:

  • Delaying heavy API calls in the splash controller.
  • Running on a physical device (works fine).
  • Disabling Impeller (flutter run --enable-impeller=false) resolves the freeze on emulators.
  • Making sure Firebase is initialized before runApp.

Question:

  • Why does my Flutter app freeze on the icon/logo screen only on some devices?
  • Could it be Impeller, Firebase, or AppLinks?
  • What is the best practice to avoid this problem for all devices and emulators?
Improve this question
2
  • According to the logs, the main thread remains overloaded on x86_64 devices. These devices may lack sufficient computational power. While keeping the same code flow for higher-end devices, try offloading more tasks from the main thread specifically for x86_64 devices. Commented Oct 20 at 11:36
  • I’m seeing reports that on some Android devices, the app installs successfully via the Play Store but gets stuck on the launch icon (splash) screen. For example, we have a confirmed report from a Pixel 8a device experiencing this issue. No crash logs are reported in Crashlytics. The issue appears device-specific, as it doesn’t affect all devices. The app works fine when installed on other devices or via direct APK installation. This suggests that the problem might be related to first-time launch, device-specific configurations, or Android version-specific behavior rather than a code crash. Commented Oct 24 at 11:19
Related questions
510
No Firebase App '[DEFAULT]' has been created - call Firebase.initializeApp() in Flutter and Firebase
11
Facing 'No Firebase App has been created' while uploading to Firebase Storage in a Flutter app
0
I am coding a Firebase app with flutter but i am getting errors about google-services.json and inititilization
Load 3 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.