Description

• Unable to send token other than MXC with MNS name in AXS wallet

Steps to reproduce

1. Open your own wallet
2. Click on “Send and Recieve”
3. Select token as “RIDE” or any other
4. Click “Send”
5. Select the “RIDE” token
6. Enter amount
7. Enter recipient as MNS name (e.g. hairy.mxc) instead of address

Expected:

Should be able to send token

Actual:

Next button is non functional at this point

https://www.notion.so/wannsee-roadmap/DApps-image-caching-e3da5e6d125e47d8a1bf6fdb1e68cf1e

https://www.figma.com/file/s1EaHblSIZm29z59KQcM5g/AXS-App-Homescreen-Upgrade?type=design&node-id=0-1&mode=design&t=MVy9YROXyHztHg9J-0

I will need to update the following for upcoming releases,

1. My dev environment
2. Project target IOS SDK
3. Flutter version might be required to be updated
4. Packages also might be required to be updated
5. App center build props

I will redesingn the home screen, To match new home screen design.
https://www.figma.com/design/nMVjWYqYkll9ZktOi8lE4c/Moonchain-App-Icons---Main?node-id=228-1293&t=eRN1oC4Yp0BEiUvs-4

Issue 1: Blank Space Appears When Bookmarks Are Already Added

Observed Behavior: There is a significant blank space in the bookmarks section.

Issue 2: Dapp Icons Are Too Large

Steps to Reproduce:
Open the dapps screen in the application.
Observed Behavior: The icons of the dapps appear to be quite large.
Expected Behavior: The dapp icons should be reduced by approximately 50% in size, as per Sheen's suggestion.

cc: @sheenhx

UPDATE:

ISSUE 1:

I'm unable to replicate it. I have attached screenshots from both the old version of the app and the new one. @reasje @sheenhx could help provide better insights on the same!

ISSUE 2:
Confirmed Style for dapps on Android || IOS (Shared and Confirmed by @sheenhx )

7 * 5

3 * 6

Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage
5.1.1(ii) Permission Apps that collect user or usage data must secure user consent for the collection, even if such data is considered to be anonymous at the time of or immediately following collection. Paid functionality must not be dependent on or require a user to grant access to this data. Apps must also provide the customer with an easily accessible and understandable way to withdraw consent. Ensure your purpose strings clearly and completely describe your use of the data. Apps that collect data for a legitimate interest without consent by relying on the terms of the European Union’s GeneralData Protection Regulation ("GDPR") or similar statute must comply with all terms of that law.

Issue Description

One or more purpose strings in the app do not sufficiently explain the use of protected resources. Purpose strings must clearly and completely describe the app's use of data and, in most cases, provide an example of how the data will be used.

Examples of unclear purpose strings:

• "App would like to access your Contacts"
• "App needs microphone access"

Next Steps

Update the location purpose string to explain how the app will use the requested information and provide an example of how the data will be used. See the attached screenshot.

Resources

• See examples of helpful, informative purpose strings.
• Review a list of relevant property list keys.

Support

For Create Wallet we already have three options
Email, Wechat and Telegram

In case all these three options are disabled - means users dosent have these in their devices

Then we should enable another option to save file locally in theor device and enable user to create wallet

Note: save file locally will only be enabled when other three options are disabled.

When attempting to save the seed phrase locally in a file on Android, the feature works correctly when using the 'My Files' directory but encounters a problem when using the 'Files' directory.

The XSD value is incorrectly shown as 0.0 XSD in the AXS wallet

I am verry sorry I write irrelevent contents, but I really don't know where to ask help.

====================================================
Hello I bridged MXC from ETH -> to zkEVM Mainnet.

It usually bridges well, but I have two locked TXs
Please have a look at the two TXIDs in etherscan.

1. 0x5a627443880f80549e9809ae5d542a403d234161d6438a2f5456a5c13a9f3bd2
2. 0x9f3b48ee0f870fba37f0d201940200983022dceb56d1d0c74c0d0cc2d541a7f2

What can I do to receive the locked MXC?

Thank you.

When clicking the 'Next' button in the 'Send MXC Token' screen twice, the confirmation popup is displayed twice instead of once. This behavior occurs inconsistently and leads to unnecessary duplication of the confirmation process.

When attempting to bridge Sepolia to Geneva and initiating a transaction, all dapps vanish from the dapp screen. This issue prevents users from accessing dapps after completing the bridging process.

https://www.notion.so/wannsee-roadmap/Remove-telegram-support-button-7190d6621e394040aef1bd2cce03d75d

Steps to Reproduce:

Navigate to the account import screen.
Enter a public key in the private key field.
Complete the import process.
Expected Result:
The system should validate the input and reject public keys entered as private keys, ensuring that only valid private keys are accepted.

Actual Result:
The system accepts the public key as a private key, leading to potential security issues and incorrect account imports.

Impact:
This bug allows the import of accounts with incorrect keys, causing confusion and possible security vulnerabilities

Test data:
It imports account 4 with account 2's public key, and the keys for both accounts are different

Ac 4: 0xcbf8aed680ce5a3990f948dff2669246cf234b0d

Ac 2: 0x415eb794c10742a7076c3f47eff109c388d312fb

This is the task for addin and integrating blueberryring background service to AXS wallet.
Helping docs by Ian