#sam_code
desert hedgeBOT
👋 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/1491492331440832692
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- sam_api, 5 hours ago, 13 messages
gray gate
Thanks @ynnojo for looking into this! Here's the full timeline of what happened:
1. Started on sandbox — Created com.nance.nance-connector as a private app on our sandbox account. Uploaded v0.0.1 successfully (no OAuth). Then discovered that OAuth requires distribution_type: "public", which sandbox doesn't support.
2. Moved to live account — Tried to upload com.meetnance.connector as a public OAuth app to our live account. Got "App id already taken" because com.nance.nance-connector was already registered on sandbox. Created a new app with ID com.meetnance.erp-connector instead.
3. All uploads to com.meetnance.erp-connector fail — Every version (0.0.1 through 0.0.13) uploads successfully from the CLI ("✔ Uploaded") but then shows "Error" in the dashboard with "Something went wrong on our end."
App IDs used across attempts:
| App ID | Account | Distribution | OAuth | Result |
|---|---|---|---|---|
com.nance.nance-connector |
Sandbox | Private | No | ✅ v0.0.1 worked |
com.meetnance.connector |
Live | Private | No | ✅ v0.0.1 worked |
com.meetnance.erp-connector |
Live | Public | Yes | ❌ All versions fail |
com.meetnance.nance-payment-connector |
Live | Public | Yes | ❌ "Already has a public app" |
So only the public + OAuth combination fails. Both private (no OAuth) apps uploaded fine. The manifest is correct per docs — we've tried every combination of CSP, icon, permissions, and views.
Could the existing apps on the account be interfering? Or is there a server-side issue specifically with processing public OAuth apps?
Is there also a way to delete apps?
{
"id": "com.meetnance.erp-connector",
"name": "Nance ERP Connector",
"version": "0.0.13",
"icon": "./icon.png",
"ui_extension": {
"views": [
{
"viewport": "stripe.dashboard.home.overview",
"component": "Home"
},
{
"viewport": "stripe.dashboard.customer.list",
"component": "Customers"
},
{
"viewport": "stripe.dashboard.customer.detail",
"component": "CustomerDetails"
}
],
"content_security_policy": {
"connect-src": [
"https://app.meetnance.ai/oauth/"
],
"image-src": [
"https://app.meetnance.ai/assets/"
],
"purpose": "Allow API calls to Nance backend"
}
},
"permissions": [
{
"permission": "balance_read",
"purpose": "Read balance for ERP reconciliation"
},
{
"permission": "charge_read",
"purpose": "Read charges to match with invoices"
},
{
"permission": "payout_read",
"purpose": "Read payouts to reconcile bank settlements"
},
{
"permission": "customer_read",
"purpose": "Read customer names for ERP matching"
}
],
"allowed_redirect_uris": [
"https://xxxxxx.ai/oauth/callback",
"https://staging-xxxxx.europe-west4.run.app/oauth/callback",
"https://xxxx.ngrok.app/oauth/callback"
],
"distribution_type": "public",
"stripe_api_access_type": "oauth"
}
acct_1THfm5PS2xeRt6Ll
thin basin
Hi there - I'll be with you in just a moment
looking now
I'm reaching out to the folks that maintain the github repo as I'm not super familiar with this
gray gate
Thanks, I tried a lot of different setups for the manifest but cant seem to get any error message or guidance....
thin basin
Waiting on a response to see if they want to handle this on the github issue or if they have some quick comments, or if they want to have a support case
desert hedgeBOT
west wasp
Haven't heard back internally yet so it will better to create a support case for this. You should get sent instuctions on how to do so momentarily
desert hedgeBOT
Hello @gray gate, we have sent you a direct message, please check it at https://discord.com/channels/@me/1491510454101479454
- 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
gray gate
Hmm no solution..?
west wasp
Apologies, I may have misunderstood my colleague when jumping on the server. Clarifying next steps now. We don't have other suggestions for fixes at the moment though unfortunately.
Okay we are aligned that working through that case is the way to go forward. I will send a quick followup email through that case to confirm I've picked it up shortly and will send updates from my colleagues there on the investigation into the issue.
gray gate
I cant be the first to try to create a simple public app with oauth authentication right?
west wasp
You aren't, the reason for the case is moreso that my specific team doesn't have anyone online right now that knows how to debug your issue further. So I need to raise this with colleagues that are more familiar with this and work with them. For things like that we get back async through cases.
gray gate
Okay thanks