Rest assured, however, that if / when Flutter does remove support for the old APIs (perhaps in 3.0?), we'll make sure that our plugin still works and doesn't lead to developer headaches. With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime. It will then give a list of what it thinks the problems are and you can go through the list and sort them out. I'll open up a PR for the suppressed warnings in a bit. Try recompiling with -Xlint:Deprecation or whatever it would say without the smilie as the option on your javac command. This is also what Flutter itself is doing for their plugins, see this example. So the best path to follow for this particular case is to suppress the deprecation warnings, and remove the methods once v1 support is removed, which might take a long time. We upgraded to the new format back in June 2020, however, Flutter recommends that we keep the old methods around for apps that use the v1 method of embedding. Note: Recompile with -Xlint:unchecked for details. Note: Recompile with -Xlint:deprecation for details. Note: Recompile with -Xlint:unchecked for details. Since 1.12, Flutter's had a new format for plugins to use, which introduces better handling of the app's lifecycle. You will get: herong> javac RawTypeTest.java Note: RawTypeTest.java uses unchecked or unsafe operations. The reason why the compiler is giving you this warning is because you have used a deprecated function call. The deprecations that get referenced by the warning are all related to flutter's v1 plugin format. Recompile with -Xlint:deprecation for details java 74,298 Solution 1 This is not an error it's a warning message. I don't have an exact ETA, however, for this particular case, removing the deprecated API usage isn't really an option:
0 Comments
Leave a Reply. |