apk

Modify Android App Bundle (aab) Contents before deploying

不打扰是莪最后的温柔 提交于 2020-08-19 10:44:13
问题 We have a build and release pipeline (Azure Devops) that deploys our APK Android app to various appcenter.ms environments. During the release process we unpack the apk, modify the contents with environment specific configuration, and then re-pack the apk. Now that we are trying to do this with an Android App Bundle (AAB), we can no longer use apktool. How can we achieve the same thing with AAB that we could with APK? This is a snippet of our working apk version of the script ## NOTE STUFF IS

Where is the .apk file output after signing it via Azure android signing build pipeline?

折月煮酒 提交于 2020-08-10 04:51:28
问题 I'm signing an apk file in a build pipeline using the Azure 'Android Signing' task but I cannot see the path in which the signed apk is output to. I've exported the entire root of the build pipeline as .zip file, but a signed .apk file does not exist. What's even more confusing is that the Android Signing task is passing , so the signed .apk must be somewhere right? The question is where! Thanks 回答1: Android Signing' task did not create a new apk. The signed apk is still in the output folder

error: command 'gcc' failed with exit status 1 when installing pip packages on alpine docker image

若如初见. 提交于 2020-08-09 06:13:51
问题 I'm attempting transition my base docker image from centos 7 to alpine, however I receive gcc errors when trying to install pip packages. This is a snippet of the error received: Successfully built backports.ssl-match-hostname configobj dpkt iniparse IPy kitchen logmatic-python maxminddb NeuroTools procfs pycparser python-json-logger pyudev repoze.lru scandir scapy Failed to build guppy kiwisolver numpy psutil pygpgme pyliblzma python-ldap pyxattr subprocess32 Installing collected packages:

android signed apk / net.sourceforge.jtds errors

三世轮回 提交于 2020-08-05 08:58:40
问题 I'm trying to build a signed apk (release) using proguard, but when generating the APK android studio reports several warnings related to "net.sourceforge.jtds" like this: Warning:net.sourceforge.jtds.jdbcx.JtdsDataSource: can't find superclass or interface javax.sql.XADataSource Warning:net.sourceforge.jtds.jdbcx.JtdsDataSource: can't find superclass or interface javax.naming.Referenceable ... and finally ends with an error: Error:Execution failed for task ':app

Force to use same certificate to sign different “buildTypes” that are configured for a particular “productFlavor”?

有些话、适合烂在心里 提交于 2020-08-01 17:29:43
问题 Background: I am generating builds using build variant. Below are the configurations: signingConfigs { production { storeFile file("some_path/buildsystem/keystore/some.release.keystore.jks") storePassword "somepassword" keyAlias "somekeyalias" keyPassword "some" v2SigningEnabled false } develop { storeFile file(".some_path./buildsystem/keystore/someother.debug.keystore.jks") storePassword "someother" keyAlias "someotherkeyalias" keyPassword "someother" v2SigningEnabled false } }

Force to use same certificate to sign different “buildTypes” that are configured for a particular “productFlavor”?

安稳与你 提交于 2020-08-01 17:27:26
问题 Background: I am generating builds using build variant. Below are the configurations: signingConfigs { production { storeFile file("some_path/buildsystem/keystore/some.release.keystore.jks") storePassword "somepassword" keyAlias "somekeyalias" keyPassword "some" v2SigningEnabled false } develop { storeFile file(".some_path./buildsystem/keystore/someother.debug.keystore.jks") storePassword "someother" keyAlias "someotherkeyalias" keyPassword "someother" v2SigningEnabled false } }