sqlcipher-update

Update SQLCipher versions across SalesforceMobileSDK-iOS projects and validate compatibility.

555|424|Updated Sep 6, 2011
One-click install
npx skills add https://github.com/forcedotcom/SalesforceMobileSDK-iOS --skill sqlcipher-update
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sqlcipher-update
Source: https://github.com/forcedotcom/SalesforceMobileSDK-iOS/tree/main/.claude/skills/update-sqlcipher
Command: npx skills add https://github.com/forcedotcom/SalesforceMobileSDK-iOS --skill sqlcipher-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Update SQLCipher across the Salesforce Mobile SDK for iOS automatically, reducing manual errors and ensuring consistency.

Core Features & Use Cases

  • Update SQLCipher version in podspecs, SmartStore references, and related project files across the repository.
  • Synchronize the cipher provider version, OpenSSL/LibTomCrypt details, and API compatibility notes across tests and configurations.
  • Validate changes by updating version tests where present, building the SmartStore components, and preparing a PR-ready summary.
  • Use Case: When patching a security vulnerability that requires upgrading SQLCipher in all dependent modules, run this Skill to apply changes consistently.

Quick Start

Provide NEW_VERSION (and optional OLD_VERSION and NEW_PROVIDER_VERSION) to update SQLCipher across the project and run a basic compatibility check.

Frequently Asked Questions about sqlcipher-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update SQLCipher across SalesforceMobileSDK-iOS projects?▼

To update SQLCipher across SalesforceMobileSDK-iOS projects, provide the NEW_VERSION to automatically update dependency references, podspecs, tests, and related configurations, then prepare a PR-ready summary.

What does updating SQLCipher in SmartStore involve for dependency management?▼

Updating SQLCipher in SmartStore involves synchronizing the cipher provider version, OpenSSL or LibTomCrypt details, and API compatibility notes across tests and configurations to ensure consistency.

Can I validate SQLCipher API changes and major version compatibility automatically?▼

Yes, you can validate SQLCipher API changes automatically by updating version tests, building SmartStore components, and checking provider version compatibility and cipher settings.

What is the best way to patch a security vulnerability requiring a SQLCipher upgrade in iOS?▼

The best way to patch a security vulnerability requiring a SQLCipher upgrade in iOS is to run an automated update across the repository to apply changes consistently across all dependent SmartStore modules.

Do I need to provide old version numbers when upgrading SQLCipher podspecs?▼

You need to provide the NEW_VERSION to upgrade SQLCipher podspecs, while OLD_VERSION and NEW_PROVIDER_VERSION are optional inputs for validating provider version and compatibility.

Why does updating SQLCipher manually cause errors across SmartStore modules?▼

Updating SQLCipher manually causes errors across SmartStore modules due to inconsistent dependency references and missed configurations, which automation solves by ensuring consistency across the repository.