#david20432
potent flame
From what I can see that error can be triggered when some things are instantiated client-side so it is possible that that error was thrown without an API call being made per se
Are you essentially asking what your old key may look like to know how to search for it? I can check in to what the format was
cerulean dew
sort of, I'm at a loss right now because really there's only 2 keys possible in my scenario, and both have that described shape, so I was looking to see if maybe I sent null or "" or something like that
this is inside a webview on a capacitor app on iOS, maybe that is helpful somehow
potent flame
Can you send me your account ID? I can see if there are any logs of API calls that don't show up in your dashboard logs
cerulean dew
acct_1H7YlAGfc9bVPDYe
potent flame
Thank you, checking in to your requests...
Not immediately seeing them, I will consult my colleagues on this and get back to you
waxen moatBOT
cerulean dew
ok, no problem. I am interested to know if this is logged somewhere, but I understand the above about this being a clientside only deal.
Looking at it further, probably (not 100%, but likely) the sentinel value <<UNINITIALIZED>> was sent; it would be nice if this was included in the error message.
serene stirrup
Can you explain more? Do you mean you initialized with an invalid PK at some point ~expectedly?
cerulean dew
yeah, that's a bug on my part, like "this starts life in some intentionally garbage state, and it should have been set to a valid value before interacting with stripe"
I guess I never tested what stripe does with the garbage value if I hadn't initialized it properly!
I do kindly suggest including the "invalid value" in the error message.
serene stirrup
We generally don't do that with keys to avoid errant logging of secrets (consider that if you'd accidentally used your SK, you would end up with your SK logged to sentry here)
Other non-key values we do generally reflect the invalid value in the error
cerulean dew
I get that, a fine line to walk yeah.