instagram_connect 0.3.4 → 0.3.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 6d411544448610a0b11fa1efc08960a9999008117c8a17f8119311f45ae55764
4
- data.tar.gz: bb5c2ec09be740aa03358058b64468fa9e415d7046b003fdd065da499d8488cf
3
+ metadata.gz: d196a916e3801d14b1247878e731491aedc6adcdae7a50b58751d548be182c47
4
+ data.tar.gz: aa43252a57668076b9c8aa72e9ccc605110157ff8437a16d1129482deb091a4f
5
5
  SHA512:
6
- metadata.gz: 02257cd24bb80798df5cc576ac7ccf62dc9efcdde4458b1697bc48e4971bea86927d471e46739ca858c48e3a7c69926ed64518dea62b27ccaa097bc9ccc0f61c
7
- data.tar.gz: d617a13ad8229ce7a3d53f46a8aadba6974ce06de7f81e8fe462cb69d3e550d4bc87f71ec793abf89fd97163c4f37a0348ec0ac07da9a1549190bd9874a46ee0
6
+ metadata.gz: 995e9d1bbd96a6aa57616b8b9cec8558fe02ef75623d28ac2707ec1bcd3e852d32fa69548a4dcb7cfdbcc2c35154b881d2d27426cb5e1536decec38860b1dc8a
7
+ data.tar.gz: 917737599c1ab1ef4eafe5cfc210e23d66c10f230dda1e882664fc76732c5321d8a2ee54bb3e0b2084f020d4dc085ea357d186a57f022f67490d50970113bf0d
data/CHANGELOG.md CHANGED
@@ -6,6 +6,28 @@ All notable changes to this project are documented here. The format follows
6
6
 
7
7
  ## [Unreleased]
8
8
 
9
+ ## [0.3.5] - 2026-07-26
10
+
11
+ ### Fixed
12
+
13
+ - **`pages_messaging` was never requested, so the Page could never be subscribed and Meta delivered
14
+ nothing.** The permission is checked when subscribing a Page to the app — not when calling the
15
+ messaging endpoints — so its absence broke nothing visible and stopped every webhook:
16
+
17
+ ```
18
+ (#200) To subscribe to the messages field, one of these permissions is needed: pages_messaging
19
+ ```
20
+
21
+ `subscribed_apps` rejects the entire call on the first field it cannot authorise, so a published
22
+ app holding a valid Page token, with every dashboard field ticked, received nothing at all.
23
+
24
+ ### Upgrading
25
+
26
+ Existing accounts hold a token issued before this scope existed and **must reconnect** — a token's
27
+ scopes are fixed at issue. The host's Meta app also needs a use case that offers `pages_messaging`
28
+ ("Engage with customers on Messenger from Meta"); the Instagram and Pages use cases do not.
29
+
30
+
9
31
  ## [0.3.4] - 2026-07-26
10
32
 
11
33
  ### Fixed
@@ -7,6 +7,17 @@ module InstagramConnect
7
7
  class FacebookLogin < Strategy
8
8
  GRAPH = "https://graph.facebook.com".freeze
9
9
  DIALOG = "https://www.facebook.com".freeze
10
+ # pages_messaging is what Meta checks when subscribing the PAGE to this app,
11
+ # not when calling the messaging endpoints — so its absence failed silently
12
+ # in the one place nothing was watching:
13
+ #
14
+ # (#200) To subscribe to the messages field, one of these permissions is
15
+ # needed: pages_messaging
16
+ #
17
+ # subscribed_apps rejects the whole call on the first field it cannot
18
+ # authorise, so without this scope the Page is never subscribed and Meta
19
+ # delivers nothing — for an app that is published, holds a valid Page
20
+ # token, and looks correct at every other step.
10
21
  DEFAULT_SCOPES = %w[
11
22
  instagram_basic
12
23
  instagram_manage_messages
@@ -15,6 +26,7 @@ module InstagramConnect
15
26
  pages_show_list
16
27
  pages_manage_metadata
17
28
  pages_read_engagement
29
+ pages_messaging
18
30
  ].freeze
19
31
 
20
32
  def graph_host
@@ -1,3 +1,3 @@
1
1
  module InstagramConnect
2
- VERSION = "0.3.4"
2
+ VERSION = "0.3.5"
3
3
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: instagram_connect
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.3.4
4
+ version: 0.3.5
5
5
  platform: ruby
6
6
  authors:
7
7
  - Kshitiz Sinha