Android Question ProGuard

[sadegh nordeh]

Hello.
Please support to include a section for setting up ProGuard in the next update.
It is true that Basic does not support ProGuard, but when the bundle version is sent to Google, unfortunately, a number of classes are lost, but in the studio the same source is written, and it is only determined which classes are not lost, so there will be no problem in the bundle version.
It has been requested several times, but no update has been made for this.

 

[Erel]

t is true that Basic

The programming language name is B4A.

Any error you encounter has nothing to do with ProGuard. Google Play doesn't strip any classes out of your bundle.

 

[sadegh nordeh]

The programming language name is B4A.

Any error you encounter has nothing to do with ProGuard. Google Play doesn't strip any classes out of your bundle.

Why do you keep saying it has nothing to do with ProGuard?
Several times, myself and other colleagues have said hundreds of times that we have an error

Fatal Exception: java.lang.NoClassDefFoundError: Failed resolution of: Landroidx/work/impl/WorkDatabase;
at androidx.work.impl.WorkManagerImpl.<init>(WorkManagerImpl.java:242)
at androidx.work.impl.WorkManagerImpl.<init>(WorkManagerImpl.java:217)
at androidx.work.impl.WorkManagerImpl.initialize(WorkManagerImpl.java:196)
at androidx.work.WorkManager.initialize(WorkManager.java:210)
at com.google.android.gms.ads.internal.util.WorkManagerUtil.zzb(com.google.android.gmslay-services-ads-lite@@23.2.0:1)
at com.google.android.gms.ads.internal.util.WorkManagerUtil.zze(com.google.android.gmslay-services-ads-lite@@23.2.0:2)
at com.google.android.gms.ads.internal.util.zzbs.zzdF(com.google.android.gmslay-services-ads-lite@@23.2.0:9)
at com.google.android.gms.internal.ads.zzbae.onTransact(com.google.android.gmslay-services-ads-base@@23.2.0:3)
at android.os.Binder.transact(Binder.java:1406)
at m.ant.bhcom.google.android.gms.policy_ads_fdr_dynamite@244410211@244410203017.691591528.691591528:8)
at com.google.android.gms.ads.nonagon.offline.buffering.c.acom.google.android.gms.policy_ads_fdr_dynamite@244410211@244410203017.691591528.691591528:82)
at com.google.android.gms.ads.nonagon.offline.buffering.h.bcom.google.android.gms.policy_ads_fdr_dynamite@244410211@244410203017.691591528.691591528:5)
at m.cjm.runcom.google.android.gms.policy_ads_fdr_dynamite@244410211@244410203017.691591528.691591528:30)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
at java.lang.Thread.run(Thread.java:1012)

But you said it will be fixed with the sdk update or with the basic update, so we still have this error

But we got exactly the same app output with Android Studio, sorry for this error
Because in Android Studio you can set which classes should not be deleted
There are a series of files in the Google bundle version that are changing, so Google must be told to keep these


By the way, basic is the same as baisc4Android.(b4a)

 

[Erel]

By the way, basic is the same as baisc4Android.(b4a)

Ok.

Why do you keep saying it has nothing to do with ProGuard?

Because it has nothing to do with ProGuard. ProGuard is not involved in the process.

But you said it will be fixed with the sdk update or with the basic update, so we still have this error

No I didn't. Don't misquote me as you will be banned.

The error with WorkDatabase isn't related to ProGuard. The missing class is supposed to be part of Google Play Services, which is installed on the device.