A problem occurred configuring project ':app'.
See original GitHub issueSince I installed webpack, I follow the instructions for to update nativescript, I begin with a problem with nativescript-plugin-firebase and I go on with others problems, finally I got this error,
A problem occurred configuring project ‘:app’.
No match found
my package.json is this:
"tns-android": {
"version": "3.4.1"
}
},
"dependencies": {
"@angular/animations": "~5.0.0",
"@angular/common": "~5.0.0",
"@angular/compiler": "~5.0.0",
"@angular/core": "~5.0.0",
"@angular/forms": "~5.0.0",
"@angular/http": "~5.0.0",
"@angular/platform-browser": "~5.0.0",
"@angular/platform-browser-dynamic": "~5.0.0",
"@angular/router": "~5.0.0",
"email-validator": "^1.1.1",
"firebase-functions": "^0.7.5",
"nativescript-angular": "^5.0.0",
"nativescript-plugin-firebase": "^5.1.2",
"nativescript-theme-core": "~1.0.2",
"nativescript-xml2js": "^0.5.2",
"reflect-metadata": "~0.1.8",
"rxjs": "^5.5.0",
"tns-core-modules": "^3.4.0",
"zone.js": "^0.8.4"
},
"devDependencies": {
"@angular/compiler-cli": "~5.0.0",
"@ngtools/webpack": "~1.8.2",
"babel-traverse": "6.4.5",
"babel-types": "6.4.5",
"babylon": "6.4.5",
"copy-webpack-plugin": "~4.0.1",
"css-loader": "~0.28.7",
"extract-text-webpack-plugin": "~3.0.0",
"lazy": "1.0.11",
"nativescript-dev-typescript": "^0.6.0",
"nativescript-dev-webpack": "^0.9.0",
"nativescript-worker-loader": "~0.8.1",
"raw-loader": "~0.5.1",
"resolve-url-loader": "~2.1.0",
"typescript": "~2.4.2",
"webpack": "~3.8.1",
"webpack-bundle-analyzer": "^2.8.2",
"webpack-sources": "~1.0.1"
}
}
my build.gradle is this:
`// Top-level build file where you can add configuration options common to all sub-projects/modules.
buildscript {
repositories {
google()
jcenter()
}
dependencies {
classpath 'com.android.tools.build:gradle:2.3.3'
classpath 'com.google.gms:google-services:3.1.2'
}
}
allprojects { repositories { google() jcenter() } }
task clean(type: Delete) { delete rootProject.buildDir }`
my project is with android.
Any body can help me?
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
configuring project ':app' failed to find Build Tools revision
$ gradle FAILURE: Build failed with an exception. * What went wrong: A problem occurred configuring project ':app'. > The SDK directory '/home/ ......
Read more >(SOLVED) A problem occurred configuring project ':app'.
Hello guys I am very new to android studio and a beginner in app development. ... (SOLVED) A problem occurred configuring project ':app'....
Read more >Create a cpp support project, but got 'Error:A problem ...
A problem occurred configuring project ':app'. > java.lang.NullPointerException (no error message) * Try: Run with --info or --debug option to get more log ......
Read more >org.gradle.api.ProjectConfigurationException: A problem ...
A problem occurred configuring project ':app'. Failed to notify project evaluation listener. java.util.NoSuchElementException (no error message)
Read more >Error building android: A problem occurred configuring project
I'm building apk from an android project exported from Cocos Creator V2.4.3 but getting the below error with Gradle A problem occurred ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ran into this issue but not during an upgrade (I’m still using TNS 3.4.2). Had to update my firebase after-prepare hook to use google services 3.1.1. The “No match found” error was saying that during the build it couldn’t find google services 3.1.2. I’m not sure why this was the case cause I see the 3.1.2 jar in my local gradle repo and I have Google Repo support in Android Studio.
@torvicv I believe i am having a similar problem, did you just run npm update? what exactly did you update?