My understanding is Proguard is automatically enabled for the release builds. Please try adding the Proguard configuration from our docs (just to make sure it is not causing any issues).
Yes… you was right. Enabled by default.
After creating manually proguard rules and adding your lines - all works ok.
BUT how can you explain that null-safe version of code is done good?
And, also, flutter embedding v2 main feature is dynamic plugin embedding and better background execution of plugins, so this lines do not need to be written there?
As I understand, embedding v2 letting Flutter decide the way of integration, not Kotlin or Java. Enabling Proguard custom config is a kludge.
But it works. Thank you.
Thank you for confirming that it works. Glad to hear it.
I suspect the reason it works is with the null-safe version, the Proguard is not activated.
I am not sure, this is the trickery that Google enforces on the developers. The best way to find out is by applying the trial-and-error approach.
Regards,
Mark
This message is a warning about Android embedding. It’s not critical and cannot cause any crashes or build errors. Our Flutter team is currently working on this issue and will release the fix soon.
Best Regards,
Maksym
Hello, @islam_yassin, @Carlton_Branch, @A2_Capital.
We have released Flutter-SDK 7.1.3. Now warning will not occur.
Best Regards, Nikita.