FragmentActivity lifecycle methods Javadocs hide the Activity lifecycle javadocs [139548782]

Assigned

Process

Status Update

No update yet.

Description

da...@gmail.com

created issue #1

Aug 18, 2019 03:04AM

The FragmentActivity javadocs for methods like onCreate(), onDestroy(), etc. have unhelpful and misleading messages that mention what they're doing to the fragments, and not what the subclass should do with it. To a total beginner, it would look like you are supposed to call these methods to do things to your fragments. These docs should @inheritDoc the Activity javadocs before explaining what they are doing to the fragments. This javadocs issue is also passed down to AppCompatActivity.

Comments

vi...@google.com <vi...@google.com> #2Sep 29, 2019 07:56AM

Assigned to vi...@google.com.

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.

vi...@google.com <vi...@google.com> #3Oct 24, 2019 11:46AM

@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
?

da...@gmail.com <da...@gmail.com> #4Oct 27, 2019 02:25PM

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.

vi...@google.com <vi...@google.com> #5Oct 31, 2019 03:01PM

@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

bn...@google.com <bn...@google.com> Dec 24, 2020 05:26AM

Reassigned to an...@google.com.

il...@google.com <il...@google.com> Jan 20, 2021 12:52AM

Reassigned to jb...@google.com.

ap...@google.com <ap...@google.com> #6Feb 26, 2021 02:23AM

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