[Feature Request] Add Kotlin 2.0+ support for Store v4

Open
#705 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
kotlin
Domain
build-system

Research direction

No files or tests are named. Start by locating Store v4 usages of Duration.hours(...) and similar kotlin.time APIs, then identify the existing Kotlin compatibility checks; done means Store v4 builds and its relevant tests pass with Kotlin 2.0+ without requiring a Store v5 migration.

Written by the indexing model from the issue text.

Description

enhancement

Is your feature request related to a problem? Please describe.
Many projects (like ours) are still using Store v4 due to stability and API familiarity. However, Store v4 breaks with Kotlin 2.0+ due to usage of older kotlin.time APIs like Duration.hours(...), which are now removed in Kotlin 2.x.

Describe the solution you'd like
Backport Kotlin 2.0+ compatibility changes into Store v4 — specifically, replace usages of Duration.hours(...) and similar deprecated APIs to ensure compatibility with Kotlin 2.x, without requiring a full upgrade to Store v5.

Describe alternatives you've considered

  • Migrating to Store v5, but it contains significant API changes and would require a lot of code rewrite in large codebases.
  • Forking Store v4 and maintaining it internally, which works but is not ideal for long-term maintainability.

Additional context
Store v4 is still widely used in many production apps. Providing Kotlin 2.x support will help teams adopt latest Kotlin versions without breaking existing architecture. We'd really appreciate official support to avoid maintaining internal forks.

Dominant language
Kotlin
Stars
3.4k
Forks
217
Avg merge
18m
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MobileNativeFoundation/Store

All issues in MobileNativeFoundation/Store

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.