Skip to content
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

feat: updates session manager sdk and related changes. #96

Open
wants to merge 36 commits into
base: master
Choose a base branch
from

Conversation

grvgoel81
Copy link
Contributor

@grvgoel81 grvgoel81 commented Sep 3, 2024

Motivation and Context

  • Update session-manager-android sdk
  • Update authService version to v9 and walletServices to v3.

Jira Link:
https://toruslabs.atlassian.net/browse/PD-4111

Description

  • Update session-manager-android sdk and related changes wrt API method parameters.
  • Update minSdkVersion to 26 in build.gradle
  • Handling Concurrency and update example.
  • Update authService version to v9 and walletServices to v3.
  • Update request() method to return signResponse.

How has this been tested?

  • Tested all functionalities like login, logout, session management ,walletservices, setupMFA and request() method.

Screenshots (if appropriate):

Screen.Recording.2024-11-05.at.11.12.10.AM.mov

For request method changes:

Screen.Recording.2024-10-23.at.10.00.39.AM.mov

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

  • My code follows the code style of this project. (run lint)
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

Signed-off-by: Gaurav Goel <gaurav@tor.us>
Copy link

@metalurgical metalurgical left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have added some comments.

Signed-off-by: Gaurav Goel <gaurav@tor.us>
metalurgical and others added 6 commits September 3, 2024 08:29
Signed-off-by: Gaurav Goel <gaurav@tor.us>
Signed-off-by: Gaurav Goel <gaurav@tor.us>
Signed-off-by: Gaurav Goel <gaurav@tor.us>
@metalurgical
Copy link

metalurgical commented Sep 3, 2024

@grvgoel81 Looking a lot better, please look at the rest of the todos

Signed-off-by: Gaurav Goel <gaurav@tor.us>
@metalurgical metalurgical dismissed their stale review September 10, 2024 07:26

comments resolved

grvgoel81 and others added 9 commits September 10, 2024 13:37
Signed-off-by: Gaurav Goel <gaurav@tor.us>
Signed-off-by: Gaurav Goel <gaurav@tor.us>
Signed-off-by: Gaurav Goel <gaurav@tor.us>
Signed-off-by: Gaurav Goel <gaurav@tor.us>
Signed-off-by: Gaurav Goel <gaurav@tor.us>
Signed-off-by: Gaurav Goel <gaurav@tor.us>
Signed-off-by: Gaurav Goel <gaurav@tor.us>
Signed-off-by: Gaurav Goel <gaurav@tor.us>
Signed-off-by: Gaurav Goel <gaurav@tor.us>
Signed-off-by: Gaurav Goel <gaurav@tor.us>
Signed-off-by: Gaurav Goel <gaurav@tor.us>
Signed-off-by: Gaurav Goel <gaurav@tor.us>
Gaurav Goel and others added 9 commits October 9, 2024 08:30
# Conflicts:
#	core/src/main/java/com/web3auth/core/Web3Auth.kt
Signed-off-by: Gaurav Goel <gaurav@tor.us>
Signed-off-by: Gaurav Goel <gaurav@tor.us>
Signed-off-by: Gaurav Goel <gaurav@tor.us>
Signed-off-by: Gaurav Goel <gaurav@tor.us>
Signed-off-by: Gaurav Goel <gaurav@tor.us>
Signed-off-by: Gaurav Goel <gaurav@tor.us>
Signed-off-by: Gaurav Goel <gaurav@tor.us>
…c JsonObject

Signed-off-by: Gaurav Goel <gaurav@tor.us>
grvgoel81 and others added 4 commits October 29, 2024 07:26
Signed-off-by: Gaurav Goel <gaurav@tor.us>
Signed-off-by: Gaurav Goel <gaurav@tor.us>
Signed-off-by: Gaurav Goel <gaurav@tor.us>
Signed-off-by: Gaurav Goel <gaurav@tor.us>
} else {
initializeCf.completeExceptionally(error)
}
initializeCf.complete(null)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it fine to call both
initializeCf.completeExceptionally(error)
and
initializeCf.complete(null)
right after each other in case of error?

Copy link
Contributor Author

@grvgoel81 grvgoel81 Nov 7, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But what's the need of it? Since .completeExceptionally completes the future with exception and .complete completes the future with any result. So ideally either of them should be called.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should not make a difference.

According to the docs it is conditional on it not already being completed for both functions:
https://docs.oracle.com/javase/8/docs/api/index.html?java/util/concurrent/CompletableFuture.html

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@grvgoel81 For clarity, it may be better to move line 178 to just after line 174 here.

Signed-off-by: Gaurav Goel <gaurav@tor.us>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants