-
Notifications
You must be signed in to change notification settings - Fork 82
Update readme #617
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update readme #617
Conversation
super.onDestroy(); | ||
// Your own Activity code | ||
lock.onDestroy(this); | ||
lock = null; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is there no need to set the reference to null in the Kotlin version?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is not because of kotlin. When an android activity gets its onDestroy method called is because is going away for good. There's no need to set to null the references. The garbage collector will recycle the whole activity instance.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are a couple of typos and questions. Other than that, it looks good.
Co-authored-by: Rita Zerrizuela <[email protected]>
60a8230
to
78c85ab
Compare
Co-authored-by: Steve Hobbs <[email protected]>
Comments addressed! |
Changes
This PR updates the readme using kotlin snippets and removing instructions that no longer apply (e.g. OIDC mode).
The content is not final and might be updated in the following PRs.
References
See
SDK-2431