如何在一台设备上安装不同版本的安卓应用
第一步:
1. Create the variant dependent strings in your build script
Edit your build.gradle file accordingly:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 | //This line allows parameterization via the terminal and the Gradle VM Options def debugsuffix = System. getProperty( 'debugsuffix' , project.getProperties().get( 'debugsuffix' , null)) def final yourApplicationId = 'your.application.id' android { //In the defaultConfig and all your product flavors create build dynamic variables defaultConfig { applicationId = yourApplicationId //These are the values for the authorities and account types. //Reference them in the java files with e.g. BuildConfig.ACCOUNT_TYPE. buildConfigField "String" , "ACCOUNT_TYPE" , "\"${applicationId}.account\"" buildConfigField "String" , "AUTHORITY" , "\"${applicationId}.provider\"" //Reference them in .xml files. resValue "string" , "account_type" , "${applicationId}.account" resValue "string" , "authority" , "${applicationId}.provider" } productFlavors { dev { applicationId = yourApplicationId + ".dev" + debugsuffix //Reference them again so they get overwritten by the flavor. buildConfigField "String" , "ACCOUNT_TYPE" , "\"${applicationId}.account\"" buildConfigField "String" , "AUTHORITY" , "\"${applicationId}.provider\"" resValue "string" , "account_type" , "${applicationId}.account" resValue "string" , "authority" , "${applicationId}.provider" } } } |
第二部:
2. Refer to them in your Android Manifest
Replace the permissions and provider authorities in yourAndroidManifest.xml with ${applicationId}
:
1 2 3 4 5 6 7 | <permission android:name= "${applicationId}.permission.MAPS_RECEIVE" android:protectionLevel= "signature" /> <uses-permission android:name= "${applicationId}.permission.MAPS_RECEIVE" /> <provider android:name= ".your.provider" android:authorities= "${applicationId}.your.provider" … /> |
第三步:
3. Refactor your Java source files with the build specific strings
Update every occurrence of static strings for authorities and account types in your source files.
1 2 | public static final String AUTHORITY = BuildConfig.AUTHORITY; public static final String AUCCOUNT_TYPE = BuildConfig.ACCOUNT_TYPE; |
第四步:
添加xml文件
4. Refactor your SyncAdapter resources
Use the resValue in the syncadapter.xml in res/xml:
1 2 3 | <sync-adapter android:contentAuthority= "@string/authority" android:accountType= "@string/account_type" … /> |
Another nice way to use this is utilising the the Jenkins build number as a suffix.
Et voilà, you can now build and install different app versions on a single device. Just make sure to do some heavy testing, as some static strings hide themselves and can break something. During research it turned out that using the pre-build variable applicationIdSuffix
does not work properly, as the application ID gets changed after the buildFlavor. Another important thing to mention is that you have to sync the project with gradle files after you changed the Gradle VM options.
From:
https://blog.grandcentrix.net/how-to-install-different-app-variants-on-one-android-device/
【推荐】国内首个AI IDE,深度理解中文开发场景,立即下载体验Trae
【推荐】编程新体验,更懂你的AI,立即体验豆包MarsCode编程助手
【推荐】抖音旗下AI助手豆包,你的智能百科全书,全免费不限次数
【推荐】轻量又高性能的 SSH 工具 IShell:AI 加持,快人一步
· 10年+ .NET Coder 心语,封装的思维:从隐藏、稳定开始理解其本质意义
· .NET Core 中如何实现缓存的预热?
· 从 HTTP 原因短语缺失研究 HTTP/2 和 HTTP/3 的设计差异
· AI与.NET技术实操系列:向量存储与相似性搜索在 .NET 中的实现
· 基于Microsoft.Extensions.AI核心库实现RAG应用
· 10年+ .NET Coder 心语 ── 封装的思维:从隐藏、稳定开始理解其本质意义
· 地球OL攻略 —— 某应届生求职总结
· 提示词工程——AI应用必不可少的技术
· Open-Sora 2.0 重磅开源!
· 字符编码:从基础到乱码解决