Deprecate `launchWhenX` APIs [248302832]

Fixed

Feature Request

Status Update

No update yet.

Description

mv...@google.com

created issue #1

Sep 22, 2022 06:18PM

The launchWhenX extension functions on LifecycleCoroutineScope are documented with a caution blurb to prevent its usage in favor of the repeatOnLifecycle API.

The launchWhenX APIs should be properly deprecated—suggesting a replace with option if possible—and favor the repeatOnLifecycle API instead.

Comments

il...@google.com <il...@google.com> Nov 1, 2022 04:27PM

Assigned to cl...@google.com.

cl...@google.com <cl...@google.com> Nov 8, 2022 01:26AM

Accepted by cl...@google.com.

[Deleted User] <[Deleted User]> #2Nov 13, 2022 07:52PM

Since this is happening in Tink, rather than in the AndroidX library, it would be best to open an issue with that project, as there isn't an easy way for us to fix this.

[Deleted User] <[Deleted User]> #3Nov 13, 2022 07:54PM

@2 I don't know what "Tink" is, but here, created:

https://github.com/google/tink/issues/534

Would this mean that this bug report should be written there as well:

https://issuetracker.google.com/issues/176215143
?

ap...@google.com <ap...@google.com> #4Nov 30, 2022 01:53AM

Tink is the library that does the heavy lifting in Jetpack Security.

And yes, potentially raising that issue with the Tink team directly could help.

ap...@google.com <ap...@google.com> #5Nov 30, 2022 01:53AM

@4 Well why didn't Google offer it there? Crashes are far more important than warning logs...
Here, created it there too:

https://github.com/google/tink/issues/535

cl...@google.com <cl...@google.com> #6Dec 12, 2022 06:38PM

Marked as fixed.

Anyone here solved the issue? I have implemented the jetpack security and got the same crashes.

na...@google.com <na...@google.com> #7Jan 11, 2023 08:12PM

same warning

my...@gmail.com <my...@gmail.com> #8Feb 17, 2023 05:48PM

same logs for me