Yes the manifest.json file was not been served well! It is possible to use it with localhost.
1 Like
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.
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 https://blockstack-id.github.io/redirect?authResponse=eyJ0eX…
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 https://flamboyant-darwin-d11c17.netlify.com 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.
1 Like
I am getting the same error. Mine is a React app. All local. The above thread replies have not worked for me. May I ask if anyone have other ideas? I am new to both Blockstack and React. Appreciate your anticipated replies. Thank you. Cheers!
@dartman100.id.blocks I found that using https:// in your manifest file creates a problem with Blockstack’s auth - regardless of a SSL certificate or not. Your manifest file should use http:// url in production for the "start_url": value if you’re deploying to Netlify.
So this is my situation: I went through the hello, blockstack tutorial, and when it came time to run npm start and authenticate, (locally) the app opened up by default in Safari. Clicking “Sign in with Blockstack” returned the same error everyone is mentioning here.
I navigated to localhost in google chrome and I was able to sign in with blockstack just fine. Why is that? What would allow for this to work in Google Chrome but not in Safari?
Thank you in advance!
Have a look in the console. You will find more details why it failed. Mostly it is about security settings in the browser. Sometimes it also helps to use 127.0.0.1 instead of localhost…
Thank you for your response!
The console is telling me that the page is not allowed to display insecure content from manifest.json–I changed from localhost to 127.0.0.1, however this did not work either.
So you are right, it is a security setting of the browser, but obviously I do not want for people who are using safari to encounter this issue. From what you are saying, and from what I have read in previous posts, it seems that this will it clear itself up (for users on the front-end) once the manifest.json is actually attached to a domain instead of localhost. Is that correct.
If you have setup your CORS headers correctly there shouldn’t be any difference between safari and chrome browser.
I have the same issue. I am currently developing an app with Ionic 4 using React and Capacitor which should be deployed to both Android and iOS.
I am not really sure what the problem is. Can you help me out?
Same issue. In my case i’m facing the issue using the provided examples giving for “photobucket” and blockstack ios
Error = apple.AuthenticationServices.WebAuthenticationSession Code=1 “(null)”
Hay same issue as @dev-tj
Browser output:
Access to fetch at ‘http://localhost:8100/manifest.json’ from origin ‘https://browser.blockstack.org’ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource. If an opaque response serves your needs, set the request’s mode to ‘no-cors’ to fetch the resource with CORS disabled.
GET localhost:8100/manifest.json net::ERR_FAILED
I have the following output:
Access to fetch at ‘http://localhost:8100/manifest.json’ from origin ‘https://browser.blockstack.org’ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource. If an opaque response serves your needs, set the request’s mode to ‘no-cors’ to fetch the resource with CORS disabled.
GET localhost:8100/manifest.json net::ERR_FAILED
So, you should enable cors headers or use a cors browser plug-in.
1 Like