This repository was archived by the owner on Nov 20, 2024. It is now read-only.
[share] Don't nullify method channel's call handler when detached from Activity #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
In an add-to-app Android application, the
sharemethod channel is set up with the appropriateMethodCallHandlerset when the plugin attaches to the Flutter engine. When the Android app launches aFlutterActivity,onAttachedToActivityis called to set the activity on theShareinstance and invokingshareworks initially. Once theFlutterActivityis dismissed and you're taken back to native,onDetachedFromActivityis executed which nullifies the activity on theShareinstance as well as theMethodCallHandleron the method channel. Subsequent launches ofFlutterActivitynever rebind theMethodCallHandleron the share method channel so any calls tosharewill then fail with:The solution here is to not nullify the
MethodCallHandlerwhen theFlutterActivityis detached and only nullifying the activity on theShareinstance.Related Issues
Replace this paragraph with a list of issues related to this PR from the issue database. Indicate, which of these issues are resolved or fixed by this PR. Note that you'll have to prefix the issue numbers with flutter/flutter#.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]). This will ensure a smooth and quick review process.///).flutter analyze) does not report any problems on my PR.Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?