NPE when using geolocator with android_alarm_manager about flutter-geolocator HOT 7 CLOSED

I will try to update the code to use the Context directly available from registrar to avoid to pass by the Activity.

from flutter-geolocator.

@sestegra I checked our code and the error happens on the spot where the native code returns the result to Dart using the instance of the MethodResult class. Looking into the "android_alarm_manager", it looks like the printHello method is called from the background. Did you follow the instructions on the documentation of the "android_alarm_manager" explaining the usage of other Flutter plug-ins together with the "android_alarm_manager" (to following is copied directly from the README):

If alarm callbacks will need access to other Flutter plugins, including the alarm manager plugin itself, it is necessary to teach the background service how to initialize plugins. This is done by giving the AlarmService a callback to call in the application's onCreate method. See the example's Application overrides. In particular, its Application class is as follows:

public class Application extends FlutterApplication implements PluginRegistrantCallback {
  @Override
  public void onCreate() {
    super.onCreate();
    AlarmService.setPluginRegistrant(this);
  }

  @Override
  public void registerWith(PluginRegistry registry) {
    GeneratedPluginRegistrant.registerWith(registry);
  }
}

from flutter-geolocator.

@mvanbeusekom I not only follow the documentation, I updated the example (that implements the Application class) to call Geolocator.

Basically, I cloned the plugins project, update the example code with above snippet and run it.

from flutter-geolocator.

I still got the following error coming from permissions.

D/permissions_handler( 9153): Unable to detect current Activity.

from flutter-geolocator.

It works if I get permission from MainActivity.

from flutter-geolocator.

@sestegra the problem with the permissions can also be solved by taking care of them manually when the App starts using the permission_handler plugin.

Unfortunately to take care of permissions we do need an Activity (which makes sense because we need to show the user a dialog). So by taking care of the permissions manually when we are sure the App is running (before we launch services in the background) we can be sure there is an activity.

Then when the Geolocator gets called it will notice that all permissions are taken care of and will simply continue acquiring the location and not try to get the required permissions.

from flutter-geolocator.

@sestegra a quick follow up, we just release version 1.6.3 of the Geolocator plug-in which includes your changes. Thanks again for reporting the issue.

from flutter-geolocator.