-
-
Notifications
You must be signed in to change notification settings - Fork 35
fix(ios): Add OnsideKit as a default dependency in ExpoIap.podspec #321
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
Open
retweakr
wants to merge
6
commits into
hyochan:main
Choose a base branch
from
retweakr:fix/onside-kit-podspec
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
34c8e6a
fix(ios): Add OnsideKit as a default dependency in ExpoIap.podspec
b1f7ccc
refactor(ios): Move OnsideKit to a subspec in ExpoIap.podspec and upd…
6b49a29
fix(ios): Adjust OnsideKit and ExpoIap/Onside handling in Podfile log…
498680c
fix(ios): use subspec for conditional OnsideKit dependency
hyochan 15fa2b5
fix(ios): use post_install hook for OnsideKit visibility instead of s…
hyochan 0057e54
fix(ios): simplify OnsideKit integration with subspec approach
hyochan File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: hyochan/expo-iap
Length of output: 838
🏁 Script executed:
Repository: hyochan/expo-iap
Length of output: 2087
🏁 Script executed:
rg -A 10 "subspec.*[Oo]nside" ios/ExpoIap.podspecRepository: hyochan/expo-iap
Length of output: 297
🏁 Script executed:
Repository: hyochan/expo-iap
Length of output: 362
🏁 Script executed:
Repository: hyochan/expo-iap
Length of output: 3759
🏁 Script executed:
Repository: hyochan/expo-iap
Length of output: 3131
🏁 Script executed:
Repository: hyochan/expo-iap
Length of output: 330
🏁 Script executed:
Repository: hyochan/expo-iap
Length of output: 653
🏁 Script executed:
rg -n "OnsideKit" README.md docs/Repository: hyochan/expo-iap
Length of output: 42
🏁 Script executed:
Repository: hyochan/expo-iap
Length of output: 145
🏁 Script executed:
Repository: hyochan/expo-iap
Length of output: 42
🏁 Script executed:
Repository: hyochan/expo-iap
Length of output: 1255
ExpoIap/Onsideinjection will break pod install for Onside-enabled users due to unresolvableOnsideKitdependency.The Onside subspec (ios/ExpoIap.podspec:32) declares
ss.dependency 'OnsideKit', butOnsideKitis not available on the public CocoaPods CDN (HTTP 404). When users enable Onside via the plugin, pod install fails during dependency resolution. The plugin must either inject a CocoaPods source forOnsideKitor implement an alternative dependency resolution strategy. Currently, documentation presents Onside as ready to use with "Easy Setup," but enabling it produces a broken build.🤖 Prompt for AI Agents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Acknowledged — this is a known blocker. OnsideKit is not on CocoaPods CDN yet (confirmed by the OnsideKit team). We've asked them to publish it. Once it's on CDN, this subspec approach works as-is with no code changes needed. This PR is intentionally written for that scenario.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hyochan, understood — thanks for the context. Since this approach is intentionally forward-looking for when OnsideKit lands on the CDN, that makes sense.One optional suggestion: it may be worth adding a temporary
WarningAggregator.addWarningIOSnote insideensureOnsidePodIOS(or in the docs) to surface a clear message to users who enable Onside before OnsideKit is published — so they get an actionable error rather than a crypticpod installfailure. This can be removed once CDN availability is confirmed.That said, if you prefer to keep it minimal until the CDN publish is done, that's reasonable too.
✏️ Learnings added
🧠 Learnings used