-
Notifications
You must be signed in to change notification settings - Fork 166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error running in release mode #172
Comments
Closing as this works fine on |
This because Line 8 in 4aacdae
and in the example flutter_background_service/packages/flutter_background_service/example/lib/main.dart Line 51 in 4aacdae
Please see dart-lang/sdk#49181 (comment) |
…-level functions. Fixes ekasetiawans#172
Is this fix already available in version 2.1.3? |
Please see #172 (comment) |
Just to confirm, I created a new project and added this lib to it, and the It should have come because this annotation is in the master branch of the repository. |
same issue. my device is Pocophone X3 GT with android 12 cannot launch the service when the app build in release mode. Flutter V3.3 E/flutter ( 8225): [ERROR:flutter/shell/common/shell.cc(93)] Dart Error: Dart_LookupLibrary: library 'package:flutter_background_service_android/flutter_background_service_android.dart' not found.
E/flutter ( 8225): [ERROR:flutter/runtime/dart_isolate.cc(668)] Could not resolve main entrypoint function.
E/flutter ( 8225): [ERROR:flutter/runtime/dart_isolate.cc(167)] Could not run the run main Dart entrypoint.
E/flutter ( 8225): [ERROR:flutter/runtime/runtime_controller.cc(385)] Could not create root isolate.
E/flutter ( 8225): [ERROR:flutter/shell/common/shell.cc(604)] Could not launch engine with configuration. |
I have an app that works perfectly in debug mode, however once in release mode (so far tested in Android), the background service is not triggered. Not sure if there is an obfuscation somewhere.
Steps:
flutter build apk
flutter install
flutter logs
Which show:
Using flutter
master
.flutter doctor -v
The text was updated successfully, but these errors were encountered: