Post AQdTEIdDZLK6K4NST2 by Aurimas@androiddev.social
 (DIR) More posts by Aurimas@androiddev.social
 (DIR) Post #AQC3IoJLspzteoepjk by eighthave@social.librem.one
       2022-12-02T10:30:56Z
       
       0 likes, 0 repeats
       
       @Aurimas I'd like to help improve the verification support in Android Studio.  How would you recommend I engage?  I've had mixed results submitting things to official Android channels, mostly I get silence, so I'd like to know if there is a channel where you think my feedback, testing and experiences would be heard.
       
 (DIR) Post #AQCVPiwJ3EWBjzxlwW by Aurimas@androiddev.social
       2022-12-02T15:45:54Z
       
       0 likes, 0 repeats
       
       @eighthave what do you mean by studio verification?
       
 (DIR) Post #AQCcH7AOIyknx9OQWe by eighthave@social.librem.one
       2022-12-02T17:02:48Z
       
       0 likes, 0 repeats
       
       @Aurimas I mean Android Studio should handle when Gradle throws errors based on the verification metadata.  Right now, our app is stuck in some mode where command line runs all work fine with verification, but Android Studio errors out with bizarre stacktraces.  So to use this app in  Android Studio, you have to delete gradle/verification-metadata.xml
       
 (DIR) Post #AQCdiw3BKQzPXTqnxY by Aurimas@androiddev.social
       2022-12-02T17:19:01Z
       
       0 likes, 0 repeats
       
       @eighthave Could it be https://github.com/gradle/gradle/issues/19089 ? Are you on Gradle 7.4?
       
 (DIR) Post #AQdEnuaOwqSirMaDPU by eighthave@social.librem.one
       2022-12-15T13:17:01Z
       
       0 likes, 0 repeats
       
       @Aurimas I tried updating to 7.5.1, and it seemed to have fixed it for a while.  But it came back... 😭 its an intermittent bug, so hard to predict. It makes the most Java error message ever:"Caused by: java.lang.IllegalStateException: Unexpected state for resolution: Unknown"
       
 (DIR) Post #AQdTEIdDZLK6K4NST2 by Aurimas@androiddev.social
       2022-12-15T15:58:38Z
       
       0 likes, 0 repeats
       
       @eighthave maybe file a bug if you are able to capture the stacktrace?