Failed to fetch information about the app requesting authentication error


When I run my Blockstack app on a local npm server and redirect it to my Android app, I get the following error after clicking “Sign in with Blockstack” button in my Android application:
“Failed to fetch information about the app requesting authentication. Please contact the app maintainer to resolve this issue.”

What does it mean? What can be the problem?


You need to run npm server with SSL support on a hosted domain. This tutorial will help you:


Is there any way to solve this issue locally?


i have this issue,too,if you have already slove this problem ,please teach me


I don’t think localhost would work in this case as app URL is important to authenticate a user against. So, let’s suppose you have an xyz application with domain name. When you will authenticate a user against your app, a tag gets inserted into the profile.json that user owns. It looks like this:

"apps": {
            "": ""

and because you own that URL and control the hosting provider, that I guess is the only way to prove the controlling authority of your app.

Another reason to have it hosted is to see the process of auth. When you click on sign in button, it opens in your browser. Once, you are authenticated, needs to send you back to the app but that particular script does not know your app and you can’t edit it (maybe if you host your own copy of that, I haven’t tried doing that), so the sends you back to your hosted server to redirect and open your app on the phone and that server address should be resolvable over the internet.

If you just want to test the auth, you can use the test URLs given in this iOS example as I haven’t seen the android code yet. Caution would be to know that this is just a test server.

While you are using it, make sure the URL scheme of your app has the entry of myblockstackapp as that is what this server recognizes.


I am also going through the same issue. I depllyed it in netlify then also it is showing the same error


I face the same issue. A have a local angular 6 application, started with ng serve and in the angular.json file I have the certificate info.

“sslCert”: “ssl/server.crt”,
“sslKey”: “ssl/server.key”,


Even if you don’t have a hosted backend, you need to add a manifest.json file on a domain with


Yes the manifest.json file was not been served well! It is possible to use it with localhost.


Now, do you solve this problem?if you do,please help me beacuse I have same problem thank you


No, I couldn’t solve it. Solutions like ngrok may work, but since I don’t have time to try them, I turn back to the netlify app given in the Android tutorial.


To Configure with keys that point at a production blockstack environment that is managed on the back end as a 'brand(domain). It also supports multiple languages. In the iOS app, present the view controller to display a list of help articles. Select an article. The text of the article is displayed, but see error message ‘Failed to fetch attachments’ appear at the top of the article. I have also done this for Printer in error state.


Tried hosting the manifest.json using github pages.

It goes past the page where it requests you to select an ID, but then gets stuck at a 404, because it tries something like
Am I missing something?


Depending on the browser, your Android app should catch the view intent. Have you setup the Manifest correctly? Have you put the well-known file correctly?

Github pages does not allow you to put the well-known file in the root folder. Therefore, the Android system does not opens the app immediately.

On Firefox you can click on the Android icon next to the address bar and continue with the auth response…


Is it possible to use an existing app origin like during development ? seems to work in the react-native app, couldn’t figure out how to use it for the react-webapp


Yes, it is possible and it is a feature of blockstack that the user can choose the app they want to use to access their data. It is in the responsibility of the user to choose a trustworthy app.

You need to use redirectToSignInWithAuthRequest in order to specify the different app domain.