It does seem to be a tooling issue so perhaps it s...
# coroutinesa
ansman
07/25/2019, 2:29 PMIt does seem to be a tooling issue so perhaps it should be reported to the Android team
m
mbonnin
07/25/2019, 2:30 PMCan you somehow reproduce it ?
a
ansman
07/25/2019, 2:31 PMIt’s very sporadic. When I get it happens until I shuffle things around in the build scripts
m
mbonnin
07/25/2019, 2:31 PMBut is it bound to an apk? Like once you have it, it happens forever on that same apk ?
a
ansman
07/25/2019, 2:31 PMYeah, exactly
ansman
07/25/2019, 2:32 PMIt does seem like the service loader file isn’t packaged in the APK for those builds
m
mbonnin
07/25/2019, 2:33 PMThat's weird. It's going to be hard to investigate if there's no way to reproduce it. Maybe if you come up with a few command lines that can reproduce the problem ?
a
ansman
07/25/2019, 2:33 PMYeah, I wish I could reproduce it
m
mbonnin
07/25/2019, 2:33 PMActually, does it happen if you build from the command line ? That might be an idea/Android Studio thing as well
a
ansman
07/25/2019, 2:34 PMYes, it happens for our release builds too which are built from the command line
ansman
07/25/2019, 2:35 PMIt does seem to be fixed if I switch my
implementationapiansman
07/25/2019, 2:38 PMI just did a super clean, removing cache. Let’s see if it happens still
ansman
07/25/2019, 2:39 PMIt does only happen for me
ansman
07/25/2019, 3:04 PMFingers crossed that this solved the issue
🤞 1
ansman
09/09/2019, 12:38 PMI fixed it by clearing the build cache
👍 1
3 Views