取得相同的Google Billing SKU,以替代应用程式套件名称 [英] Get same Google Billing SKU's for alterantive app package names
问题描述
在我们的应用程序中,我们有2个应用程序命名架构:com.my.app
用于发布版本,com.my.app.debug
用于调试.
以此方式进行设置,因此我们可以在Firebase上分离分析-这样,调试崩溃不会污染我们的生产洞察力.
In our app we have 2 app naming schemas: com.my.app
for release builds, and com.my.app.debug
, for, well, debugging.
This is setup this way, so we can separate analytics on Firebase - so debug crashes don't pollute our productions insights.
其中包含 Android结算.在我们的Play商店帐户中,我们上传了制作作品.aab
(com.my.app
),并设置了一些应用内订阅.我还要补充一点,我们仍处于预生产阶段.
In comes Android Billing. In our Play store account, we have uploaded our productions build .aab
(com.my.app
), and set-up some in-app subscriptions. I'll add that we are still in the pre-prod stage.
问题是-我们在 debug 版本中没有得到任何SKU
,因为包签名与配置中的包签名不同,并已上传到Play商店控制台.
Problem is- we don't get any SKU
s in debug build, since the package signature is different than the one configured in, and up-loaded to Play Store console.
问题是-除了使用debug
包裹名称?
The questions is- Is there a way to integrate/test our production Android Billing products against our debug build, other than creating a new app
with the debug
package name?
推荐答案
否,不同的程序包意味着不同的应用程序,因此意味着无法与其他应用程序共享的不同应用程序内产品.
No, different package means different app and therefore different in-app products that cannot be shared with another app.
奇怪的是,当android studio和其他IDE可以在调试模式或发布模式下工作而无需更改项目时,您已经制作了一个用于调试的应用程序.
The strange thing is that you have made a different app for debugging when android studio and other IDEs can work in debug mode or release mode without changing project.
这篇关于取得相同的Google Billing SKU,以替代应用程式套件名称的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!