ann-flavor-cocoapods 0.4.4 → 0.4.5

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 26c819f56bb3a959737651233fbdbed8e0bd887ddcdfbf0fd0c157c26b99a011
-  data.tar.gz: d322f020327b3b62f3eb02922a01d1af90040a2b5595614a37795eacf311a2cf
+  metadata.gz: 308ae984ebc6057da442a37d87cda0ccaa0f110b5044ac8a1a84233390398dfb
+  data.tar.gz: 36e009d9eab357e286766fec9bcd31edc383237c8c17e027843380792f52a0d9
 SHA512:
-  metadata.gz: 85564c5fcc276b9f448381fc8cb3d334ca65d9bedbccd2b40fe25b46e43775afc50f66b7a2c6394ab032a118ecb8e3b1335b596c89f0c5dc79d7945bc52bc7ac
-  data.tar.gz: e2e76a0da4568f8bc5a040d1f3f0422a8844b1da28b0b34b6324fda2c56d7c47eceec963ae644c82044f266b20193fe29d9572cce60a7dbf59933ac8df9a2221
+  metadata.gz: 8efac100a09e6c88be9c283379c2d17f8fac58c3f40281f4f3f87b35f687a89a024595c74839fa80f973236514d87608090498737ff1fb93f79a7d400f6c9dec
+  data.tar.gz: e46fe48609f35471fc48f101e95cc2804d82a7d2fa474cccdeb9f3438f3a06b8215837d7eeb19e844aee1a0604a0709aae0b0a0d56f3bd5e2115126f89a378e9

data/CHANGELOG.md

@@ -1,5 +1,25 @@
 # Changelog
 
+## 0.4.5
+
+### Fixed
+- **0.4.4 stopped the cycle for a *fresh* install, but any project already
+  on 0.4.1-0.4.3 kept hitting it after upgrading.** 0.4.4 stopped *setting*
+  `input_paths` on `[ann-flavor] Merge Entitlements`/`Merge Info.plist`, but
+  never explicitly *cleared* it. `existing = target.build_phases.find { ... }`
+  reuses the same Xcodeproj object across runs, and `pod install` never
+  touches an attribute it doesn't assign — so a project that had already run
+  0.4.1-0.4.3 (which did set `input_paths` on that same, reused object) kept
+  the stale value forever, silently reintroducing the exact "Cycle inside
+  Runner" failure 0.4.4 was meant to remove. Confirmed live against `ledger`:
+  the cycle came back, now involving whichever framework happened to be on
+  the other side of the shared `ModuleVerifierTaskProducer` gate (in this
+  case an SPM-resolved `AppLovinAdapter.xcframework`, following the
+  consumer's separate SPM plugin migration — same underlying mechanism, not
+  a new bug). Fixed by explicitly setting `phase.input_paths = []` on both
+  phases, so a stale value is genuinely wiped on the next `pod install`, not
+  just left unset going forward.
+
 ## 0.4.4
 
 ### Fixed

data/lib/ann_flavor_cocoapods/podfile_helper.rb

@@ -912,11 +912,17 @@ module AnnFlavorCocoapods
       # output_paths) -- suppresses "input file not found" for INFOPLIST_FILE
       # referencing a path nothing else produces until this phase runs.
       phase.output_paths = ['$(DERIVED_FILE_DIR)/Info-merged.plist']
-      # NOT declaring input_paths on Check Pods Manifest.lock's output here
-      # (tried in v0.4.1) -- see the identical, fuller explanation on
-      # inject_merge_entitlements_phase below for why that direction was
-      # actually the cause of the real "Cycle inside Runner" failure, not a
-      # (partial) fix for it.
+      # Explicitly cleared, NOT just omitted -- v0.4.1-0.4.3 set input_paths
+      # to Check Pods Manifest.lock's output; v0.4.4 stopped setting it (see
+      # the identical, fuller explanation on inject_merge_entitlements_phase
+      # below for why that declaration was actually the cause of the real
+      # "Cycle inside Runner" failure, not a fix for it), but never explicitly
+      # cleared it -- `existing` reuses the same Xcodeproj object across runs,
+      # so a project that upgraded from 0.4.1-0.4.3 kept the stale value
+      # forever (pod install never touches an attribute it doesn't assign),
+      # silently reintroducing the exact cycle 0.4.4 was meant to fix.
+      # Confirmed live against ledger.
+      phase.input_paths = []
 
       # Appended at the END of build_phases, not unshifted to the front --
       # see the identical, fuller explanation on inject_merge_entitlements_phase
@@ -1048,6 +1054,14 @@ module AnnFlavorCocoapods
       # output_paths + running after the Pods/framework-copy phases (via
       # position, below) is sufficient on its own.
       #
+      # Explicitly cleared (not just omitted) -- `existing` reuses the same
+      # Xcodeproj object across runs, so a project that upgraded from
+      # 0.4.1-0.4.3 kept the stale input_paths value forever (pod install
+      # never touches an attribute it doesn't assign), silently
+      # reintroducing the exact cycle this fix was meant to remove.
+      # Confirmed live against ledger.
+      phase.input_paths = []
+      #
       # Appended at the END of build_phases, not unshifted to the front.
       # v0.4.1 tried fixing this phase's real "Cycle inside Runner" Xcode
       # build failure (confirmed live against ledger, a project with real

data/lib/ann_flavor_cocoapods/version.rb

@@ -1,3 +1,3 @@
 module AnnFlavorCocoapods
-  VERSION = "0.4.4"
+  VERSION = "0.4.5"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: ann-flavor-cocoapods
 version: !ruby/object:Gem::Version
-  version: 0.4.4
+  version: 0.4.5
 platform: ruby
 authors:
 - ANN Solutions