Android Question B4A 10.9: Design support and Mavens

[Semen Matusovskiy]

Hi, guys --

I wrote an Android app three years ago and time to time make cosmetic changes.
Last time I did about two-three monthes ago . I used B4A 10.5 (because it were troubles in 10.7)

Now I need to change again. Because a time of platform 29 is over, I want to move to platform 30.

But in 10.9 I have two types of troubles.

1) DesignSupport - are any news about updates, because old release crashes an app ?

2) I was not able to update some mavens (because new releases crash an app)

Any ideas ?

 

[Erel]

Which error have you encounter?

 

[Semen Matusovskiy]

There is death message only: xxx keeps stopping App info, Close app. Nothing in logs.

 

[Erel]

Check the unfiltered logs. There must be a stack trace there.

 

[Semen Matusovskiy]

It seems to me this is important. Anyway I attached all

FATAL EXCEPTION: main
Process: com.quick.men, PID: 21369
java.lang.NoSuchMethodError: No direct method <init>(Lcom/google/firebase/FirebaseApp;Lcom/google/firebase/iid/Metadata;Lcom/google/firebase/platforminfo/UserAgentPublisher;Lcom/google/firebase/heartbeatinfo/HeartBeatInfo;Lcom/google/firebase/installations/FirebaseInstallationsApiV in class Lcom/google/firebase/iid/GmsRpc; or its super classes (declaration of 'com.google.firebase.iid.GmsRpc' appears in /data/app/~~NLVT1MRKuAz-OjQzyYkk3A==/com.quick.men-1m62kr5iIE4L2SD4A0z4pA==/base.apk!classes2.dex)
at com.google.firebase.messaging.TopicsSubscriber.createInstance(com.google.firebase:firebase-messaging@@20.3.0:1)
at com.google.firebase.messaging.FirebaseMessaging.<init>(com.google.firebase:firebase-messaging@@20.3.0:12)
at com.google.firebase.messaging.FirebaseMessagingRegistrar.lambda$getComponents$0$FirebaseMessagingRegistrar(com.google.firebase:firebase-messaging@@20.3.0:25)
at com.google.firebase.messaging.FirebaseMessagingRegistrar$$Lambda$0.create(Unknown Source:0)
at com.google.firebase.components.ComponentRuntime.lambda$discoverComponents$0(ComponentRuntime.java:132)
at com.google.firebase.components.ComponentRuntime$$Lambda$1.get(Unknown Source:4)
at com.google.firebase.components.Lazy.get(Lazy.java:53)
at com.google.firebase.components.ComponentRuntime.doInitializeEagerComponents(ComponentRuntime.java:291)
at com.google.firebase.components.ComponentRuntime.initializeEagerComponents(ComponentRuntime.java:281)
at com.google.firebase.FirebaseApp.initializeAllApis(FirebaseApp.java:584)
at com.google.firebase.FirebaseApp.initializeApp(FirebaseApp.java:303)
at com.google.firebase.FirebaseApp.initializeApp(FirebaseApp.java:267)
at com.google.firebase.FirebaseApp.initializeApp(FirebaseApp.java:252)
at com.google.firebase.provider.FirebaseInitProvider.onCreate(FirebaseInitProvider.java:51)
at android.content.ContentProvider.attachInfo(ContentProvider.java:2388)
at android.content.ContentProvider.attachInfo(ContentProvider.java:2358)
at com.google.firebase.provider.FirebaseInitProvider.attachInfo(FirebaseInitProvider.java:45)
at android.app.ActivityThread.installProvider(ActivityThread.java:7239)
at android.app.ActivityThread.installContentProviders(ActivityThread.java:6780)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6697)
at android.app.ActivityThread.access$1300(ActivityThread.java:237)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1913)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:223)
at android.app.ActivityThread.main(ActivityThread.java:7656)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
at com.android.internal.os.Zyg

 

[Erel]

It is not related to the old and unmaintained design support libraries.

It looks like you are using an old SDK. Download a new one, exactly as explained here: https://www.b4x.com/b4a.html

 

[Semen Matusovskiy]

I tried to follow your advice and completely reinstall B4A_SDK (recommended Mavens + which a program asked).
At first, barrierMargins in com.google. android.material. Ok, doubt that a program uses a time picker, so I removed a line.

Compiling

Uncaught translation error: com.android.dx.cf.code.SimException: invalid opcode ba (invokedynamic requires --min-sdk-version >= 26)
Uncaught translation error: com.android.dx.cf.code.SimException: invalid opcode ba (invokedynamic requires --min-sdk-version >= 26)
Uncaught translation error: com.android.dx.cf.code.SimException: invalid opcode ba (invokedynamic requires --min-sdk-version >= 26)
Uncaught translation error: com.android.dx.cf.code.SimException: invalid opcode ba (invokedynamic requires --min-sdk-version >= 26)
Uncaught translation error: com.android.dx.cf.code.SimException: invalid opcode ba (invokedynamic requires --min-sdk-version >= 26)
Uncaught translation error: com.android.dx.cf.code.SimException: invalid opcode ba (invokedynamic requires --min-sdk-version >= 26)
Uncaught translation error: com.android.dx.cf.code.SimException: invalid opcode ba (invokedynamic requires --min-sdk-version >= 26)
Uncaught translation error: com.android.dx.cf.code.SimException: invalid opcode ba (invokedynamic requires --min-sdk-version >= 26)
Uncaught translation error: com.android.dx.cf.code.SimException: invalid opcode ba (invokedynamic requires --min-sdk-version >= 26)
UNEXPECTED TOP-LEVEL EXCEPTION:
java.lang.RuntimeException: Translation has been interrupted
    at com.android.dx.command.dexer.Main.processAllFiles(Main.java:692)
    at com.android.dx.command.dexer.Main.runMultiDex(Main.java:366)
    at com.android.dx.command.dexer.Main.runDx(Main.java:291)
    at com.android.dx.command.dexer.Main.main(Main.java:249)
    at com.android.dx.command.Main.main(Main.java:94)
Caused by: java.lang.InterruptedException: Too many errors
    at com.android.dx.command.dexer.Main.processAllFiles(Main.java:684)
    ... 4 more

What is it ? A joke of Platform 30 (I changed in manifest and android.jar path to platform 30).

 

[agraham]

Perhaps this?
desugar - fix the "invokedynamic requires" error | B4X Programming Forum

 

[Semen Matusovskiy]

It seems to me that Agraham is right. A problem is in new mavens, which use 'bad' features.

 

[Erel]

I tried to follow your advice and completely reinstall B4A_SDK (recommended Mavens + which a program asked).
At first, barrierMargins in com.google. android.material. Ok, doubt that a program uses a time picker, so I removed a line.

This is not my advice.

My advice: delete your current SDK and download a new one: https://www.b4x.com/b4a.html
No need to run anything else.

 

[Semen Matusovskiy]

I did not notice ready sdk folder, because always created it by myself. Unlike it was necessary to add or update some mavens, a process was enough fast. And what is more important, l was able to compile and run. Thanx