Repository navigation
Have CLI doctor check permissions on gradlew script #2127
Description
Activity
Hey @Raj29Kumar your comment is not related to this issue. Please create separate issue describing your problem.
I think we can add this check, @cortinico WDYT?
I personally never noticed
gradlewhaving wrong permissions, but yes, this is a simple check we can add anyway@szymonrybczak I will take a look on this one. Just to make sure, Is this something we can add to the
healthchecksor is it some other file?@szymonrybczak I will take a look on this one. Just to make sure, Is this something we can add to the
healthchecksor is it some other file?Yeah, sure
Describe the Feature
I've recently cloned a project on a new computer and
yarn androidwas failing without much explanation, only suggesting I run the cli doctor to check my environment. I did have an issue with it not detecting I had Android SDK 33.0 installed, but it was due to me actually not having the Android SDK Command Line Tools version 10.0 installed.I go on to fix it and now I'm in this interesting state where the cli doctor tells me everything is fine but the android build was still failing with the exact same output. I found out the issue was that I had to
chmod +x gradlewin this new machine. So maybe having the cli doctor check for these permissions could be useful.Possible Implementations
No idea guys, sorry. You are better prepared than me.