Revert to minSdk 23 - #158
Conversation
|
Thanks for the PR. I checked it out and ran the build. The direction is right and most of the revert is faithful to the pre-4b77900 code: Blocker — CI fails. That comes from the The fix, which is better anyway. The annotation on So: move Docs still say 26. Nits.
One caveat on my side: none of this is exercised on a real API 23 device, so the restored pre-26 behaviour is verified by code review and lint only. |
|
Can you fix the compile error so we can merge? |
A yes, I assumed the first comment was ai generated with no actual human looking at the pr. |
|
This should fix the ktfmt and minsdk issues at least. I can also say that the lib works fine on minsdk23 at least when tested on my app with several <26 sdk users (apart from the standard issues with android storage that are impossible to fix). |
…t behind The 26 guard on EXTRA_INITIAL_URI is back, so the "only takes effect on API 26+" notes 4b77900 deleted are true again. README, CONTRIBUTING and MIGRATION still advertised minSdk 26. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01D8wJZXku2iXgHRETtRmvHw
|
Merged and out as 3.1.0 — I pushed one commit on top of yours: the docs still said minSdk 26 (README, CONTRIBUTING, MIGRATION), and the Thanks for the fix — and for the sub-26 field report, which is the only real-device evidence here; on my side this was verified by build, lint and unit tests only. |
Fixes #157 by reverting parts of 4b77900