#SJ057

1 messages Β· Page 1 of 1 (latest)

iron quiverBOT
velvet ridge
#

Looking in to how to troubleshoot this

#

To cover the obvious bases first: have you double checked that you are viewing your dashboard as the same account you are running the command as? One email can be connected to multiple accounts so I have seen this when a user was on a different account than they initially thought

signal crow
#

Yes. I am using the same account...before starting the app locally I have to log in with stripe first and then run the command stripe apps to start.

velvet ridge
#

Gotcha. Can you send me your account ID here (acct_1234)? I think I should be able to see logs around this.

signal crow
#

acct_1MARpdB57HHkN7RO

velvet ridge
#

Thank you, checking in to what I can see here

#

To be clear, has this flow ever worked for you?

#

And is this an app that you jus freshly created or is this one of our demo apps you downloaded from somewhere?

signal crow
#

I have freshly created app

velvet ridge
#

Gotcha, so literally just ran stripe apps create foo, did the dashboard actions for that, and ran stripe apps start?

#

Just checking because my next suggestion was going to be to see if that got the same error

signal crow
#

I am getting the same validation msg

velvet ridge
#

Good to know, thank you for checking. I'm going to try to pull in a colleague who is more familiar with Stripe Apps to see if they have a better idea of what to check next

signal crow
#

ok

summer roost
#

Hi πŸ‘‹

Can you take a look at the browser console when you hit the Preview page?

signal crow
#

i have open the console

summer roost
#

Do you see any error messages?

signal crow
#

Yes

summer roost
#

Okay, are the referencing CORS or CSP problems?

signal crow
#

Yes

summer roost
#

Which one?

signal crow
#

m.stripe.network/inn…on=6&preview=true:1 Access to XMLHttpRequest at 'https://m.stripe.com/6' from origin 'https://m.stripe.network' has been blocked by CORS policy: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.

#

CORS

summer roost
#

And what browser are you using?

signal crow
#

Chrome

summer roost
signal crow
#

no

summer roost
#

how are you running stripe apps start?

#

Directly on your machine or inside a container of some sort?

signal crow
#

Directly from machine

#

with stripe apps start

summer roost
#

And when you run stripe version what version number do you see?

signal crow
summer roost
#

Okay good to know, I'm glad you got it working in the end

#

As you can see this issue was created by someone here at Stripe so hopefully ( 🀞 ) it will get some attention in the near future

signal crow
#

Hoping good...Thank you @summer roost .. πŸ™‚

#

Hi @summer roost ...just wanted know ...is there any provision ...where we can find logs in local machine ?

summer roost
#

You mean logging the local server?

#

I think it would make sense to file that as an issue in the Github Repo. I think it would make sense to have a flag like stripe apps start --verbose that would return the logs from the server at localhost:4242 to the console

signal crow
#

ok..Thanks

signal crow
summer roost
#

The team working on Stripe Apps uses Github Issues for a lot of their developer feedback so it's a good place to request features like that. And it's better if it comes from you in case they have follow up questions about what sort of functionality you would expect.

signal crow
#

sure...I will add an issue over there...Thank @summer roost ..It is a great conversation....Merry Christmas..πŸŽ„

summer roost
#

And a happy new year to you!

signal crow
#

Thank You...Happy New Year πŸ™‚