Bump ios package

[ktnishide]

bumping iterable ios sdk due to issue:
Iterable/iterable-swift-sdk#844

Summary by CodeRabbit

• Chores
  • Updated Iterable-iOS-SDK dependency to version 6.6.1
  • Added namespace configuration to Android build settings

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[coderabbitai]

📝 Walkthrough

Walkthrough

Configuration updates to the iOS and Android build files: upgrading the Iterable-iOS-SDK CocoaPods dependency from version 6.4.7 to 6.6.1 and adding a namespace property to the Android Gradle configuration.

Changes

Cohort / File(s)	Summary
iOS Dependency Update ios/iterable_flutter.podspec	Upgraded Iterable-iOS-SDK dependency version from 6.4.7 to 6.6.1.
Android Namespace Configuration android/build.gradle	Added namespace property with value com.lahaus.iterable_flutter in the android block.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A hop and a bump, dependencies rise,
Version six-six brings improvements so wise,
Android's namespace now proudly displayed,
Configuration adjusted, no bugs to evade! 🎉

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Bump ios package' is vague and generic, failing to specify which package is being bumped or what version change occurred.	Consider a more specific title like 'Update Iterable-iOS-SDK to 6.6.1' or 'Bump Iterable iOS SDK version for issue #844' to clearly convey the main change.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 3

🧹 Nitpick comments (3)

.dart_tool/extension_discovery/README.md (3)

5-5: Grammar: subject–verb agreement.

Use “contain” (plural) with “lists of packages”.

-packages that contains extensions for other packages.
+packages that contain extensions for other packages.

---

22-23: Incomplete sentence; clarify intent.

This line is a fragment. Suggest replacing with a complete directive.

-If you want to access information from this folder.
+To access any information represented by this cache, use the API provided by the `extension_discovery` package.

---

30-31: Minor grammar/punctuation fix for readability.

-Hence, it should never be necessary to clear this cache manually, if you find a
-need to do please file a bug.
+Hence, it should never be necessary to clear this cache manually. If you find a
+need to do so, please file a bug.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c068aef and a923ac8.

📒 Files selected for processing (3)

• .dart_tool/extension_discovery/README.md (1 hunks)
• .dart_tool/extension_discovery/vs_code.json (1 hunks)
• android/build.gradle (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• .dart_tool/extension_discovery/vs_code.json

🧰 Additional context used

🪛 LanguageTool

.dart_tool/extension_discovery/README.md

[style] ~23-~23: Consider using a less common alternative to make your writing sound more unique and professional.
Context: ...o access information from this folder. Feel free to delete this folder --------------------...

(FEEL_FREE_TO_STYLE_ME)

🪛 markdownlint-cli2 (0.17.2)

.dart_tool/extension_discovery/README.md

10-10: Unordered list indentation
Expected: 0; Actual: 1

(MD007, ul-indent)

---

11-11: Unordered list indentation
Expected: 0; Actual: 1

(MD007, ul-indent)

[coderabbitai]

💡 Verification agent

🧩 Analysis chain

Gradle plugin 4.1.0 does not support namespace; this will break the Android build.

The namespace DSL was introduced in newer Android Gradle Plugin versions (7.x). With AGP 4.1.0 (as declared on Line 12), this property is unknown and will cause a sync/build failure. Given the PR scope (iOS SDK bump), suggest reverting this addition unless you’re also upgrading AGP/Gradle in this PR.

Apply this diff to keep the build working with AGP 4.1.0:

-    namespace "com.lahaus.iterable_flutter"

If you intend to keep namespace, plan an AGP upgrade (and Gradle wrapper update) in a separate PR and verify the manifest package is consistent with the chosen namespace.

---

🏁 Script executed:

#!/bin/bash
# Verify Android Gradle Plugin version
grep -R "com.android.tools.build:gradle" -n .

Length of output: 218

---

Remove unsupported namespace for AGP 4.1.0 or plan an upgrade

The Android Gradle Plugin declared in android/build.gradle (classpath com.android.tools.build:gradle:4.1.0) does not recognize the namespace DSL (introduced in AGP 7.0+). Leaving this line in place will cause a sync/build failure.

• File: android/build.gradle
Line: 28
Current:
groovy namespace "com.lahaus.iterable_flutter"
• Options:

1. Remove the namespace line to restore compatibility with AGP 4.1.0.

   -    namespace "com.lahaus.iterable_flutter"

2. If you need to keep namespace, upgrade the Android Gradle Plugin and Gradle wrapper in a follow-up PR to version 7.x or later, and verify your manifest’s package matches the new namespace.

🤖 Prompt for AI Agents

In android/build.gradle around line 28, the file contains the unsupported AGP 7+
DSL line `namespace "com.lahaus.iterable_flutter"` while the project uses
Android Gradle Plugin 4.1.0; remove that namespace line to restore compatibility
with AGP 4.1.0, or alternatively perform a follow-up upgrade of the Android
Gradle Plugin and Gradle wrapper to AGP 7.x+ and ensure the AndroidManifest
package value matches the new namespace if you choose to keep it.