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

Hotfix/1.11.6 #1338

Merged
merged 13 commits into from
Feb 26, 2025
Merged

Hotfix/1.11.6 #1338

merged 13 commits into from
Feb 26, 2025

Conversation

micbakos-rdx
Copy link
Contributor

Description

Addresses three fixes:

  1. Adds Estimated label on NFTs that are classified as predicted in tx analysis, in both non fungible collections and in stake claims
  2. Stake claim NFTs that have no claim value are labeled as Amount of deposit is unknown
  3. There was a bug when resolving the Using DApps section. Specifically when there are multiple component addresses that point to the same dApp, the app was displaying the same dApp for each component. Now dApps are distinct. In this scenario, also there was a change to resolve all components with the same request instead of chaining parallel different requests.

Copy link
Contributor

@giannis-rdx giannis-rdx left a comment

Choose a reason for hiding this comment

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

LGTM

…definition address points to another.

This stems from an old bug on VerifyDAppsUseCase were a dApp was always verified when dev mode was enabled. It was later fixed to always verify the network id of that dApp is the same with the current network id.
Comment on lines +171 to +177
/**
* Simple extension on `ProfileNetwork` that filters out dApps with dAppDefinitionAddress
* on another network. All AuthorizedDApps are supposed to be under the same `ProfileNetwork::networkId`
* but due to an old bug that was later fixed on `VerifyDAppUseCase`, there seems to be some profiles that
* have authorized dApps with dApp definition address pointing to another network. A user with
* **Developer Mode ON** could "verify" any dApp and store it in profile.
*/
Copy link
Contributor

Choose a reason for hiding this comment

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

good that you added an explanation there, thanks!

@micbakos-rdx micbakos-rdx changed the base branch from hotfix/1.11.5 to main February 26, 2025 12:50
# Conflicts:
#	app/src/main/java/com/babylon/wallet/android/presentation/ui/composables/assets/StakingTab.kt
#	core/src/main/java/rdx/works/core/sargon/ProfileExtensions.kt
Copy link

Quality Gate Failed Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 40%)
10.8% Duplication on New Code (required ≤ 3%)

See analysis details on SonarQube Cloud

@micbakos-rdx micbakos-rdx merged commit d2d2f27 into main Feb 26, 2025
10 of 11 checks passed
@micbakos-rdx micbakos-rdx deleted the hotfix/1.11.6 branch February 26, 2025 14:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants