#aeo_error
1 messages Β· Page 1 of 1 (latest)
π Welcome to your new thread!
β²οΈ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
β±οΈ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
π This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1471648917408977007
π Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi there. Can you share the request that's failing, if possible? I'm looking for a req_123 id
one second... sorry, account rep responding as well...
through the API, it never finishes to get a req... it is unhandled exception from stripe SDK
when I go to the dashboard, and view the connected account as me, and attempt to enable the terminal feature... i get this error:
upon further inspection, it appears maybe there is some corrupt data at stripe. and the SDK is choking on it
req_dMvekfWq9e0puL
that was a get request to pull the readers, but the C# sdk blew up trying to serialize the results to me?
interesting. Could you give me what you logged from that request?
ya, one sec
that was on the create... let me find the get
that was the GET request to pull the readers by location
same thing really... the Create POST request, was calling the same function to serialize it back to a reader object
not sure where the real problem is... although I find it interesting that it errors trying to enable terminals.. which I thought was the problem... but maybe they are related in some way
Would it be possible to get the exact url from the dashboard screenshot you sent above?
I am wondering if there is a real restriction/incapatiblity here and we're just not handling it gracefully in the SDK
possibly.. that would make sense... where the restriction is in place, but the create location and create terminal endpoints aren't following the rules, and allowing the call to be made...
one more piece of information, please - could you give me the code that makes the call that's blowing up in the c# sdk?
just the stripe bit
either one at that point eh? this is the get
public List<Reader> GetTerminalsAtLocation(string locationId) {
var service = new ReaderService();
var options = new ReaderListOptions {
Location = locationId,
Limit = 100
};
var readers = service.List(options, GetAccountLevelRequestOptions);
return new List<Reader>(readers.Data);
}
GetAccountLevelRequestOptions, just adds our api key, and the connected account it
id*
it blows up on service.List
π
does that mean "retry" ? if so, i did, and it blew up still
Sorry I wanted the :loading: reactji but we don't have it in discord I guess
i see π
Hey! Taking over this thread, do give me some time to catch up!
no worries... let me know if you need anything else answered
using the CLI and running: stripe terminal readers list --stripe-account acct_1Sg8idAjxmkU1mQB
it looks like good data... but the SDK is not liking it for some reason
Right, so there seems to be two questions here:
- The error that appears on the dashboard. but it still allows you to call the create location and terminal buttons/endpoints
- The error from the simulated reader
i guess that's accurate
i'm not really that worried about the dashboard honestly... because it looks different in prod.... i only brought it up because I originally thought that was the whole problem.... but really now, i think its just the data issue or whatever is happening with the sdk.
but maybe they are related in a way i'm not privy to... i really dont know.
Regarding the first issue, I managed to recreate it using my own Platform account on a connected account (UA2).
The reason for the error is that you do not have permission to turn the feature on; that permission belongs to the connected account, who has full dashboard access. Therefore, when you tried to activate it, you received an error
That being said, you are right that they are separate issues
I am downloading the sample code for C#
interesting on the first issue... i'll have to bring that up with my account rep, on how to deal with it.
for the second issue, did you use https://docs.stripe.com/terminal/quickstart forthe simulated reader?
not exactly... i did call create location and create reader enpoints though..
for a "connected account" obviously.. that also didn't have "terminal" turned on... as you discovered...
i'm gonna try something.... i think i still have the login for that test account in sanbox, maybe I log into that account, and enable terminal... then see what the call does....
Could you try this endpoint in your browser: https://dashboard.stripe.com/acct_1SNwQgAX55J9SsmJ/connect/view-as/acct_1Sg8idAjxmkU1mQB/test/terminal
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
And take a screenshot of what you see?
Hmmm, thats strange, for mine, although i get that same error when i tried to activate it, I am still able to see the Terminal dashboard page and click the buttons there
We might need additional time to look into this
Could I trouble you to write in to out team for this?
Hello @uneven folio, we have sent you a direct message, please check it at https://discord.com/channels/@me/1471666848004309155
- πThe message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
sorry... was away for a sec
ok, logged into that test account, and enabled it as the "real"" account user... testing the call again
still blows up..
dratz
Hmm, with regard to the API call here, could you try to use the sample code from our quickstart guide: https://docs.stripe.com/terminal/quickstart?platform=server-driven&lang=dotnet
- Download our .net example code with "Download guide"
- Amend the Code to include your connected account in RequestOptions
- Check if the issue still persists
not sure how the helps....not trying to be dismissive of the idea... but the CLI call to: stripe terminal readers list --stripe-account acct_1Sg8idAjxmkU1mQB is the same as the List in the SDK... and the CLI returns data, but the SDK blows up using the same data... not sure that using the quickstart changes much?
i called the SDK to create the terminal like this: var service = new ReaderService();
var options = new ReaderCreateOptions {
Location = locationId,
RegistrationCode = "simulated-s700",
Label = "Simulated Terminal"
};
return service.Create(options, GetAccountLevelRequestOptions);
and the location like this: var service = new LocationService();
var options = new LocationCreateOptions {
DisplayName = loc.Description,
Address = new AddressOptions {
Line1 = address.Address1,
Line2 = address.Address2,
City = address.City,
State = address.State,
PostalCode = address.Zip,
Country = address.Country == "USA" ? "US" : "CA"
},
Metadata = new Dictionary<string, string> {
{ "uschedule_locationId", loc.Id.ToString() }
}
};
return service.Create(options, GetAccountLevelRequestOptions).Id;
going to try and upgrade to 50.3 from 49.2 SDK version..
@oblique tapir issue resolved itself with 50.3
looks like it was resolved in https://github.com/stripe/stripe-dotnet/issues/3253
sorry, i didn't check for this first... i guess.
I took a closer look at the dashboard error that was observed.
I understand that you were using the "View Dashboard as..." feature to access the connected account. This may have provided you with a limited set of permissions rather than the full permissions necessary to perform certain tasks on the connected account.
yeah... i'm not sure how to deal with this issue yet. i'll have to chat with my account rep, i want to make enabling terminals as seamless as possible for my connected accounts, but maybe thats just having "terminal" turned on by default on new accounts... i really dont know
Hmmm, actually, if you are able to create a terminal reader for the connected account, as seen in this request here: req_y8wbLsGjk7kbQ1, they should already be able to use Stripe's terminal products.
It just that when you tried to access the page through "view dashboard as", it gave you limited permission.
oh, interesting.. well... it might not be a problem in prod... cause things looked different....
Just to confirm that they have access to Stripe's Terminal product, could you allow me access to view the connected account?
when I did the "view as" thing in prod, i was able to get to the terminal page, without the "click here to signup" modal
Hello @uneven folio, we have sent you a direct message, please check it at https://discord.com/channels/@me/1471666848004309155
- π The message has instructions on how to grant read and write access to your Stripe Dashboard for our Developer Support team, in order to help you more effectively.
my sandbox?
I just sent you a DM for view access to your account
approved it
taking a look!
Yup, I think the account acct_1Sg8idAjxmkU1mQB is already able to access the terminal dashboard page
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
that's cause when I was trying to debug this whole thing... one of the steps I took was to login to that account with the "real" user, and enable it manually
I see, hmmm, if it happens again then i would recommend you to reach out to Stripe Support -Β Β https://support.stripe.com/contact
but when that didn't work, SDK call.. i tried updating the version of the sdk, and then that fixed it and I found the issue mentioned in update logs
Right
but it was "interesting" that it let me create the location and terminal... without the "feature" being on yet...
i'm not sure what would have ahppened if I tried to process a pyament
that might be a "sandbox" thing as well... not really sure... but not really wanting to invest time into figuring that out π
Yeap, i agree that it could be a sandbox thing, but even if it was, it is a frustrating user experience, sorry for that.
If it happens again, could you write in to us at Stripe Support - https://support.stripe.com/contact ?
well... its "sort of" my fault for using a 3 month old SDK ... lol.
but yeah... no worries for now... testing has progressed past my roadblock... until the next one...
thanks for your help... btw i really love your product as a dev... so many cool things
Happy to be of help! Thats nice to hear that you are enjoying our products π
first time chatting with discord... not sure how to end this... but if you need to click something or whatever.... i don't have anymore questions related to this issue.