Closed arturgontijo closed 2 months ago
If I remove read_shopify_payments_dispute_evidences
I am able to deploy the app, but when I try to query evidences, I get this:
{
"errors": [
{
"message": "Access denied for disputeEvidence field. Required access: `read_shopify_payments_dispute_evidences` access scope.",
"locations": [
{
"line": 1,
"column": 3
}
],
"path": [
"disputeEvidence"
],
"extensions": {
"code": "ACCESS_DENIED",
"documentation": "https://shopify.dev/api/usage/access-scopes",
"requiredAccess": "`read_shopify_payments_dispute_evidences` access scope."
}
}
],
"data": {
"disputeEvidence": null
},
"extensions": {
"cost": {
"requestedQueryCost": 2,
"actualQueryCost": 1,
"throttleStatus": {
"maximumAvailable": 2000.0,
"currentlyAvailable": 1999,
"restoreRate": 100.0
}
}
}
}
If I use use_legacy_install_flow = true
I am able to deploy it:
But when I try to Oauth my store, I get this:
Thanks for getting in touch about this! The scope you mentioned is for payments apps only. Your app doesn't seem to be a payments app. You can learn more about payments apps here.
Hey @amcaplan, thank you so much for the reply (it's been a while since we've been trying to understand this error)
First of all, we do not want/need to handle any payment logic. With that said is it still necessary to apply for the "Payments Partner application" just to keep track of disputes (this can be done without it) and their evidences?
If so, wouldn't it be better to make CLI flag it while trying to deploy the app?
First of all, we do not want/need to handle any payment logic. With that said is it still necessary to apply for the "Payments Partner application" just to keep track of disputes (this can be done without it) and their evidences?
At present, the Payments Apps platform is invitation-only, and that applies across the payments API. Details here
If so, wouldn't it be better to make CLI flag it while trying to deploy the app?
Can you explain where in the process you'd expect to see this issue brought up?
Can you explain where in the process you'd expect to see this issue brought up?
If we run shopify app deploy
with the scopes = "read_shopify_payments_dispute_evidences"
in its TOML file, we get:
╭─ error ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ Version couldn't be created. │
│ │
│ app-access │
│ │
│ Validation errors │
│ • scopes: read_shopify_payments_dispute_evidences │
│ │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
At least for me, that's not helpful at all...It would be great to have more assertive error message like:
│ Validation errors
│ • restricted scopes: read_shopify_payments_dispute_evidences
Maybe also point it out to one of those links that you've shared.
But yeah, I think we can close this issue. Thanks again!
Thanks, this is a great point. I've passed on your feedback to the relevant internal team. Closing out this issue for now.
Please confirm that you have:
In which of these areas are you experiencing a problem?
App
Expected behavior
Be able to release an app with the following scopes:
It would be great to also have:
Actual behavior
Verbose output
Reproduction steps
scopes = "read_orders,read_customers,read_products,read_files,write_files,read_shopify_payments_payouts,read_shopify_payments_disputes,read_shopify_payments_dispute_evidences"
toshopify.app.toml
npx shopify app deploy --verbose
Operating System
Mac OS Sonoma 14.5
Shopify CLI version (check your project's
package.json
if you're not sure)3.65.1
Shell
zsh 5.9
Node version (run
node -v
if you're not sure)v20.12.2
What language and version are you using in your application?
Node v20.12.2