search

microsoftconnect / intune-app-wrapping-tool-android

Use the Intune App Wrapping Tool for Android to enable Android apps to be managed by Microsoft Intune
28 stars 11 forks source link

Getting error on building apk #31

Closed donny08 closed 4 years ago

donny08 commented 5 years ago

Describe the bug: Application wrapping in progress. App Wrapping Tool Version: 1.0.2554.2 [main manifest:5] Manifest has more than one /manifest/uses-permission[@name=android.permission.INTERNET] element. C:\Users\CHARLE~1\AppData\Local\Temp\IntuneAppWrappingTool-2941818379944089507\sourceApk\res\values\public.xml:1104: error: resource 'drawable/$avd_hide_password0' has invalid entry name '$avd_hide_password0'. Invalid character '$avd_hide_password0'. C:\Users\CHARLE~1\AppData\Local\Temp\IntuneAppWrappingTool-2941818379944089507\sourceApk\res\values\public.xml:1105: error: resource 'drawable/$avd_hide_password1' has invalid entry name '$avd_hide_password1'. Invalid character '$avd_hide_password1'. C:\Users\CHARLE~1\AppData\Local\Temp\IntuneAppWrappingTool-2941818379944089507\sourceApk\res\values\public.xml:1106: error: resource 'drawable/$avd_hide_password2' has invalid entry name '$avd_hide_password2'. Invalid character '$avd_hide_password2'. C:\Users\CHARLE~1\AppData\Local\Temp\IntuneAppWrappingTool-2941818379944089507\sourceApk\res\values\public.xml:1107: error: resource 'drawable/$avd_show_password0' has invalid entry name '$avd_show_password0'. Invalid character '$avd_show_password0'. C:\Users\CHARLE~1\AppData\Local\Temp\IntuneAppWrappingTool-2941818379944089507\sourceApk\res\values\public.xml:1108: error: resource 'drawable/$avd_show_password1' has invalid entry name '$avd_show_password1'. Invalid character '$avd_show_password1'. C:\Users\CHARLE~1\AppData\Local\Temp\IntuneAppWrappingTool-2941818379944089507\sourceApk\res\values\public.xml:1109: error: resource 'drawable/$avd_show_password2' has invalid entry name '$avd_show_password2'. Invalid character '$avd_show_password2'.

donny08 commented 5 years ago

@rygo-msft Any help with this

rygo-msft commented 5 years ago

Hi @donny08, can you please attach the full log file. There should be a message at the end of wrapping that describes the log file location. It should look like Verbose logs can be found at: <filepath>

rygo-msft commented 4 years ago

Closing this issue because we need more information. If you can provide the verbose log file, we can reopen the issue.