Build with "@nativescript/android": "8.2.0-alpha.10" fails
cjohn001 opened this issue · comments
When building with "@nativescript/android": "8.2.0-alpha.10" runtime the build fails with the following console output:
Downloading https://services.gradle.org/distributions/gradle-7.2.0-bin.zip
Exception in thread "main" java.io.FileNotFoundException: https://downloads.gradle-dn.com/distributions/gradle-7.2.0-bin.zip
at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1920)
at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1520)
at java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:250)
at org.gradle.wrapper.Download.downloadInternal(Download.java:60)
at org.gradle.wrapper.Download.download(Download.java:45)
at org.gradle.wrapper.Install$1.call(Install.java:62)
at org.gradle.wrapper.Install$1.call(Install.java:48)
at org.gradle.wrapper.ExclusiveFileAccessManager.access(ExclusiveFileAccessManager.java:69)
at org.gradle.wrapper.Install.createDist(Install.java:48)
at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:107)
at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:61)
Failed to build plugin @nativescript-community/ui-material-core :
Error: Command ./gradlew failed with exit code 1
It is not clear to me if the bug might be related with the ui-material-components, see discussion here:
nativescript-community/ui-material-components#350 (comment)
"dependencies": {
"@angular/animations": "13.2.1",
"@angular/common": "13.2.1",
"@angular/compiler": "13.2.1",
"@angular/core": "13.2.1",
"@angular/forms": "13.2.1",
"@angular/platform-browser": "13.2.1",
"@angular/platform-browser-dynamic": "13.2.1",
"@angular/router": "13.2.1",
"@apollo/client": "3.5.8",
"@nativescript-community/ui-material-tabs": "6.2.10",
"@nativescript/angular": "13.0.1",
"@nativescript/core": "8.1.5",
"@nativescript/iqkeyboardmanager": "2.0.0",
"@nativescript/localize": "5.0.4",
"@nativescript/mlkit-barcode-scanning": "1.0.0-alpha.8",
"@nativescript/mlkit-core": "1.0.0-alpha.8",
"@nativescript/secure-storage": "3.0.0",
"@nativescript/theme": "3.0.2",
"@nativescript/ui-charts": "file:../mnd-custom-plugins/nativescript-ui-charts/publish/package/nativescript-ui-charts-0.1.10.tgz",
"apollo-angular": "3.0.0-alpha.2",
"apollo3-cache-persist": "0.13.0",
"d3-ease": "3.0.1",
"graphql": "16.3.0",
"graphql-tag": "2.12.6",
"intl": "1.2.5",
"moment": "2.29.1",
"nativescript-oauth2-ext": "file:../mnd-custom-plugins/nativescript-oauth2-ext/publish/package/nativescript-oauth2-ext-3.0.0.tgz",
"nativescript-sqlite": "2.8.6",
"nativescript-ui-autocomplete": "8.0.1",
"nativescript-ui-calendar": "file:../mnd-custom-plugins/plugins-ui/dist/packages/ui-calendar/nativescript-ui-calendar-8.0.0.tgz",
"nativescript-ui-gauge": "8.0.1",
"reflect-metadata": "0.1.13",
"rxjs": "7.5.2",
"uuid": "8.3.2",
"zone.js": "0.11.4"
},
"devDependencies": {
"@angular-devkit/build-angular": "13.2.2",
"@angular/compiler-cli": "13.2.1",
"@graphql-codegen/cli": "2.5.0",
"@graphql-codegen/fragment-matcher": "3.2.1",
"@graphql-codegen/introspection": "2.1.1",
"@graphql-codegen/typescript": "2.4.3",
"@graphql-codegen/typescript-apollo-angular": "3.3.3",
"@graphql-codegen/typescript-operations": "2.2.4",
"@nativescript/android": "alpha",
"@nativescript/ios": "8.1.0",
"@nativescript/types": "8.1.1",
"@nativescript/webpack": "5.0.4",
"@ngtools/webpack": "13.2.2",
"@types/d3-ease": "3.0.0",
"@types/intl": "1.2.0",
"@types/node": "16.11.6",
"@types/uuid": "8.3.4",
"codelyzer": "6.0.2",
"keycloak-request-token": "0.1.0",
"rimraf": "3.0.2",
"sass": "1.49.7",
"tslint": "^6.1.3",
"ts-node": "10.4.0",
"typescript": "4.5.5"
},
Issue can be observed with both of the following cli versions:
ns --version
8.1.5-next-12-23-2021-1617049163
ns --version
8.1.5-next-02-03-2022-1791684443
Update to .11
@triniwiz : Thanks a lot .11 builds are working :)
I suspected that the new runtime might already have the connection patches included we were speaking about yesterday on discord. Should this be the case? I just ask, because I am still seeing the app on android emulator freeze when the chrome debugger connects. I close the issue here than. One step ahead :)