Closed sn-michiyo closed 6 months ago
Hi @sn-michiyo Thank you for reaching out on this topic I have confirmed that the option "Verify" is intended to detect potential plugin bugs, and not application bugs. So, enabling this feature will result in a build time error, instead of a runtime crash. As of now you are not able to manually generate a failed verify. ref: https://learn.microsoft.com/en-us/mem/intune/developer/app-sdk-android-phase3#verification
intunemam {
verify = true
}
**Example Sequence/response from Gradle Build output --debug:
2024-04-30T12:39:37.203-0700 [WARN] [com.microsoft.intune.mam.BuildTimeMamifier] **Verifying classes**
2024-04-30T12:39:37.203-0700 [INFO] [com.microsoft.intune.mam.TransformationUnit] **Verifying classes for** C:\Users\ChismanRaheem\.gradle\<plugins*>
2024-04-30T12:39:45.647-0700 [INFO] [com.microsoft.intune.mam.BuildTimeMamifier] **verification took 8 seconds**
Intune Android App SDK [Gradle Build Plugin] Issue
Questions to Ask Before Submission
Summary
Our app integrates the Android Intune SDK. We saw the verification tool. This looks extremely useful; we would like to integrate it into our CI pipeline. To do so, we need to force it to detect an error so we can make sure that CI will report the error to us.
We have been unable to get
verify
to fail. We learned in https://github.com/msintuneappsdk/ms-intune-app-sdk-android/issues/225 that using the incorrect javassist version will not be detected by this plugin. How can we force a problem thatverify
is able to detect?Details
Logs
NA