The Dreaded MissingPluginException (Let's have an FAQ)
As a plugin developer, I get numerous issues regarding this error on a regular basis. There are many unrelated causes for this error, and to make matters worse, the error message identifies the plugin that was attempting to use platform channels although that is not necessarily the plugin that is responsible for the error, and so you get issues posted by app developers on the wrong projects asking for the bug to be fixed. Furthermore, sometimes the error is caused by an incorrectly written plugin and other times it is caused by something the app developer did or didn't do. In both cases, there is a lack of documentation to help both the plugin developer and the app developer to navigate this issue and track down the root of what's causing it. What I think is sorely needed is an official MissingPluginException FAQ listing all of the causes for this error and how to address them. Additionally, since a lot of these errors can be caused whenever an app is creating a background FlutterEngine and it fails to register plugins for some reason, the documentation for Flutter background execution needs to be improved. The following page, for example, still refers to an old Medium article written by Ben Konyi that desperately needs an update: https://flutter.dev/docs/development/packages-and-plugins/background-processes On the Android side, the linked article has still not been updated to explain the v2 architecture and plugins that don't do this correctly may fail to do plugin regis
Posted by ryanheise on Jul 22, 2020, 6:03 AM
Tags
Related issues
- Many devs love to shit on the guy from the 'I just want the exe.
- Now imagine how poor people stress if their smartphone bricks or gets damaged or lost.
- Resuming an extended-thinking session fails permanently with 400 "thinking blocks cannot be modified" (transcript stores thinking text as empty but keeps signat
- I'll preface this with a statement that as a European I want European alternatives to succeed, and MS-owned GitHub to shrivel and disappear.
- Yeah, but there’s a world of difference between “not perfect” and “we rounded a few sliders, and now the modal is a nightmare to use”.
- I used to write a lot of native Windows corporate software in the 90's and 2000's and my standard login window was a floating draggable o...
Raise real-world problems, find people facing the same issue, and discuss solutions.3,500 issues0 comments
reliability (SaaS)
Many devs love to shit on the guy from the 'I just want the exe.
Now imagine how poor people stress if their smartphone bricks or gets damaged or lost.
Resuming an extended-thinking session fails permanently with 400 "thinking blocks cannot be modified" (transcript stores thinking text as empty but keeps signat
I'll preface this with a statement that as a European I want European alternatives to succeed, and MS-owned GitHub to shrivel and disappear.
Yeah, but there’s a world of difference between “not perfect” and “we rounded a few sliders, and now the modal is a nightmare to use”.
I used to write a lot of native Windows corporate software in the 90's and 2000's and my standard login window was a floating draggable o...
App broken with Mosquitto broker 7.0.0
[BUG] Remote Control: automatic reconnection doesn't work -- connection drops silently with no recovery
The Dreaded MissingPluginException (Let's have an FAQ)
As a plugin developer, I get numerous issues regarding this error on a regular basis. There are many unrelated causes for this error, and to make matters worse, the error message identifies the plugin that was attempting to use platform channels although that is not necessarily the plugin that is responsible for the error, and so you get issues posted by app developers on the wrong projects asking for the bug to be fixed. Furthermore, sometimes the error is caused by an incorrectly written plugin and other times it is caused by something the app developer did or didn't do. In both cases, there is a lack of documentation to help both the plugin developer and the app developer to navigate this issue and track down the root of what's causing it. What I think is sorely needed is an official MissingPluginException FAQ listing all of the causes for this error and how to address them. Additionally, since a lot of these errors can be caused whenever an app is creating a background FlutterEngine and it fails to register plugins for some reason, the documentation for Flutter background execution needs to be improved. The following page, for example, still refers to an old Medium article written by Ben Konyi that desperately needs an update: https://flutter.dev/docs/development/packages-and-plugins/background-processes On the Android side, the linked article has still not been updated to explain the v2 architecture and plugins that don't do this correctly may fail to do plugin regis
Comments (0)
No comments yet. Start the discussion.