-
Notifications
You must be signed in to change notification settings - Fork 38
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
Issue on error building apk #3
Comments
Hi @shuaibidshuaib , |
nope i think its from gradle issues
…On Sun, Apr 3, 2022 at 2:36 AM Shivani Singh ***@***.***> wrote:
Hi @shuaibidshuaib <https://github.com/shuaibidshuaib> ,
My apologize for not seeing this yet, is this over or do you need any help
?
—
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUZEYA5TWUDTQM4ULTJWUSTVDGNG5ANCNFSM5EWUDTXA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hi @shuaibidshuaib , |
Hello there sister, after downloading your project, just by inserting and running "Flutter build apk --release" , i got the following error, pls help me to sort it out.
Running Gradle task 'assembleRelease'...
FAILURE: Build failed with an exception.
Running Gradle task 'assembleRelease'...
Running Gradle task 'assembleRelease'...
Running Gradle task 'assembleRelease'...
java.net.BindException: Address already in use: Cannot bind
Running Gradle task 'assembleRelease'...
Running Gradle task 'assembleRelease'...
Running Gradle task 'assembleRelease'...
Run with --stacktrace option to get the stack trace. Run with
--info or --debug option to get more log output. Run with --scan to get full insights.
Running Gradle task 'assembleRelease'...
Running Gradle task 'assembleRelease'...
* Get more help at https://help.gradle.org
Running Gradle task 'assembleRelease'...
Running Gradle task 'assembleRelease'... Done 36.9s
Gradle task assembleRelease failed with exit code 1
C:\Users\MTGSTCKN\Downloads\Compressed\hopOn-master\hopOn-master\lib>
The text was updated successfully, but these errors were encountered: