Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BrutException: could not exec (exit code = -1073741515) when run with 32bit JVM #27

Closed
rygo-msft opened this issue Apr 12, 2019 · 2 comments
Labels
Bug Issue is a valid bug with the AW. Closed - Fixed Issue has been addressed with a verified fix.

Comments

@rygo-msft
Copy link
Collaborator

rygo-msft commented Apr 12, 2019

Failure Message:
App Wrapping fails with the following exception:
com.microsoft.intune.mam.apppackager.utils.AppPackagerException: Failed to load app resource table.
...
brut.androlib.AndrolibException: brut.common.BrutException: could not exec (exit code = -1073741515): [brut_util_Jar_2464172016156763930.tmp ...]

Root Cause:
This seems to correlate to a missing dependency in ApkTool when running in 32bit Java.

Work Around:
This failure can be mitigated by running 64-bit Windows and using 1.0.2676.4 or later.

See iBotPeaches/Apktool#2053 for more information

@msintuneappsdk msintuneappsdk added the Bug Issue is a valid bug with the AW. label May 2, 2019
@rygo-msft rygo-msft changed the title Wrapping fails with BrutException: could not exec (exit code = -1073741515) when run with 32bit JVM Wrapping fails with "Failed to load app resource table." caused by BrutException: could not exec (exit code = -1073741515) when run with 32bit JVM May 13, 2019
@rygo-msft rygo-msft pinned this issue Jun 21, 2019
@rygo-msft rygo-msft changed the title Wrapping fails with "Failed to load app resource table." caused by BrutException: could not exec (exit code = -1073741515) when run with 32bit JVM BrutException: could not exec (exit code = -1073741515) when run with 32bit JVM Jul 8, 2019
@rygo-msft
Copy link
Collaborator Author

The latest release 1.0.2676.4 contains a partial workaround for this issue. This issue should no longer occur on 64 bit systems. 32 bit systems may still experience issues.

@rygo-msft
Copy link
Collaborator Author

The full fix for this is in the 1.0.2896.3 release

@meghandaly meghandaly added the Closed - Fixed Issue has been addressed with a verified fix. label Feb 2, 2021
@rygo-msft rygo-msft unpinned this issue Dec 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Issue is a valid bug with the AW. Closed - Fixed Issue has been addressed with a verified fix.
Projects
None yet
Development

No branches or pull requests

2 participants