-
Notifications
You must be signed in to change notification settings - Fork 476
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
app_not_installed error right after app uninstallation #1322
Comments
Hi @mironov Thank you for reporting this issue. I'm able to reproduce the issue by uninstalling the app and and close the setting page. We'll look more into this issue to figure out why the page doesn't navigate away after app uninstallation. Si |
Hi @mironov, thank you for raising this issue. We have applied a fix and this problem should no longer occur.. |
@zzooeeyy I just saw another instance of this error in our logs:
Could it be that the issue is not fully resolved? |
Issue summary
Before opening this issue, I have:
shopify_api
version: 14.3.0log_level: :debug
in my configuration, if applicableI believe this has started after switching to the new token exchange API.
When user uninstalls our app, that executes a background job that destroys the shop record. Shortly after, a request to our web app comes with the token of that shop:
That results in the following error:
I believe it is happening on the following lines: https://github.com/Shopify/shopify-api-ruby/blob/main/lib/shopify_api/auth/token_exchange.rb#L53-L68
However, it is not handled because error is not
invalid_subject_token
butapp_not_installed
. The error bubbles up to our controller.If that is helpful, here is the id of the error: edf7bd5b-4f17-4bf8-a35e-0bba570eb2bd-1717860642.
Expected behavior
I think the error should be handled gracefully, and
InvalidJwtTokenError
should be bubbled up instead.Actual behavior
Error is not handled.
Steps to reproduce the problem
I can't reliably reproduce this but from the logs I see the same order of steps is happening.
Debug logs
The text was updated successfully, but these errors were encountered: