You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had a good time debugging but I can't figure out the source of the problem at all.
In my code I need to pass information from my UI to my service and vice versa, for that I use .json files which contain all the information I need.
The problem is that I can't use the getApplicationDocumentsDirectory function contained in a custom class in my service, even though I use the same class as in my UI. So the problem can't be the class.
A precision that may be important is that the getApplicationDocumentsDirectory function is called in my custom class and comes from the path_provider package which is quite common.
My error is this:
[ERROR:flutter/lib/ui/ui_dart_state.cc(209)] Unhandled Exception: MissingPluginException(No implementation found for method getApplicationDocumentsDirectory on channel plugins.flutter.io/path_provider)
Do you know why the service does not seem to take the package into account?
And if so, how do I fix it please?
Thanks in advance
The text was updated successfully, but these errors were encountered:
Hello,
I had a good time debugging but I can't figure out the source of the problem at all.
In my code I need to pass information from my UI to my service and vice versa, for that I use .json files which contain all the information I need.
The problem is that I can't use the getApplicationDocumentsDirectory function contained in a custom class in my service, even though I use the same class as in my UI. So the problem can't be the class.
A precision that may be important is that the getApplicationDocumentsDirectory function is called in my custom class and comes from the path_provider package which is quite common.
My error is this:
Do you know why the service does not seem to take the package into account?
And if so, how do I fix it please?
Thanks in advance
The text was updated successfully, but these errors were encountered: