docs(flutter ui kit): the documented platform floors cannot be built against - #500
Merged
raj-dubey1 merged 1 commit intoSep 8, 2026
Conversation
raj-dubey1
force-pushed
the
docs/skills-v5-temp
branch
from
September 8, 2026 11:26
26ffabb to
d35f9fd
Compare
raj-dubey1
requested review from
mathews-cometchat and
raj-dubey1
as code owners
September 8, 2026 11:26
…against `ui-kit/flutter/getting-started` says `minSdk = 24` and `platform :ios, '13.0'`; `call-features` says `minSdkVersion 24` and `platform :ios, '12.0'`. **No Flutter UI Kit app can satisfy any of those**, and the failure is a build error, not a warning. ## Why `cometchat_chat_uikit` 6.1.1 depends on **`cometchat_calls_sdk` unconditionally** — it sits in the main `dependencies:` block, not behind an opt-in — and that package pins `minSdkVersion 26` and `platform :ios, '15.1'` (5.0.7; iOS was 13.0 through 5.0.6). Gradle and CocoaPods both take the **maximum** across the dependency graph, so a lower app-level value is a manifest-merger error on Android and a failed `pod install` on iOS. Proof rather than inference — resolving a pubspec whose only dependency is `cometchat_chat_uikit: ^6.1.0`: ``` cometchat_chat_uikit direct main 6.1.1 cometchat_calls_sdk transitive 5.0.7 cometchat_sdk transitive 5.0.7 ``` ## Why it was easy to get wrong The kit's own AAR really does allow `minSdkVersion 21`, and its own podspec really does say `9.0`. Reading the kit in isolation gives a lower answer; only the resolved graph is right. The documented 24 looks like it came from exactly that reasoning — close, and still unbuildable. ## The fix Both pages now say `minSdk = 26` and `platform :ios, '15.1'`, each with a short note saying **why** — that the Calls SDK comes along with the kit whether or not the app uses calling, and that the maximum across the graph is what binds. On `call-features` that note matters twice, since a reader there is enabling calling and would otherwise assume the floor is calling's price rather than the kit's baseline. ## Scope Current (unversioned = v6) pages only. The archived `ui-kit/flutter/v4/` and `ui-kit/flutter/v5/` trees are left alone — they document older versions with their own floors. This is a different page tree from the `/calls/flutter` corrections in cometchat#492, which is why it is a separate PR. Companion skills change: 10 sites across 8 `cometchat-flutter-v6-*` skills carried the documented numbers and have been corrected in cometchat-team/cometchat-skills#184. Closes DOCS-BACKLOG D7. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
anshuman-cometchat
force-pushed
the
docs/flutter-uikit-platform-floors
branch
from
September 8, 2026 11:48
b055d06 to
0af624c
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
ui-kit/flutter/getting-startedsaysminSdk = 24andplatform :ios, '13.0';call-featuressays
minSdkVersion 24andplatform :ios, '12.0'. No Flutter UI Kit app can satisfy any ofthose — and the failure is a build error, not a warning.
Why
cometchat_chat_uikit6.1.1 depends oncometchat_calls_sdkunconditionally — maindependencies:block, not behind an opt-in — and that package pinsminSdkVersion 26andplatform :ios, '15.1'(5.0.7; iOS was 13.0 through 5.0.6).Gradle and CocoaPods both take the maximum across the dependency graph, so a lower app-level
value is a manifest-merger error on Android and a failed
pod installon iOS.Proof rather than inference. Resolving a pubspec whose only dependency is
cometchat_chat_uikit: ^6.1.0:Why this was easy to get wrong
The kit's own AAR really does allow
minSdkVersion 21, and its own podspec really does say9.0. Reading the kit in isolation gives a lower answer; only the resolved graph is right.The documented 24 looks like it came from exactly that reasoning — close, and still unbuildable.
The change
getting-startedminSdk = 24·platform :ios, '13.0'minSdk = 26·platform :ios, '15.1'call-featuresminSdkVersion 24·platform :ios, '12.0'minSdkVersion 26·platform :ios, '15.1'Each with a short note saying why — that the Calls SDK comes along with the kit whether or not
the app uses calling, and that the maximum across the graph is what binds. On
call-featuresthatmatters twice: a reader there is enabling calling and would otherwise read the floor as calling's
price rather than the kit's baseline.
Scope
Current (unversioned = v6) pages only. The archived
ui-kit/flutter/v4/andui-kit/flutter/v5/trees are untouched — they document older versions with their own floors.
Separate PR from #492 because
ui-kit/flutteris a different page tree from/calls/flutter.Companion skills change: 10 sites across 8
cometchat-flutter-v6-*skills carried thedocumented numbers and are corrected in cometchat-team/cometchat-skills#184.
Closes DOCS-BACKLOG D7.