Nescroll docs
 v1.0.0
Get help
● Ship · New versions

Updating
to a new version of the item.

When a new version of Nescroll is released, download it from your Downloads page on the marketplace. Because you changed only a few files to rebrand, merging is short if you keep track of them.

01Keep your changes easy to find

  • Put your copy of the project in Git from day one, and commit the untouched package first. Then every change you make is visible with git diff.
  • Your rebrand lives in project.yml, AppConfig.swift, LockShared.swift and the asset catalog. Keep other edits small and commented.

02Update steps

  1. Read the Changelog of the new version.
  2. Create a branch in your repository, for example update-1.1.0.
  3. Copy the new app/ folder over yours, except project.yml, AppConfig.swift, LockShared.swift and Assets.xcassets.
  4. Compare those four with the new package (diff or a merge tool) and copy over new keys or values, keeping your IDs, names and URLs.
  5. Check translations: if you added languages to Localizable.xcstrings, merge the new English strings into your file and translate them.
  6. Regenerate and test: xcodegen generate, run the tests, test the Lock tab on a device.
  7. Raise your version (MARKETING_VERSION, CURRENT_PROJECT_VERSION) and release.

03Only filter fixes?

If a new version only changes selectors, labels or redirects in Platform.swift, you can copy them into your remote rules.json instead and skip an App Store release (Updating filters remotely).