Status Update
No update yet.
Comments
fa...@google.com
This error shows up when there is a module in your project whose .iml file does not contain:
external.system.id ="GRADLE"
Can you please check your .iml files? Also, instead of opening the project, *import* it, that will completely rewrite your .iml files and you won't see that error again.
Can you please check your .iml files? Also, instead of opening the project, *import* it, that will completely rewrite your .iml files and you won't see that error again.
fa...@google.com
[Deleted User] <[Deleted User]>
I can confirm that it works with AS 0.8.14 if I do
1) open AS,
2) delete the Gradle Java modules from the project,
3) re-import the Gradle Java modules to the project,
4) close AS,
5) re-open AS.
In that case AS does not *not* complain about Gradle Java modules to be non-Gradle Java modules, and I've confirmed that the generated *.iml files containexternal.system.id ="GRADLE".
However, if I do
6) close AS,
7) delete the *.iml files,
8) re-open AS,
then AS again complains *although* the generates files again containexternal.system.id ="GRADLE". It seems that the problem is related to "open" vs. "import". In the latter instructions, the *.iml files seem to get implicitly generated because the Gradle Java modules are referred to from setting.gradle.
Can it be that AS is somehow performing the check for non-Gradle Java modules before the *.iml files are generated in case of just opening (instead of importing) the project?
1) open AS,
2) delete the Gradle Java modules from the project,
3) re-import the Gradle Java modules to the project,
4) close AS,
5) re-open AS.
In that case AS does not *not* complain about Gradle Java modules to be non-Gradle Java modules, and I've confirmed that the generated *.iml files contain
However, if I do
6) close AS,
7) delete the *.iml files,
8) re-open AS,
then AS again complains *although* the generates files again contain
Can it be that AS is somehow performing the check for non-Gradle Java modules before the *.iml files are generated in case of just opening (instead of importing) the project?
ho...@gmail.com
I see what is happening now. Yes, you are right. This is an issue with "open". I think I know how to fix this issue.
nr...@gmail.com
Thanks for the confirmation. On a more or less related note, as this would not have happened if I was committing the *.iml files, what is your recommendation WRT this? I know about [1] which recommends to share "All the .iml module files", but it's kind of annoying that these files get rewritten if e.g. dependencies change in build.gradle. In general, most of the *.iml files seem to be duplicate content WRT the build.gradle files and can be derived from them. So, should we commit *.iml files for Gradle Android modules to Git?
[1]https://intellij-support.jetbrains.com/entries/23393067
[1]
jk...@gmail.com
It is better not to add iml files to source control. For regular IDEA projects is OK because .iml files are the source of truth for project configuration. In the case of Android projects, the source of truth is gradle.build files, and .iml are generated from them every time you sync your project with Gradle.
[Deleted User] <[Deleted User]>
Thanks for the clear recommendation!
fi...@gmail.com
@5 As you seem to know what the problem is, would it be appropriate to change the status from "NeedsInfo" to "Accepted"?
ko...@gmail.com
This issue is fixed in Studio 1.2.
pe...@gmail.com
It also happens if there are comments in .iml file like:
<!----------- My comment -------------->
<!----------- My comment -------------->
pi...@gmail.com
I just received this error from AS 1.2.1.1 and I do not have any non-Gradle Java modules in my project.
I have one main android application + six Android libraries.
We do not commit our .iml files to source control.
I have one main android application + six Android libraries.
We do not commit our .iml files to source control.
da...@gmail.com
I received the same error in version 1.3.2.
sa...@gmail.com
I received this error on 2.1.2.
jo...@gmail.com
[Comment deleted]
ju...@gmail.com
received this error in 2.3 canary 2
ka...@gmail.com
I am receiving this error in AS 2.3 Canary 2 after doing File->Invalidate Caches->Restart. Mine is a CMake project. This error is not very useful, since the project eventually builds anyway.
[Deleted User] <[Deleted User]>
[Comment deleted]
da...@gmail.com
I am seeing this with AS 2.3 Beta 1 as well. Since this issue has been closed for some time, I went ahead and created a new issue @ https://code.google.com/p/android/issues/detail?id=230550&thanks=230550&ts=1482021669
ja...@gmail.com
#18 & #19: Did you happen to get this error after switching to Gradle 3.2?
And are you, by any chance, using the com.github.dcendents.android-maven plugin? I upgraded from 1.4.2 of that to 1.5, and updated to Gradle 3.2 at the same time, and I'm seeing the error even after downgrading to AS 2.2.3.
I'm in the process of doing a clean install now, and then I'll be trying reverting back to the older version of both, to see if that changes anything.
And are you, by any chance, using the com.github.dcendents.android-maven plugin? I upgraded from 1.4.2 of that to 1.5, and updated to Gradle 3.2 at the same time, and I'm seeing the error even after downgrading to AS 2.2.3.
I'm in the process of doing a clean install now, and then I'll be trying reverting back to the older version of both, to see if that changes anything.
ph...@gmail.com
I don't know what's changed, but after a clean install, and removing ALL .iml files, after an initial complaint on opening the project, it rebuild all the .iml files and now seems fine. It's weird that last night, I tried making a brand-new project, and got the same results, but I'll take what I can get.
That said, it seems interesting to me that several people at once all seemed to run into the same thing. There may be something going on, still.
That said, it seems interesting to me that several people at once all seemed to run into the same thing. There may be something going on, still.
pa...@catchyour.com
The issue is still exist in android studio 3.0.1
pa...@catchyour.com
Same here on android studio 3.0.1
de...@gmail.com
Same here on android studio 3.0.1
dv...@gmail.com
Same here on android studio 3.0.1
ma...@leviarto.com
The same in Android 3.1
d6...@gmail.com
also the same in Android 3.1
ba...@gmail.com
where can i find java gradle module?
pt...@gmail.com
same error in Android Studio 3.1.2
al...@gmail.com
Msg Error in Android Studio v 3.1.2 :
6:48 PM Unsupported Modules Detected: Compilation is not supported for following modules: AndroidStudioProjects. Unfortunately you can't have non-Gradle Java modules and Android-Gradle modules in one project.
I do not have any non-Gradle Java modules in my project.
6:48 PM Unsupported Modules Detected: Compilation is not supported for following modules: AndroidStudioProjects. Unfortunately you can't have non-Gradle Java modules and Android-Gradle modules in one project.
I do not have any non-Gradle Java modules in my project.
gr...@gmail.com
The error occurs also in:
Android Studio 3.1.4
Build #AI-173.4907809, built on July 23, 2018
JRE: 1.8.0_152-release-1024-b01 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 4.15.0-32-generic
I am not sure, but I believe this causes further errors which are quite problematic. I have several projects with this issue: in all of them, some dependencies that are defined in a module's build.gradle file cannot be resolved by AS. Actually, the dependencies are resolved and downloaded from the repositories and show up under "External Libraries" in Project view. However, everywhere I try to use any class from those dependencies... I get a "Cannot resolve symbol XYZ". So I end up stuck with unresolved imports, no way to navigate through classes, etc.
The wierdest thing, though, is that the app compiles fine and runs in a device. It's just AS cannot resolve symbols from well-resolved dependencies.
Project structure overview:
- "app" Android application module (Gradle); depends on "commons", "annotations" and "processor" modules -> *gets detected as non-Gradle*
- "commons" Android library module (Gradle) with common utils, views, dependencies, etc.
- "annotations" java module (Gradle)
- "processor" java module (Gradle)
The symbols that are not resolved by AS come from dependencies defined in the "commons" module.
I have invalidated caches, deleted .idea and .gradle folders, re-downloaded the project, deleted ~/.gradle/caches folder, deleted *.iml files... no luck whatsoever.
Any hints on this issue? Do you believe the "Unsupported Modules Detected" error has anything to do with the "Cannot resolve symbol" issue?
Thanks a lot and best regards.
Android Studio 3.1.4
Build #AI-173.4907809, built on July 23, 2018
JRE: 1.8.0_152-release-1024-b01 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 4.15.0-32-generic
I am not sure, but I believe this causes further errors which are quite problematic. I have several projects with this issue: in all of them, some dependencies that are defined in a module's build.gradle file cannot be resolved by AS. Actually, the dependencies are resolved and downloaded from the repositories and show up under "External Libraries" in Project view. However, everywhere I try to use any class from those dependencies... I get a "Cannot resolve symbol XYZ". So I end up stuck with unresolved imports, no way to navigate through classes, etc.
The wierdest thing, though, is that the app compiles fine and runs in a device. It's just AS cannot resolve symbols from well-resolved dependencies.
Project structure overview:
- "app" Android application module (Gradle); depends on "commons", "annotations" and "processor" modules -> *gets detected as non-Gradle*
- "commons" Android library module (Gradle) with common utils, views, dependencies, etc.
- "annotations" java module (Gradle)
- "processor" java module (Gradle)
The symbols that are not resolved by AS come from dependencies defined in the "commons" module.
I have invalidated caches, deleted .idea and .gradle folders, re-downloaded the project, deleted ~/.gradle/caches folder, deleted *.iml files... no luck whatsoever.
Any hints on this issue? Do you believe the "Unsupported Modules Detected" error has anything to do with the "Cannot resolve symbol" issue?
Thanks a lot and best regards.
ev...@gmail.com
Same error in 3.2.1
Did some research and this was the outcome after trying in Windows & Mac.
When importing a project you have a screen giving 2 options:
- Create project from existing sources
- Import project from external model
Inside the "Import project from external model" there are 2 more options:
- Android Gradle
- Gradle
If you select "Android Gradle" everything is fine, no false positive at all.
If you select Gradle you will get the false positive error message every time you open that project in Android Studio.
Did some research and this was the outcome after trying in Windows & Mac.
When importing a project you have a screen giving 2 options:
- Create project from existing sources
- Import project from external model
Inside the "Import project from external model" there are 2 more options:
- Android Gradle
- Gradle
If you select "Android Gradle" everything is fine, no false positive at all.
If you select Gradle you will get the false positive error message every time you open that project in Android Studio.
[Deleted User] <[Deleted User]>
same error in 3.5.1
lt...@gmail.com
Same error in 4.0.0
an...@gmail.com
Same issue I am facing every single time I open my project in android studio 4.0.0
hw...@gmail.com
AS 4,0,1
for one of older project
deleted .idea and .gradle folders, re-downloaded the project, deleted ~/.gradle/caches folder, deleted *.iml files..
work ok.
for one of older project
deleted .idea and .gradle folders, re-downloaded the project, deleted ~/.gradle/caches folder, deleted *.iml files..
work ok.
za...@gmail.com
+1
ma...@gmail.com
This still happens with AS 4.0.1. All of my *.iml files specify 'external.system.id ="GRADLE"', and the Java modules build
when I double-click on the "build" gradle task - but the IDE can't build the Java modules itself. Better to use a Makefile for
building I guess ...
when I double-click on the "build" gradle task - but the IDE can't build the Java modules itself. Better to use a Makefile for
building I guess ...
he...@richardcooke.io
who solved this issue on the latest versions of AS, please share your actions
la...@gmail.com
deleted
pr...@google.com
If you get this message it is unlikely to be the same old issue. Please file a new bug and, if possible, share your idea.log files (Help | Show Log...). Thank you!
tl...@gmail.com
this is happening here too, nothing works, I'm using Android Studio Ladybug Feature Drop | 2024.2.2 Canary 1 on a mac m2
bug reported
bug reported
ro...@gmail.com
th...@gmail.com
+1
da...@gmail.com
Will this be ever fixed?
da...@gmail.com
+1 please give us ETA. Thank you
[Deleted User] <[Deleted User]>
+1
fr...@googlemail.com
+1
ch...@gmail.com
+1
fu...@gmail.com
I also have this problem, panicked because I thought my account was hacked, realized that this request hasn't been resolved in the last 8 years...
lu...@gmail.com
+1
cz...@myszef.com
+1
dz...@gmail.com
+1
pu...@gmail.com
+1
ko...@gmail.com
+1
li...@gmail.com
+1
ro...@gmail.com
+1
ak...@gmail.com
+1
ka...@gmail.com
+1
ta...@gmail.com
+1
p....@gmail.com
+1
ar...@google.com
ku...@gmail.com
+1
by...@gmail.com
+1
bl...@gmail.com
+1
dg...@gmail.com
+1
pa...@gmail.com
Is this going to be solved anytime?
ar...@google.com
wi...@gmail.com
+1
ro...@gmail.com
+1
this ticket is 5 years old.
this ticket is 5 years old.
th...@pulsify.io
+1
ch...@gmail.com
+1
sz...@gmail.com
+1
de...@gmail.com
+1
ma...@gmail.com
+1 and say no to modern salvery
[Deleted User] <[Deleted User]>
+1
da...@gmail.com
+1
br...@gmail.com
+1
[Deleted User] <[Deleted User]>
+ 1
we...@gmail.com
+100
ra...@linnify.com
+1
iw...@gmail.com
+99999999999
ju...@gmail.com
+1
su...@gmail.com
Will this be ever fixed?
na...@gmail.com
+1
ga...@fassilavalle.com.ar
+1
ma...@gmail.com
+1
em...@gmail.com
+1
aj...@gmail.com
+1
da...@gmail.com
+1
th...@gmail.com
+1
ge...@gmail.com
+1
gu...@gmail.com
+1
sj...@gmail.com
+1
th...@gmail.com
+1
jo...@providence.org.c-03oege15.appstempdomain.goog
+1
si...@quitedo.com
+1 like it makes any difference
lu...@brandbastion.com
+1
lg...@gmail.com
+1
de...@gmail.com
+1
ni...@gmail.com
+1
al...@sada.com
+1
pa...@gmail.com
+1
ce...@gmail.com
+1
yupp same here.. don't have contact with the client anymore and would like to remove myself from the project
yupp same here.. don't have contact with the client anymore and would like to remove myself from the project
vi...@gmail.com
6 years+ now.. this is dragging for such simple feature
fa...@gmail.com
+1 ... 6 years, isn't that hard is it? Maybe you can ask ChatGPT to make the code :)
ku...@google.com
ku...@google.com
ku...@google.com
ef...@gmail.com
So well, as almost a decade passed without fixing this, I just created a cloud project called "PLS-FINALLY-FIX-BUG-35903415" and started adding all validated Google executive, internal and employee accounts to it. And they won't be able to remove themselves until this is fixed. Maybe if the bug bugs them too, not just us, it will be fixed. Maybe I can change their role from "Viewer" to "Editor", then back, every other day, so they will get notified about my awesome new project.
Yaay: imgur . com/a/rnAFuO8
¯\_(ツ)_/¯
Yaay: imgur . com/a/rnAFuO8
¯\_(ツ)_/¯
sa...@gmail.com
+1 ^^ brilliant
ca...@gmail.com
No one fix this. LOL
co...@maxcorbeau.com
FOR THE LOVE OF GOD FIX THIS !!!
Now I can't use Power BI because of this: someone has added me to GCP project integration-test-project / sixth-utility-385100 without me asking. I can't leave it, and when trying to use Power BI BigQuery connector, despite pointing it to another project, I get the below error I can't bypass (my guess is that the connector checks admin permissions for all projects I have access to and fails). Granted this is an issue with Power BI to start with, but it's made worse by the fact that we can't leave GCP projects.
DataSource.Error: ODBC: ERROR [42000] [Microsoft][BigQuery] (100) Error interacting with REST API: Access Denied: Project sixth-utility-385100: User does not have bigquery.jobs.create permission in project sixth-utility-385100 error
ju...@gmail.com
This is ridiculous that it is not possible to do this. One should always be able to remove oneself from a project. The fact that this is open for almost EIGHT YEARS now is plainly quite rude.
sd...@gmail.com
We are all the way from 2016 to 2023. I dont know for how many years more this thread goes on. I too have a ghost project. No idea how I got it and I have not a single permission to do anything but stays in my projects list. Why are you letting someone add sh*t into my plate. I don't want it. Please implement this much requested feature.
an...@gmail.com
This is embarrassing. I was denied access from a project after quitting a job (could no longer tolerate the manager - a manipulative, passive-aggressive individual), and now he can grant me access again anytime he wants so that I will appear to be associated with this project - for the better (for them), or for the worse (for me). In the name of all the people who requested this, please fix this issue. It's a very big problem. Thank you.
r....@gmail.com
It is so stupid that this issue is still open.
ra...@gmail.com
+1
re...@gmail.com
+1
pr...@gmail.com
+1
mi...@gmail.com
+1
al...@gmail.com
+1
sz...@googlemail.com
+1
vo...@gmail.com
+1
ba...@hikari-sas.fr
+10000000000000000000000000000
kr...@gmail.com
+1
qu...@multiminds.eu
+1
ko...@gmail.com
+1
as...@gmail.com
I was added as an editor for a project from a start-up. They dissolved the company, and the owner's email is bouncing. It's ridiculous that this feature request is still open. At least there should be a way to hide this project from my GCP dashboard and drop-downs.
sy...@abloomai.com
This is asinine. A former employee made themselves the project owner, we have sent legal paperwork from court asking them to be removed to the project and migrate our project to a new account and Google refuses to help.
go...@gmail.com
I'm linked to old projects that I can't delete but want to remove myself from them permanently. How this is not possible is beyond me...
ma...@gmail.com
+1
al...@gmail.com
+1
al...@gmail.com
Comment has been deleted.
ka...@gmail.com
Hello,
I was made an Editor in one of these GC projects 14 (FOURTEEN. FOURTEEN F'ING YEARS GOOGLE. GET THAT RIGHT ) years ago alright. Now because Editor roles don't have permission to modify roles, they cannot remove themselves from the project. At least that's my case. Billing Support say they can't help. The owner of the account is not responding because the company f'ing shut down !!!
I simply see this as a security threat, I don't want to be associated with a project. You are causing so much trouble to me and other people.
Why won't you let us remove ourselves from a project ? We wish we could take you to the court for the inconvenience, trouble and suffering you are causing here. How would you feel if somebody kept their garbage in your backyard for 15 years by force, not letting you clean it up. You are causing so much pain
LET US SIMPLY BE ABLE TO LEAVE A PROJECT OMG
ka...@gmail.com
get your sister, friends and family to vote and +1 this thread, anyone that is affected by this bug. This is not a feature request this is a core functionality that's missing, it's not just inconvenient, it's CRIMINAL to prevent your customers from leaving a project / service against their will.
let's all gather and take a look at the way Google treats their own GCP community. It's an embarrassment.
ba...@google.com
su...@gmail.com
Finally, someone with @google.com has interacted with this issue.
va...@google.com
Hi,
We have found that this issue is a duplicate of
To avoid duplicate reports, I'm going to close this issue, which will no longer be monitored. In case you want to report a new issue, please do not hesitate to create a new issue on the
Thank you.
jo...@gmail.com
It is astounding that this issue and it's 7 duplicates are consistently ignored by Google. It should be basic functionality to have the rights to remove yourself from a project. Every platform I know has a feature like that in similar scenarios. I'm a software dev and I'd be ashamed if someone pointed out an omission like that in our own platform and for sure it would be fixed ASAP because it can have many unwanted cluttering and unwanted associations as many have pointed out above and in the duplicates.
The reason for duplicates to exist is because the issue which is annoying the hell out of a lot of developers has not been addressed in over what is it ? 13 Years, what a disgrace
The reason for duplicates to exist is because the issue which is annoying the hell out of a lot of developers has not been addressed in over what is it ? 13 Years, what a disgrace
vi...@gmail.com
+1 been waiting for this for years
mz...@gmail.com
+10 is this really so difficult to implement? As a owner of my account I want to have possibility to manage my own GCP projects I am in. I could invite all of the world to all projects and spam them their space completely.
Thank you for considering to implement this feature.
Thank you for considering to implement this feature.
wb...@razoyo.com
Can someone from Google at least give a status update here? It incredible that I am forced to live with projects in my resources that I have nothing to do with anymore and no contact with the project owner. It makes is much more difficult to audit my projects.
qu...@gmail.com
+1
vi...@0x1.now
After 8 years, this problem is still present. Google you are doing well :(
ni...@gmail.com
+1
mv...@gmail.com
+1
zj...@gmail.com
+1
ya...@gmail.com
+1
da...@gmail.com
here in 2025 ... This is disrespectful!
bu...@gmail.com
+1
Description
1. Somebody added me to a Google Cloud project (accidentally)
2. I see that unknown project in my list of projects
2.1: (optional) I panic(), because I thought that somebody hacked my account
3. Try to delete myself from the project, using the web console
What is the expected output? What do you see instead?
I want to be removed from the project, but, because I don't have permissions to do so, I can't.
What version of the product are you using? On what operating system?
Google Cloud web console.
Please provide any additional information below.
I'm don't have any relation with the owners of the project. I sent them already an email, asking to be removed, but they haven't do that (at this moment, at least).
On the other hand, I don't know if this bug could be used to harvest emails of GCP users, to later attempt to hack them in another way.
Also I never received any email asking me for approving the new project. That should be a minimum countermeasure for this problem.