be958fffea
which run *after* any migrations which mutate the schema. If a user hasn't been keeping up to date, it's possible they'll crash when running several migrations in sequence. Any migration which leverages SDSModel serialization must occur *after* changes to the database schema complete. Otherwise, for example, consider we have these two pending migrations: - Migration 1: resaves all instances of Foo (Foo is some SDSModel) - Migration 2: adds a column "new_column" to the "model_Foo" table Migration 1 will fail, because the generated serialization logic for Foo expects "new_column" to already exist before Migration 2 has even run. The solution is to always split logic that leverages SDSModel serialization into a separate migration, and ensure it runs *after* any schema migrations. That is, new schema migrations must be inserted *before* any of these Data Migrations. |
||
|---|---|---|
| .. | ||
| protobuf | ||
| Resources | ||
| src | ||
| tests | ||
| Utilities | ||
| .clang-format | ||
| .gitignore | ||
| .travis.yml | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| README.md | ||
SignalServiceKit
SignalServiceKit is an Objective-C library for communicating with the Signal messaging service for iOS & OS X
To use SignalServiceKit via CocoaPods add the following to your Podfile
pod 'SignalServiceKit', git: 'https://github.com/signalapp/Signal-iOS.git'