Our app, Filta, has recently added coinbase wallet support. When we connect, per the developer documentation, it works, but the “Allow Connection” screen in Coinbase wallet app has a big red text that says “this mobile dapp can not be authenticated. Please proceed with caution.” What do we have to do to authenticate our app so users don’t see scary red text?
Hello @cdiddy77! Thank you for taking an interest in trying out Coinbase APIs. For the details regarding your concern, we will check on this for you with our team. We will get back to you once we have more information. Keep in touch!
Hi @cdiddy77! We’ve seen your concern. We’re already looking into it and are still working with the teams to ensure this is addressed accurately for you. We will get back to you once we have more information. Thank you for your patience!
Hello @cdiddy77! Apologies for the delayed response. Can you please send us a screenshot that demonstrates your concern? Please blur any sensitive information. Thank you!
Hello @cdiddy77! Thanks for providing us with the screenshot. Can you confirm if your app is a developer build/sideloaded or is it distributed through the app store? We’ll wait for your response. Thanks!
hello, the program doesn’t work, dapp wallet keeps giving my passport and the advice is not good, I don’t know what to do, I asked for help and nothing helped at all
@Daniela - I am sorry that you are experiencing issues with the Dapp wallet. Unfortunately, this is a Coinbase developer tools forum and we do not have the correct resources here to assist with individual issues with retail products. Have you submitted a request here - https://help.coinbase.com/en/contact-us?
Getting the same red error message “this mobile dapp can not be authenticated. Please proceed with caution." for Android too, how can android resolve this
I’m also curious about how to remove the red warning for iOS and Android. And also how to say to the Coinbase app what is the server where the AASA file is.
I figured out, that the red warning disappears when I use a universal link as a callback URL. But there is an issue. The user is able to cancel opening universal links in the app in Safari and in that case, the app is not opened with the callback.
Is it possible to use a custom scheme as a callback (that is working now as well but with the red warning) and for example define the app’s URL in config as the identification of the app to avoid the red warning rectangle?