Do not rely on the Activity object when this plugin is instantiated.

[ened]

✨ What kind of change does this PR introduce? (Bug fix, feature, docs update...)

Bug fix

⤵️ What is the current behavior?

Plugin is incompatible with background isolates which may be held by a service on Android

🆕 What is the new behavior (if this is a feature change)?

Plugin will depend on the generic Context class and cast to activity (if available) to show the google play services warning fragment.

💥 Does this PR introduce a breaking change?

No

🐛 Recommendations for testing

Setup a background isolate holder Service

📝 Links to relevant issues/docs

🤔 Checklist before submitting

• All projects build
• Follows style guide lines (code style guide)
• Relevant documentation was updated
• Rebased onto current develop

[mvanbeusekom]

LGTM Thanks for contributing

[ened]

The permission handler plugin seems to rely on the “activeContext” function instead of “context”. Perhaps something this PR should do as well.

[robotsrulz]

I am interested to have this pull request merged. Can anybody tell me the reason it's not? I looked through logs of failed build and it seems to me that this patch is not reason, there is something else.

[mvanbeusekom]

@ened first of all thanks for the PR, we really appreciate it!

Just to reply on your last question, since I recently figured this out for the geolocator and location_permission plugins (see Baseflow/flutter-permission-plugins#1 (comment)).

I think it would be best to keep using the context method here since it will return the ApplicationContext instead of the current Activity or ServiceContext. For more information please have a look at this article.

[mvanbeusekom]

@robotsrulz, I have just release version 2.0.1 of this plugin which includes this PR

[ened]

@mvanbeusekom thx.