-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Android 12 non-SDK restrictions reflection is unsupported #233
Comments
Hi @rid-hrant, Thanks for reaching out about this. I'll take a closer look at this with my engineering team. This is the first report we've heard with this issue, though many of our customers are using our latest Android SDK (5.7.1) and have customers on Android 12. Is this causing any issues for your app in production, development, or both? Any other details you could give would be helpful. Thanks again! |
Hi @CaseyApptentive, I am currently working on researching Android 12 changes to target our application. I'm not using |
Thanks for the follow up, @rid-hrant. Let me discuss this with my team and get back to you. Stay tuned! |
Hi @rid-hrant ! I have spoken with our engineering team and we have assessed the issue that you brought up. The Our engineer tested the function on Andoroid 12 to check if it would cause an issue, and found that it fails silently before hitting Thank you so much for bringing this to our attention! |
Hey, @HarryAWoodworth thx for your response, and thx for testing it on android 12. I suppose in your message you mean |
@rid-hrant Yes, my apologies, I did mean |
After analyzing my app with the veridex tool, I found that there are two use cases for the reflection API in the Apptentive Android SDK.
The reason for this log is reflection field API usage getDeclaredField and it could break the app on Android 12. Here you can see the code snippet from Apptentive Android SDK.
com.apptentive.android.sdk.util.Util#replaceDefaultFont
The functionality of the replaceDefaultFont method, which currently relies on reflection, needs to be replaced with some supported API.
The text was updated successfully, but these errors were encountered: