Sam Lu

I got the same error today: Caused by: java.lang.NoSuchMethodError: No direct method (Lcom/google/gson/Gson;)V in class Lcom/google/gson/Gson$1; or its super classes (declaration of 'com.google.gson.Gson$1' appears in /data/app/com.google.android.apps.mtaas.crawler-1/base.apk) at com.google.gson.Gson.doubleAdapter(Gson.java:312) at com.google.gson.Gson.(Gson.java:241)...

No. only Java 7 is used. The same build script, linked libraries, and environment for my app. No such issue for the new build apk that I uploaded to Play...

Glad to know that the problem is not related to our code. I also changed the source code of ConsentInformation.java #248 from `} catch (Exception e) {` to `} catch...

Here is my solution. Search "ysl" to see the changes. I have tested it on several Android 12 devices without any issues. ``` /* * Copyright (C) 2014 Jake Wharton...

I don't see any issues with the app that targets the sdk 33. Did you apply my patch code (https://github.com/JakeWharton/ProcessPhoenix/issues/47#issuecomment-1128377615)?

Looking forward to seeing the new solution. Yes, I am building the FAN adapter myself.

Declaring nested hierarchies within the same XML resource using a nested PreferenceScreen is no longer supported. Use nested Fragment objects instead. https://developer.android.com/develop/ui/views/components/settings/organize-your-settings#preferencescreens

`m3expressive_alert_dialog_title.xml` has the same issue. lib/java/com/google/android/material/dialog/res/layout/m3expressive_alert_dialog_title.xml ```

The main reason for my suggestion is to maintain consistent behavior with the standard system and AppCompat AlertDialog, neither of which enables this by default. If this feature is important...