instagram_connect 0.3.11 → 0.3.12

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 34e72217b3285a05cf86874ad6d225bc92304f0f496381b86707b257d6e25571
-  data.tar.gz: 77fc696bff514db7f944596595a9f6e9773f14cf4993975e4933e9805bf0ab76
+  metadata.gz: 8e2491421a8ef87f13bdf5713bb30b07c92f12dc9abeffdf985ec8c4a2db04b5
+  data.tar.gz: 13dc408e540367da45330ca0d17ee785cda564312e865752d4e9635c75cd1b27
 SHA512:
-  metadata.gz: bdf866209e683e9dd48942da0027d8ee008abe7bce256dbc37cdf4809a4394a1a6ce990d5e8d38b3f08222e216d72a814445757144dc9c619938a71a682788c1
-  data.tar.gz: f6ffb8669960514dbe4a914a7f6a6f104a902cd746168e6e4e5dfc2140d5034434fd701ed9bb484eea035708940ed04bf10340e24c9aac88659c2f3df08d1d4a
+  metadata.gz: 331c2f1c32aac22c0270d59b17a0ce189bb3ceb96bd5cc389b7e4a0cb7c06e85ffbe9d14970a4362d8b0d7eaf0b07b609b14b5ae918ae0048a404743fcaf57cc
+  data.tar.gz: 824e82804b90ae2bd9f887d109e1945ddffd549e1f1e92852a985465b1cd484a29993139fb9ce474f9a14195d895aafdf2e2a4fac0351857192078bebfb1ae58

data/CHANGELOG.md

@@ -6,6 +6,19 @@ All notable changes to this project are documented here. The format follows
 
 ## [Unreleased]
 
+## [0.3.12] - 2026-07-27
+
+### Fixed
+
+- **An undecryptable access token is caught here, not by Meta.** Tokens are encrypted at rest;
+  with `support_unencrypted_data` on, a decrypt that fails (rotated or missing keys) hands the
+  ENVELOPE back instead of raising, and every Graph call then sent that JSON blob as the bearer
+  token — Meta answered `Invalid OAuth access token - Cannot parse access token` and nothing said
+  the cause was local. `Account#client` now refuses to build, stamps `readiness_error` with the
+  fix ("reconnect this Instagram account"), and raises `TokenUnreadableError`, which jobs log and
+  stop on rather than retrying forever. `Account#token_readable?` is public for host health screens.
+
+
 ## [0.3.11] - 2026-07-27
 
 ### Fixed

data/app/jobs/instagram_connect/application_job.rb

@@ -1,4 +1,11 @@
 module InstagramConnect
   class ApplicationJob < ActiveJob::Base
+    # A token this process cannot decrypt is a configuration fault, not a
+    # transient one: retrying re-raises forever and Meta only ever answers
+    # "Cannot parse access token". Log the actionable message once and stop —
+    # Account#client has already stamped readiness_error for the health screen.
+    rescue_from InstagramConnect::TokenUnreadableError do |error|
+      logger.error("[instagram_connect] #{self.class.name} aborted: #{error.message}")
+    end
   end
 end

data/app/models/instagram_connect/account.rb

@@ -24,6 +24,13 @@ module InstagramConnect
       encrypts :page_access_token
     end
 
+    # An Active Record Encryption envelope, as stored. With
+    # support_unencrypted_data on, a decrypt that FAILS (rotated or missing
+    # keys) hands the envelope back instead of raising — so an unreadable
+    # token reaches Meta as this JSON blob and comes back as the baffling
+    # "Cannot parse access token", with every call dead and nothing saying why.
+    ENCRYPTED_ENVELOPE = /\A\{"p":/
+
     # Every Instagram messaging call and the webhook subscription are Page-token
     # operations. Falling back to the user token keeps a freshly connected
     # account working until the readiness pass swaps in the Page one.
@@ -31,10 +38,30 @@ module InstagramConnect
       page_access_token.presence || access_token
     end
 
+    # False when the stored token cannot be decrypted with the keys this
+    # process has. Recovery is always the same: reconnect the account, which
+    # writes fresh tokens under the current keys.
+    def token_readable?
+      token = api_token.to_s
+      token.present? && !token.match?(ENCRYPTED_ENVELOPE)
+    end
+
+    TOKEN_UNREADABLE_MESSAGE =
+      "Stored access token cannot be decrypted with the current encryption " \
+      "keys — reconnect this Instagram account to store a fresh one.".freeze
+
     # The only place a Client should be built. Constructing one directly picks
     # up the *global* auth path, which is wrong for any host with accounts on
     # both paths — and wrong silently, which is worse.
     def client
+      # Refuse to build a client around a token Meta can only reject, and
+      # record WHY on the row so the host's health screen can say it out loud
+      # instead of every screen quietly rendering empty.
+      unless token_readable?
+        update_columns(readiness_error: TOKEN_UNREADABLE_MESSAGE.truncate(255))
+        raise InstagramConnect::TokenUnreadableError, TOKEN_UNREADABLE_MESSAGE
+      end
+
       InstagramConnect::Client.new(
         access_token: api_token,
         ig_user_id: ig_user_id,

data/lib/instagram_connect/errors.rb

@@ -22,4 +22,10 @@ module InstagramConnect
 
   # Raised when an inbound webhook fails HMAC signature verification.
   class SignatureError < Error; end
+
+  # The stored token could not be decrypted with this process's encryption
+  # keys, so it is an envelope rather than a token. Raised before any Graph
+  # call, because sending it produces only Meta's opaque "Cannot parse access
+  # token" with no hint that the cause is local.
+  class TokenUnreadableError < Error; end
 end

data/lib/instagram_connect/version.rb

@@ -1,3 +1,3 @@
 module InstagramConnect
-  VERSION = "0.3.11"
+  VERSION = "0.3.12"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: instagram_connect
 version: !ruby/object:Gem::Version
-  version: 0.3.11
+  version: 0.3.12
 platform: ruby
 authors:
 - Kshitiz Sinha