F4uzan / HgLauncher

A launcher for a slow day.
https://f4uzan.github.io/HgLauncher
GNU General Public License v3.0
73 stars 22 forks source link

Unable to resolve dependency for ':app@debug/compileClasspath': #27

Closed sherlockbeard closed 5 years ago

sherlockbeard commented 5 years ago

ERROR: Unable to resolve dependency for ':app@debug/compileClasspath': Could not resolve project :slidinguppanel:library. Show Details Affected Modules: app

ERROR: Unable to resolve dependency for ':app@debugAndroidTest/compileClasspath': Could not resolve project :slidinguppanel:library. Show Details Affected Modules: app

ERROR: Unable to resolve dependency for ':app@debugUnitTest/compileClasspath': Could not resolve project :slidinguppanel:library. Show Details Affected Modules: app

Not sure how to properly build the project . i love this launcher i want to contribute. plz help and guide me .

F4uzan commented 5 years ago

Hi! Thanks for taking your time to report the issue.

This usually happens if the SlidingUpPanel library is not properly initialised. You can alternatively try cloning/downloading it from https://github.com/F4uzan/AndroidSlidingUpPanel and then placing it under the 'slidinguppanel' folder.

I may also need to know what you're compiling the launcher on. Is it the latest Android Studio?

sherlockbeard commented 5 years ago

thanks for replying . i did what you told me to do . but the error is still present . and i am using 3.3.2 .

F4uzan commented 5 years ago

Can you check what contents 'slidinguppanel' have? This doesn't seem to be an Android Studio issue, so I presume that narrows down the issue a tad.

sherlockbeard commented 5 years ago

this time zero sync error . but while building i am getting this compile time error error

libary

depending

F4uzan commented 5 years ago

The structure of 'slidinguppanel' is wrong. Can you cut/move the contents of 'AndroidSlidingUpPanel' to 'slidinguppanel'? It seems that you have placed it incorrectly.

You shouldn't need to toy around the modules manually.

sherlockbeard commented 5 years ago

@F4uzan thank you . for helping. the issue finally resolved it was a great debugging experience.