FAQ

Why my application cannot detect MSafe environment / `MSafeWallet.inMSafeWallet` returns false?

MSafe wallet itself is a web application. You need to open your application within the MSafe App store. For example for partner endpoint, you may replace ${YOUR_URL} in the following link to access your application on Testnet.

https://testnet.m-safe.io/apps/0?url=${YOUR_URL}

Upon connecting the MSafe wallet, why application is redirected to MSafe?

To interact with MSafe wallet, application need to talk to the MSafe application in the parent frame. So MSafe wallet adapter will automatically redirect to the MSafe application page if MSafe environment is not detected. This is an automatic bahavior as expected.

Why my application cannot connect to MSafe wallet?

1. Make sure you are using the latest MSafe wallet code, and follow the instructions using MSafe SDK or Aptos-wallet-adapter.

2. You are opening your application within the MSafe application. E.g. https://testnet.m-safe.io/apps/0?url=${YOUR_URL}.

3. You have created at least one MSafe wallet.

Why my UI interface does not show up on MSafe page?

Please check whether you have created at least one MSafe wallet. We will add more prompt for better user experience later.

How to tell whether my application works with MSafe?

1. Open your application in MSafe app store with your application's URL. (E.g. https://testnet.m-safe.io/apps/0?url=${YOUR_URL})

2. Connect your wallet, and wallet is connected to MSafe address.

3. Submit a transaction within your application, the transaction displays in the transaction queue page.

4. After enough signatures are collected, the transaction is submitted on chain.

5. If you have created multiple MSafe wallets, switching the address will result in connected wallet address change in your application. Please see onAccountChange for details.

Why `signAndSubmit` does not resolve the promise?

In multi-sig use case, signAndSubmit is the wallet manager submitting the transaction proposal for MSafe wallet. The transaction with the application's logic can only be executed after collecting enough signatures from the MSafe managers, which will take days to finish. Thus, in the current implementation, signAndSubmit transaction will not be resolved.

Is there any improvements for better user experience?

Yes.

We suggest automatically detect and connect MSafe wallet so that user does not need to connect wallet and select MSafe manually.

Please check out https://app.m-safe.io/apps/Tortuga for example.