Attribution Android apps in the Chinese domestic market Best practice for viewing attribution data in AppsFlyer. (I accidentally discovered that right-clicking on this name will replace it with the path to the folder containing adle, but if you cancel and start editing the configuration again, it will still appear as just the project name.)Īfter making this change, the configuration built as expected, and I observed that only one java.exe was launched, using the same JDK path as when I ran tasks from the 'Gradle' panel in the UI.At a glance: Attribution of Android devices without GAID by using OAID or IMEI. In this case, the content of the field is just the project name, and is shown with subtly different background/foreground colours. However, what I should have done was follow the pattern in existing configurations, where the Gradle project: was specified as a 'registered project', by clicking the 'folder' icon to the right of the field, highlighted in green in the following image. (I did this by clicking the ellipsis (.) button to the right of the field, but I could also have entered it directly.) The cause turned out to be that I had defined a new configuration in the 'Run/Debug Configurations' dialog and put the full path to the adle file in the Gradle project: field, as follows. I also noticed (using Process Explorer, since I'm on Windows) that, in the failing case, IntelliJ launched a number of java.exe Gradle daemon processes, and that there were definitely no daemon processes running before I tried to start my build. I couldn't make IntelliJ's embedded JRE be first on my path, because I needed that to be the JDK for various reasons, so I needed another solution. Re-ordering my path caused it to use yet another 'unwanted' version of Java, so it was clearly using the path to choose what to run, but it wasn't clear why.

The Wanted Java version happened to be a system-wide install of the JRE, and not the JDK I had configured for the project, nor the value set for JAVA_HOME, which made me very suspicious (and confused).

I found several similar error reports online but none had the IDEA embedded JRE as the Wanted version. My problem was similar to yours in that the Wanted context had the javaHome as the path to the JRE embedded in the IDEA install folder, and the Actual context had it as the first version of Java on my path. I found this question while investigating a similar problem, and I solved mine, so maybe my experience will help.

Android studio gradle context mismatch