Skip to content
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

Question: Do we still need deleteTCStringIfOutdated? #8

Open
AndroidDeveloperLB opened this issue Dec 18, 2023 · 2 comments
Open

Question: Do we still need deleteTCStringIfOutdated? #8

AndroidDeveloperLB opened this issue Dec 18, 2023 · 2 comments
Labels
documentation Improvements or additions to documentation

Comments

@AndroidDeveloperLB
Copy link

Do we still need deleteTCStringIfOutdated? Or was it fixed already?
I'm talking about this:
https://github.com/bocops/UMP-workarounds/blob/main/detect_outdated_consent/android/kotlin/detect_outdated_consent.kt

@bocops
Copy link
Owner

bocops commented Dec 18, 2023

I haven't followed all conversations about this in detail, but this is something that might have been solved in the meantime. I will check if I can find a reliable source for this, and would update README.md if that is the case, but probably still keep the code around for the time being.

@bocops bocops added the documentation Improvements or additions to documentation label Dec 18, 2023
@AndroidDeveloperLB
Copy link
Author

How do you check it out? You do reverse-engineering?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants