Closed mdj-uk closed 1 year ago
Hi, thanks for reporting this!
As you pointed out, the API won't return protected customer information initially, so you'll need to request access to that data, as per the docs.
While in development, you still need to configure your app to receive the data, but it won't require any approvals from Shopify. You can do that by following the link in the log message, and that should unblock your calls!
Since this is working as intended, I'll close the issue, but please reopen it or report a new one if you're still having problems.
Ah, my apologies, I must have misread that page on the partner dashboard - I didn't realise there was a distinction between filling out the form to request access to those fields, and submitting for review.
Thanks for the response.
i try to save the details in the access form in Step 1
but it throws GraphQL error invalid input
my access scopes include :
write_products read_assigned_fulfillment_orders write_assigned_fulfillment_orders read_customers read_fulfillments write_fulfillments read_locations read_merchant_managed_fulfillment_orders write_merchant_managed_fulfillment_orders read_orders write_orders read_shipping write_shipping read_third_party_fulfillment_orders write_third_party_fulfillment_orders unauthenticated_read_customers
It makes no sense why they wont automatically allow access for development stores
Issue summary
Trying to obtain a list of orders via the rest admin api from the starter app (CLI 3), I get an error saying that 'this app is not approved to access REST endpoints with protected customer data'.
I'm confused because according to the documentation I should be allowed to do this in development without the app being reviewed. And I can't reasonably ask for a review when I've only written a handful of lines of code.
The app is connected to a development store and is being run in dev mode (
npm run dev
).Expected behavior
App should receive response with order data if run on a development store.
Actual behavior
Clicking the link I see this
Steps to reproduce the problem
npm run dev
and navigate to pagename routeReduced test case
Can provide if necessary.
Specifications