Describe the solution you'd like
After migrating our app from DX/Proguard to D8/R8, the app had several problems. Contacting AppCenter chat, I was informed that it isn't supported and to open a new feature request.
R8 became the default code shrinker for Android and should be supported.
Describe alternatives you've considered
Building the apk on our Visual Studio, results in a working app. But breaks our CI/CD.
NunoBem
All 11 comments
Hi @NunoBem - thanks for the feature request. App Center diagnostics only supports deobfuscation with the ProGuard at the moment. We don't have immediate plans to support D8/R8 but I will monitor this request for interest.
(Note: similar request #458)
winnie
on 17 Jul 2019
D8/R8 is becoming standard in Android world. @winnieli1208 please consider supporting it soon
filipkowicz
on 25 Jul 2019
Since R8 is becoming de-facto standard from Android side, and is supposed to replace proguard. In recent versions of Android Studio and gradle it is enabled by default. I suppose that tells you that there will be interest for this.
Why the need to explicitly show the interest with comments and up-votes?
brcinho
on 25 Jul 2019
Contacting AppCenter chat, I was informed that it isn't supported and to open a new feature request.
@brcinho I suppose microsoft is driven by community feedback too and defines it's priorities.
NunoBem
on 25 Jul 2019
@NunoBem I completely agree with you. The problem occurs when someone is shutting down the service to push their own service but they didn't match the quality, pro-activeness and feature set of the previous service. Then they can not rely that product roadmap depends on the community feedback solely, they need to show some initiative and pro-activeness on their own.
brcinho
on 26 Jul 2019
@NunoBem Were your problems with R8/D8 related to only building your app on App Center or also diagnosing crash reports? I'll look into the conversations on why it might have failed for you, but feel free to share more details here or with me personally (email is in bio) if needs be - at least in general it should work for App Center Build.
matthiaswenz
on 26 Jul 2019
@ranterle Related to inability for app center to de-obfuscate the stack trace based on the mapping.txt uploaded.
brcinho
on 14 Aug 2019
458
brcinho
on 14 Aug 2019
What's the feedback about this? @winnieli1
NunoBem
on 2 Oct 2019
Hi all! Our team is starting this very soon. No exact ETA yet but we expect to have this done in a few
weeks. Thanks for the patience! We'll post here with updates.
winnie
on 7 Nov 2019
We added support for this last week (see #458). Thanks!
winnie
on 20 Nov 2019
Related issues
busterlaursen
路
4Comments
mason-hz
路
3Comments
egorikftp
路
3Comments
kuyazee
路
3Comments
KSemenenko
路
3Comments
Most helpful comment
@NunoBem I completely agree with you. The problem occurs when someone is shutting down the service to push their own service but they didn't match the quality, pro-activeness and feature set of the previous service. Then they can not rely that product roadmap depends on the community feedback solely, they need to show some initiative and pro-activeness on their own.