You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a reason for not targeting the API level 29?
We've experienced a problem with Samsung devices where the clock was behaving strangely (Felt like displaying random times). I tried to make detailed logging by forking the library and adding the modules to our project. Then we realized that we couldn't get the logs from Samsung device with API level 29. I only managed the logs working by targeting API level 29. We are still not sure if the original problem is solved of course.
There I was wondering why the library is targeting API level 27 and whether we can do anything about it or not.
The text was updated successfully, but these errors were encountered:
Hi,
Is there a reason for not targeting the API level 29?
We've experienced a problem with Samsung devices where the clock was behaving strangely (Felt like displaying random times). I tried to make detailed logging by forking the library and adding the modules to our project. Then we realized that we couldn't get the logs from Samsung device with API level 29. I only managed the logs working by targeting API level 29. We are still not sure if the original problem is solved of course.
There I was wondering why the library is targeting API level 27 and whether we can do anything about it or not.
The text was updated successfully, but these errors were encountered: