-
Notifications
You must be signed in to change notification settings - Fork 129
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
Critical Issue and apk not build with pusher-channels-flutter on Flutter 3.24.0 #174
Comments
Launching lib\main.dart on sdk gphone16k x86 64 in debug mode... FAILURE: Build failed with an exception.
BUILD FAILED in 1s Exited (1). |
Using pusher_channels_flutter from GitHubTo use the Option 1: Regular DependencyAdd the following to your dependencies:
flutter:
sdk: flutter
pusher_channels_flutter:
git:
url: https://github.com/ArmanKT/pusher-channels-flutter.git
ref: master
or
dependency_overrides:
pusher_channels_flutter:
git:
url: https://github.com/ArmanKT/pusher-channels-flutter.git
ref: master |
FAILURE: Build failed with an exception. I'm reaching out to report an issue with the pusher-channels-flutter package while trying to build an APK on Flutter Unfortunately, the build is currently failing, and it appears to be due to compatibility issues with the latest Flutter version. I have tried troubleshooting, but the problem seems to persist. Given how widely this package is used, I would highly recommend looking into this issue and providing a fix. It would greatly help many developers, including myself, who rely on this package for production environments. |
FAILURE: Build failed with an exception.
Execution failed for task ':pusher_channels_flutter:verifyReleaseResources'.
I'm reaching out to report an issue with the pusher-channels-flutter package while trying to build an APK on Flutter 3.24.0. Unfortunately, the build is currently failing, and it appears to be due to compatibility issues with the latest Flutter version. I have tried troubleshooting, but the problem seems to persist.
Given how widely this package is used, I would highly recommend looking into this issue and providing a fix. It would greatly help many developers, including myself, who rely on this package for production environments.
The text was updated successfully, but these errors were encountered: