Smali Write Error: Cannot Wrap App with Azure Identity Dependencies

[idpetrocheilos]

Questions to Ask Before Submission

1. Does you app launch successfully without wrapping? Yes
2. Have you reviewed the prerequisites for App Wrapping? Yes
3. Does your issue have a solution in the Troubleshooting Guide? No
4. Have you checked the Microsoft Intune App SDK for Android repository for similar issues? Yes
5. Are you using the latest version of the App Wrapper? Yes

Describe the bug:
App containing the following dependencies cannot be wrapped due to "Smali failed while writing smali file to DEX format":

• com.azure:azure-identity
• com.azure:azure-security-keyvault-certificates

Expected behavior:
App is wrapped successfully.
log.txt

[idpetrocheilos]

Hello, can I please have some help on this?

[kanishkaBagga]

@idpetrocheilos - we are looking into this.

[kanishkaBagga]

The problem occurs if the LOB app reaches or nearly reaches the 64K method reference limit of DEX files. In this scenario, the Microsoft Intune Wrapping Tool can't add the necessary Intune code to the app without exceeding this limit.

Install the latest version of the Microsoft Intune App Wrapping Tool for Android.
Enable multidex for your Android app.
Test whether the problem is fixed. If the problem persists, try the following methods in the given order:

Examine the multidex configuration to see whether you specify any classes in the primary DEX file. You may experience problems if too many classes are added to the primary DEX file. For more information, see https://developer.android.com/studio/build/multidex#keep.

To work around this problem, reduce the number of classes that are specified in the primary DEX file.

Enable code shrinking by using ProGuard. For more information, see https://developer.android.com/studio/build/shrink-code#shrink-code

[idpetrocheilos]

Hello and happy new year! I just returned from vacation - please allow some time to review your solutions.

[idpetrocheilos]

Hello,

Unfortunately it didn't work. We enabled multidex and deleted multiple classes from the primary DEX file, but we still get the same issue. I am attaching fresh logs. Is there anything else you can suggest?

Best regards,

newlogs.txt

[kanishkaBagga]

The error logs you’ve shared indicate that there was a failure during the wrapping process of an Android app using the Intune App Wrapping Tool.The error indicates that the wrapping tool could not complete its task due to issues in the earlier stages.

 Smali failed while writing smali file to DEX format: 
 C:\Users\...\ReflectionUtilsMethodHandle.smali.
 ```

This error occurs during the conversion of Smali files to the DEX format.

• Possible Causes:

  • Unsupported or complex methods in the .smali file that the app wrapping tool cannot handle.
  • Conflicts arising from resource reassignments or other changes made during wrapping.

Recommendations for Troubleshooting:

Update Wrapping Tool Version:

• Ensure you are using the latest version of the Intune App Wrapping Tool.

Test Wrapping Without Modifications:

• If you made custom modifications to the APK or Smali files, try wrapping the original APK without changes to isolate the issue.

[idpetrocheilos]

Hello again,

Based on our investigation it appears that wrapping tool is incompatible with the following dependencies:

• com.azure:azure-identity
• com.azure:azure-security-keyvault-certificates

If we disable those, wrapping works. If we enable them, smali fails. I can provide some more logs but can you provide me with a way to do it privately, as I would not like to hand them over publicly.

Best regards,

[idpetrocheilos]

Hello,

Please any update/info on this?

[kanishkaBagga]

@idpetrocheilos , can you share the logs on kbagga@microsoft.com

[idpetrocheilos]

Good morning,

I just emailed you the logs.

Thanks for your time!

[kanishkaBagga]

@idpetrocheilos - We are looking into the logs , will revert ASAP

[idpetrocheilos]

@kanishkaBagga Hello, any update on this?

[idpetrocheilos]

Hello @kanishkaBagga ,

Can we please get an answer on this matter? From our end it seems like a product limitation. We understand that it might need time to get sorted but we could at least get a confirmation that it’s a product issue so that we can move forward and explore other options.

Thank you in advance for your understanding.

[kanishkaBagga]

@idpetrocheilos - I understand , we are working on this internally , will get back to you ASAP