Skip to content

Target API level 29 #39

@emredirican

Description

@emredirican

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions