Android build failing to deploy due to "Deploy failed, error: failed to get apk infos"

When building my Android app, I make it all the way to the deploy to Bitrise step where the build then fails with the error “Deploy failed, error: failed to get apk infos”. I believe I have tracked this to line 84 of https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/blob/master/uploaders/apkuploader.go. However the output error of the aapt command, “signal: abort trap”, is not very indicative of the issue. Any help with figuring out what is going on here would be very much appreciated.

[32;1mUploading apk file: /Users/vagrant/deploy/brand-debug-bitrise-signed.apke[0m
analyzing apk
e[31;1mDeploy failed, error: failed to get apk infos, output: package: name='[REDACTED]' versionCode='32' versionName='1.0.18'
sdkVersion:'19'
targetSdkVersion:'26'
uses-permission: name='android.permission.INTERNET'
uses-permission: name='android.permission.CALL_PHONE'
uses-permission: name='android.permission.ACCESS_FINE_LOCATION'
uses-permission: name='android.permission.GET_ACCOUNTS'
uses-permission: name='com.google.android.c2dm.permission.RECEIVE'
uses-permission: name='android.permission.RECEIVE_BOOT_COMPLETED'
uses-permission: name='android.permission.BLUETOOTH'
uses-permission: name='android.permission.BLUETOOTH_ADMIN'
uses-permission: name='android.permission.CAMERA'
uses-permission: name='android.permission.READ_EXTERNAL_STORAGE'
uses-permission: name='android.permission.WRITE_EXTERNAL_STORAGE'
uses-permission: name='android.permission.READ_CALENDAR'
uses-permission: name='android.permission.WRITE_CALENDAR'
uses-permission: name='android.permission.READ_LOGS'
uses-permission: name='android.permission.READ_PHONE_STATE'
uses-permission: name='android.permission.VIBRATE'
uses-permission: name='android.permission.NFC'
uses-permission: name='android.permission.ACCESS_NETWORK_STATE'
uses-permission: name='android.permission.REQUEST_INSTALL_PACKAGES'
uses-permission: name='android.permission.ACCESS_COARSE_LOCATION'
uses-permission: name='android.permission.FOREGROUND_SERVICE'
uses-permission: name='android.permission.WAKE_LOCK'
uses-permission: name='com.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICE'
application-label:'39'
application-label-af:'39'
application-label-am:'39'
application-label-ar:'39'
application-label-as:'39'
application-label-az:'39'
application-label-be:'39'
application-label-bg:'39'
application-label-bn:'39'
application-label-bs:'39'
application-label-ca:'39'
application-label-cs:'39'
application-label-da:'39'
application-label-de:'39'
application-label-el:'39'
application-label-en-AU:'39'
application-label-en-CA:'39'
application-label-en-GB:'39'
application-label-en-IN:'39'
application-label-en-XC:'39'
application-label-es:'39'
application-label-es-US:'39'
application-label-et:'39'
application-label-eu:'39'
application-label-fa:'39'
application-label-fi:'39'
application-label-fr:'39'
application-label-fr-CA:'39'
application-label-gl:'39'
application-label-gu:'39'
application-label-hi:'39'
application-label-hr:'39'
application-label-hu:'39'
application-label-hy:'39'
application-label-in:'39'
application-label-is:'39'
application-label-it:'39'
application-label-iw:'39'
application-label-ja:'39'
application-label-ka:'39'
application-label-kk:'39'
application-label-km:'39'
application-label-kn:'39'
application-label-ko:'39'
application-label-ky:'39'
application-label-lo:'39'
application-label-lt:'39'
application-label-lv:'39'
application-label-mk:'39'
application-label-ml:'39'
application-label-mn:'39'
application-label-mr:'39'
application-label-ms:'39'
application-label-my:'39'
application-label-nb:'39'
application-label-ne:'39'
application-label-nl:'39'
application-label-or:'39'
application-label-pa:'39'
application-label-pl:'39'
application-label-pt:'39'
application-label-pt-BR:'39'
application-label-pt-PT:'39'
application-label-ro:'39'
application-label-ru:'39'
application-label-si:'39'
application-label-sk:'39'
application-label-sl:'39'
application-label-sq:'39'
application-label-sr:'39'
application-label-sr-Latn:'39'
application-label-sv:'39'
application-label-sw:'39'
application-label-ta:'39'
application-label-te:'39'
application-label-th:'39'
application-label-tl:'39'
application-label-tr:'39'
application-label-uk:'39'
application-label-ur:'39'
application-label-uz:'39'
application-label-vi:'39'
application-label-zh:'39'
application-label-zh-CN:'39'
application-label-zh-HK:'39'
application-label-zh-TW:'39'
application-label-zu:'39'
application-icon-120:'res/drawable/ic_launcher.png'
application-icon-160:'res/drawable-mdpi-v4/ic_launcher.png'
application-icon-240:'res/drawable-hdpi-v4/ic_launcher.png'
application-icon-320:'res/drawable-xhdpi-v4/ic_launcher.png'
application-icon-480:'res/drawable-xxhdpi-v4/ic_launcher.png'
application-icon-640:'res/drawable-xxhdpi-v4/ic_launcher.png'
application-icon-65534:'res/drawable-mdpi-v4/ic_launcher.png'
application-icon-65535:'res/drawable-xxhdpi-v4/ic_launcher.png'
application: label='39' icon='res/drawable-mdpi-v4/ic_launcher.png'
application-debuggable
launchable-activity: name='com.[REDACTED]technology.android.golfer.WelcomeActivity'  label='' icon='', error: signal: abort trape[0m

Hi @garrett.steffens!

Sorry to hear about the issue! Could you please include an URL to the build where this is occurring.

Thanks for the reply, @bitce. Here it is: https://app.bitrise.io/build/ede008ae9626aca6#?tab=log

Thanks! Is this issue occurring on the latest version of the step too?

Unfortunately, yes. Tamas reached out yesterday and recommended I try the version you see in that build link however that didn’t help either.

Hi @garrett.steffens,
As we solved this in the Support thread you opened via the on-site chat I’ll be closing this discuss thread :nerd_face:
To have it here as well I’ll include the issue and the steps we took to resolve the issue:
The error message: error: signal: abort trap
The issue was that the stack used to build the project was a MacOS stack on which the aapt tool was trying to write a memory section that it didn’t have right to access.

Steps we took to resolve the issue:

  • Switched to the Linux stack
  • Modified the installation scripts to use apt-get instead of brew
1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.