-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[firebase_messaging] Deprecation warning after updating flutter. #1625
Comments
Hi @jcvw75 |
I did the first 2 and the issue is still there, but I also enabled -Xlint:deprecation in gradle and got some other warning message this time. Builds fine though. ------flutter build apk --split-per-abi--------------------- Running Gradle task 'assembleRelease'...
-------------------------------flutter doctor -v--------------------------- [√] Flutter (Channel stable, v1.12.13+hotfix.5, on Microsoft Windows [Version 6.3.9600], locale en-US) [√] Android toolchain - develop for Android devices (Android SDK version 28.0.3) [√] Android Studio (version 3.5) [√] VS Code, 64-bit edition (version 1.41.0) [!] Connected device ! Doctor found issues in 1 category. ----flutter run --verbose----------------------------------------------------------------------------- flutter run --verbose #0 throwToolExit (package:flutter_tools/src/base/common.dart:28:3) |
-------------------------------flutter doctor -v--------------------------- [√] Android toolchain - develop for Android devices (Android SDK version 29.0.2) [√] Android Studio (version 3.5) [√] VS Code (version 1.41.1) [√] Connected device (1 available) • No issues found! ----flutter run --verbose--- |
hai, do you solve this? i just got the error here. |
@iapicca I am using
I applied your comment #1625 (comment)
And still have the issue, please fix the deprecated code :) |
downgrading
|
Hey all 👋 As part of our roadmap (#2582) we've just shipped a complete rework of the If you can, please try out the dev release (see the migration guide for upgrading and for changes) and if you have any feedback then join in the discussion here. Given the scope of the rework I'm going to go ahead and close this issue in favor of trying out the latest plugin. Thanks everyone. |
The text was updated successfully, but these errors were encountered: