search

Vanethos / flutter_notification_permissions

Plugin for Flutter to check and ask for Notification Permissions
BSD 2-Clause "Simplified" License
81 stars 72 forks source link

The plugin `notification_permissions` uses a deprecated version of the Android embedding. #38

Closed dpedrinha closed 3 years ago

dpedrinha commented 3 years ago

I started getting the following warning (that surely looks almost like an error):

The plugin notification_permissions uses a deprecated version of the Android embedding. To avoid unexpected runtime failures, or future build failures, try to see if this plugin supports the Android V2 embedding. Otherwise, consider removing it since a future release of Flutter will remove these deprecated APIs. If you are plugin author, take a look at the docs for migrating the plugin to the V2 embedding: https://flutter.dev/go/android-plugin-migration.

I just want to be sure that it's being looked at and that my app won't stop working once Android updates.

Here's my flutter doctor:

Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel master, 2.4.0-5.0.pre.164, on Microsoft Windows [version 10.0.19042.1110],
    locale pt-BR)
[√] Android toolchain - develop for Android devices (Android SDK version 30.0.1)
[√] Chrome - develop for the web
[√] Android Studio (version 4.2)
[√] Connected device (3 available)

• No issues found!
junqi commented 3 years ago

@dpedrinha In my case, by changing the flutter version to the stable version, the error message is no longer displayed. (flutter channel stable; flutter clean; flutter pub get)

I recommend you try it.

dpedrinha commented 3 years ago

@dpedrinha In my case, by changing the flutter version to the stable version, the error message is no longer displayed. (flutter channel stable; flutter clean; flutter pub get)

I recommend you try it.

I'm not worried about the warning. I'm worried if the devs are aware of it and planning to update it in time.

Kal-Elx commented 3 years ago

Any updates? Is this being worked on?

dpedrinha commented 3 years ago

Any updates? Is this being worked on?

I'm starting to get worried. Last interaction from anyone involved in the plugin here was in May.

@Vanethos how are you, man? Can we still count on your updates?

Vanethos commented 3 years ago

Hello!

Sorry for being so AWOL, tough times at work.

Will do my best to try to check the error and update the library in due time, probably over the weekend.

In the meantime, if anyone has a PR that can aid me in this quest (currently viewing this on my e-mail), that would be amazing.

Thanks for being so patient!

dpedrinha @.***> escreveu em qui., 9/09/2021 às 09:26 :

Any updates? Is this being worked on?

I'm starting to get worried. Last interaction from anyone involved in the plugin here was in May.

@Vanethos https://github.com/Vanethos how are you, man? Can we still count on your updates?

— You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub https://github.com/Vanethos/flutter_notification_permissions/issues/38#issuecomment-915873995, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACR3JOMW7LCYGSKJYNRVVGLUBBVSHANCNFSM5A3ARVGA .

-- Gonçalo Palma Flutter Developer https://gpalma.pt

ened commented 3 years ago

hi @dpedrinha, @Kal-Elx please take a look at the linked PR & check if the plugin is working for you.

Kal-Elx commented 3 years ago

hi @dpedrinha, @Kal-Elx please take a look at the linked PR & check if the plugin is working for you.

Yes this removes the warning. Thanks @ened, great work!

dpedrinha commented 3 years ago

I can confirm the warning is gone and that it works on my project. I didn't check the code though. I'll leave it to you @Vanethos. It's your baby :) And thank you @ened !

Vanethos commented 3 years ago

Will prepare the release now, thank you!

Vanethos commented 3 years ago

Right now I'm just migrating the pubspec.yaml to the new way of declaring plugins, and I'll be back with a new pub version

Vanethos commented 3 years ago

Version 0.6.0 up @ened @dpedrinha and @Kal-Elx ! 🚀

I'm deeeeeply sorry for taking so long, I really coudln't manage to be here earlier

Aulig commented 3 years ago

Awesome, thanks for your work @ened & @Vanethos :)

dpedrinha commented 3 years ago

Right now I'm just migrating the pubspec.yaml to the new way of declaring plugins, and I'll be back with a new pub version

Oh jeezz is that a thing? Man it's getting hard to keep up with flutter updates...

I'm deeeeeply sorry for taking so long, I really coudln't manage to be here earlier

All good man. As you can see, I get it. I honestly spend more time updating and fixing bugs from updates than working on new features and projects nowadays. I've so many ideas that I could be working on right now and I bet you too. But there's this invisible weight called deprecation dragging us.

Honestly, the dev community need to become more aware of this problem and start prioritizing non-disrupting updates. Specially those working on SDKs, IDEs, APIs and ecosystems in general.

Sorry for the rambling. I'm just tired (and scared as hell) of Flutter, Android and iOS updates.

KDCinfo commented 3 years ago

Right now I'm just migrating the pubspec.yaml to the new way of declaring plugins, and I'll be back with a new pub version

Oh jeezz is that a thing?

I initially thought the same thing, but I think they're referring to how package developers implement the pubspec.yaml for their pub.dev packages. https://medium.com/dartlang/announcing-dart-2-14-b48b9bb2fb67

Side note: I'm currently theorizing one way to get ahead of the Flutter deprecation curve is to switch to the master channel when you have some time, research and apply the deprecation changes, then switch back to stable (it should have no issues with your deprecation fixes from master). There didn't seem to be quite as many with 2.5 as there were with 2.0, but then Material You is coming our way too.