Skip to content
This repository has been archived by the owner on Feb 6, 2024. It is now read-only.

Fix linting warnings and errors on SDK version 31 #209

Closed
ktohalloran opened this issue Mar 24, 2023 · 0 comments · Fixed by #216
Closed

Fix linting warnings and errors on SDK version 31 #209

ktohalloran opened this issue Mar 24, 2023 · 0 comments · Fixed by #216
Assignees

Comments

@ktohalloran
Copy link
Contributor

ktohalloran commented Mar 24, 2023

While issue #201 bumped up the target and compile SDK version to 31, we should actually update this more fully, including addressing the many linting warnings and handful of warnings, and updating dependencies as needed. This should help us in the upgrade to 33 in issue #208.

Additional context:

  • Some of the linting issues point to the deprecation of AsyncTask. Some quick Googling suggests there is no 1-to-1 replacement for this, so we should learn a bit more about fixing these would entail and if it's worth the effort to address this right now.
  • We use features that are deprecated in Gradle v8, so we should decide whether those features are worth updating to upgrade our version of Gradle.
  • We have been seeing E/RecyclerView: No adapter attached; skipping layout and E/PlacesList: image view not found; not setting up scroll listener errors for the last couple of versions. Is there an easy fix for this or can it be fixed by a dependency upgrade?
  • E/libprocessgroup: set_timerslack_ns write failed: Operation not permitted errors appear on API level 28+ following issue Upgrade to Android SDK version 31 by August 31, 2023 #201. To replicate, go to the "places" map view, select an event from the map, or select filter on the map view. These errors appear to be related to the dialogue boxes and map.
  • Google's pre-launch report from releasing the app to testing resulted in the following error java.lang.IllegalStateException: android.os.ServiceManager$ServiceNotFoundException: No service published for: search. We should figure out how to replicate and address this issue.
  • API level 31 added the ability to share approximate location instead of precise location. The app works if you only share approximate location, but you'll continue to see permissions pop ups and toast messages. We should try to find and fix whatever is checking again and again for precise location and update it to accept approximate location.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants