Tasker breaks gson in android making apps to crash

[sn4k3]

I took days and wipes between debugs to find the cause.
In end I settle in tasker being the cause for it.

The problem is after "unknown" setting the gson start to stack overflow in AndroidRuntime.
I asked for help: google/gson#2870

07-04 01:41:58.517 15200 16275 E AndroidRuntime: java.lang.StackOverflowError: stack size 1037KB
07-04 01:41:58.517 15200 16275 E AndroidRuntime: 	at java.lang.reflect.Field.get(Native Method)
07-04 01:41:58.517 15200 16275 E AndroidRuntime: 	at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$1.writeField(ReflectiveTypeAdapterFactory.java:2)
07-04 01:41:58.517 15200 16275 E AndroidRuntime: 	at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.write(ReflectiveTypeAdapterFactory.java:8)
07-04 01:41:58.517 15200 16275 E AndroidRuntime: 	at com.google.gson.Gson$FutureTypeAdapter.write(Gson.java:4)
07-04 01:41:58.517 15200 16275 E AndroidRuntime: 	at com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.write(TypeAdapterRuntimeTypeWrapper.java:17)
07-04 01:41:58.517 15200 16275 E AndroidRuntime: 	at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$1.write(ReflectiveTypeAdapterFactory.java:4)
...
07-04 01:37:45.049  9361 10653 E AndroidRuntime:        at com.google.gson.Gson.toJson(Gson.java:22)
07-04 01:37:45.049  9361 10653 E AndroidRuntime:        at com.google.gson.Gson.toJson(Gson.java:11)
07-04 01:37:45.049  9361 10653 E AndroidRuntime:        at com.google.gson.Gson.toJson(Gson.java:5)
07-04 01:37:45.049  9361 10653 E AndroidRuntime:        at com.google.gson.Gson.toJson(Gson.java:3)
07-04 01:37:45.049  9361 10653 E AndroidRuntime:        at sibs.connector.helpers.JsonParser.toJson(JsonParser.java:6)
07-04 01:37:45.049  9361 10653 E AndroidRuntime:        at sibs.connector.core.ConnectorHandler._callback(ConnectorHandler.java:39)
07-04 01:37:45.049  9361 10653 E AndroidRuntime:        at sibs.connector.core.ConnectorHandler.callback(ConnectorHandler.java:1)
07-04 01:37:45.049  9361 10653 E AndroidRuntime:        at sibs.connector.core.ConnectorHandler.nativeProcessService(Native Method)
07-04 01:37:45.049  9361 10653 E AndroidRuntime:        at sibs.connector.core.ConnectorHandler.processService(ConnectorHandler.java:1)
07-04 01:37:45.049  9361 10653 E AndroidRuntime:        at sibs.intra.sw.mbwaysdk.implementation.ConnectorHandlerMBWay.processService(ConnectorHandlerMBWay.java:1)
07-04 01:37:45.049  9361 10653 E AndroidRuntime:        at o.d.a(MBWayPrivateServiceImpl.java:24)
07-04 01:37:45.049  9361 10653 E AndroidRuntime:        at l.u1.run(MBWayRegisterServiceImpl.java:22)
07-04 01:37:45.049  9361 10653 E AndroidRuntime:        at java.lang.Thread.run(Thread.java:1042)

The affected apps in my case were MBWay and CGD (Banking apps)

• MBWay will infinitely loop
• CGD will crash once click MBWay

After many wipes and step by step I was able to reproduce the problem and associate with tasker.

Grating "Access to Hidden APIs" trigger the problem.
I found latter that if I revoke that the problem is solved, grant again and problem is back.

Tried to uninstall tasker with that granted and problem remains.
Strangely granting that access breaks something in android and causes the overflow.
Before I know "ungrant is the way to fix" I had to format android and retry every app.
I left shizuku uninstalled as I also suspect from it, but in the end was all the tasker.

Now I have everything working, including shizuku and problematic apps works. (As long tasker don't touch hidden apis)

My few tasks are simple, just a sleep task, auto power save mode, auto toggle mobile network, airplane, check and send sms.

Example of problem (Infinite loop where stackoverflow happens):
https://github.com/user-attachments/assets/819e38ab-9608-48a4-b9e5-343fe828ea24

My phone:

[joaomgcd]

Hi. Thanks very much for getting to the bottom of it and the very accurate analysis.

Did you have any suggestions on how to handle this? Or are you suggesting that I should add a warning to that permission button saying that it could break apps in unexpected ways?

Thanks again!

[sn4k3]

Hard to tell, as I have no clue if this is frequent, for instance:

• Does it happen in other(s) Android 15?
• Does it happen in different Android versions?
• Or does it only happen in some OSes like OriginOS?

Do you have any clue why that API is causing such trouble?
Can you test under your device and replicate this?

If able to confirm a popup can inform user prompt about the possible unexpected problem before activate this API.

[sn4k3]

Today I got a notification from tasker saying something like ADB wifi required to perform a action.
I didn't set anything, the MBWay start to show the problem, I connect the phone to PC to check permissions and the Hidden API was been auto granted:

Does or can tasker auto grant this itself? I have adb wifi on and shuziku (However shuziku service was stopped at the moment).
Is there a way to prevent this auto grant?

PS: I need to revoke again to put MBWay working again, but is bad situation if this happen and I'm not near my PC.

EDIT: I disabled the task that auto enables the Hidden API (Mobile Data Off).
But also prepared adb shell settings delete global hidden_api_policy to run with ashell just in case...

[joaomgcd]

That's automatically granted whenever an ADB Wifi action is ran, Airplane mode is attempted to be toggled and Network mode is attempted to be changed.

It's also granted when you use the helper to select an ADB Wifi action.

Glad you figured it out though!