Closed ZacSweers closed 1 year ago
Thanks for the report, we are looking into this issue.
I figured out the cause of the issue. It's because intune plumbs the MamifyExtension
straight into an input property of the mamify task. Gradle then tries to snapshot these inputs, and any string inputs not defined or with a convention cause a crash in gradle.
The solution is to make the properties in the extension be annotated accordingly with @Input
and have reasonable defaults set for their conventions in the plugin constructor. Then the input in the task should just be marked as @Nested
instead.
I think it's worth mentioning that this reproduces instantly and 100% of the time. I can't really see how this would have passed any unit or manual test.
This issue should now be fixed in the 9.7.0 SDK
Describe the bug: When testing the new preview implementation in 9.4.0, a strange crash comes from deep in Gradle that suggests it is unable to properly snapshot the
MamifyClassesTask
input properties.To Reproduce Steps to reproduce the behavior:
MamifyClassesTask
run.Expected behavior: I expect it not to crash Gradle's infrastructure.
Screenshots and logs: See above
Smartphone (please complete the following information): N/A
Intune App SDK for Android (please complete the following information):
Additional context: I am posting a separate issue with some feedback and findings that may have a clue.