Migrate Lifecycle Common/Runtime to multiplatform [317249252]

Fixed

Feature Request

Status Update

No update yet.

Description

il...@google.com

created issue #1

Dec 20, 2023 07:32PM

It would be nice if the core concepts of Lifecycle would be available for use in Kotlin Multiplatform projects.

Libraries like the Navigation Component, Fragments, etc. have all settled on the same definitions of Lifecycle States, which seem to apply to any UI:

CREATED - created, but not yet visible
STARTED - visible, but not yet settled (e.g., entering or exiting transitions may still be running)
RESUMED - visible and settled

This would include:

And ideally everything in the lifecycle-common and lifecycle-runtime artifacts.

Comments

il...@google.com <il...@google.com> Jan 23, 2024 09:23PM

Assigned to mg...@google.com.

il...@google.com <il...@google.com> #2Jan 30, 2024 11:09PM

fix:

https://github.com/androidx/androidx/pull/147

ap...@google.com <ap...@google.com> #3Feb 2, 2024 12:20AM

Project: platform/frameworks/support
Branch: androidx-main

commit 428f0ec685ff80035c0511c0cdb12b9770b6159c
Author: Maxim Savoskin <maximsavoskin@gmail.com>
Date: Mon Mar 29 13:20:52 2021

[GH] [Lifecycle] [Lint] fixes

b/183696616

: KtCallExpression is not always the first in the list

## Proposed Changes
KtCallExpression is not always the first in the list. In this case, it is KtModifierList.

## Testing

Test: ./gradlew test lint buildOnServer

## Issues Fixed

Fixes:

https://issuetracker.google.com/issues/183696616

This is an imported pull request from

https://github.com/androidx/androidx/pull/147.

Resolves #147
Github-Pr-Head-Sha: 3c2693e2f4cceb367c9c169749d1391a9da2740f
GitOrigin-RevId: a6440720029b1c0c702207f1393d3b01180691b8
Change-Id: I9b4383329b9ece85e3bffa4a9bf8e8a3f0c3d84a

M lifecycle/lifecycle-livedata-core-ktx-lint/src/main/java/androidx/lifecycle/lint/NonNullableMutableLiveDataDetector.kt
M lifecycle/lifecycle-livedata-core-ktx-lint/src/test/java/androidx/lifecycle/lint/NonNullableMutableLiveDataDetectorTest.kt

https://android-review.googlesource.com/1656820

mg...@google.com <mg...@google.com> #4Feb 2, 2024 04:31PM

Will you guys be releasing a hot fix 2.3.2 for this?

ap...@google.com <ap...@google.com> #5Feb 6, 2024 09:06PM

Any updates about when this is going live?

mg...@google.com <mg...@google.com> Feb 14, 2024 03:27PM

Marked as fixed.

ap...@google.com <ap...@google.com> #6Mar 8, 2024 11:29AM

Hi, I hate to keep posting same comments, but are there any plans to release this fix? It's blocking us from updating to fragment 1.3.2+.

ap...@google.com <ap...@google.com> #7Mar 8, 2024 11:38AM

pr...@google.com <pr...@google.com> #8Mar 20, 2024 08:26PM

How do you update components that are viewed through the chrome.url page of they all indicate that they are not up to date