Skip to main content

Troubleshooting

Initial iCloud Synchronization​

The initial iCloud synchronization may take some time, especially if you have a lot of snippets. Please wait a couple of minutes and check if the snippets are synchronized on all devices.

Changes are received in batches, so even if the app displays that the database has been synchronized at XYZ, it doesn't mean that all changes have been already received.

iCloud Synchronization​

If you experience issues with iCloud synchronization, you can try the following steps:

  1. Make sure that iCloud Synchronization is enabled on macOS in App Settings -> General.
  2. Make sure that you are logged in with the same Apple ID on all devices.
  3. Make sure that you have an active internet connection.
  4. Check your iCloud status on macOS in System Preferences -> Apple ID -> iCloud.
    • Make sure that you've got enough free space.
    • Check if Sync this Mac is enabled.
    • Go to Drive -> Apps syncing to iCloud Drive and check if Snippety is enabled.
    • Check the same on your iOS/iPadOS devices.
  5. Restart Snippety on all devices.
  6. Disable and re-enable iCloud Synchronization in App Settings -> General (macOS).
  7. Restart all your devices.

If you recently made a lot of changes in your database, Apple may throttle your account and the synchronization may be temporarily disabled. In this case, you need to wait. It should be re-enabled in about 1 hour.

If you still experience issues, try reinstalling the app on all devices. You may also need to delete the local database on macOS before reinstalling the app. To do this, close the app by using CMD + Q, go to

~/Library/Containers/pl.wojciechkulik.Snippety/Data/Documents

and delete the storage folder. But be careful, this will delete all your snippets and settings, so make sure that you have a backup.

Snippet Expander​

Built-In Troubleshooting​

First of all, open App Settings -> Snippet Expander -> Troubleshooting and check if there are any issues reported and try addressing them.

Expansion Issues​

  1. Check if the problem is reproducible in other applications.
  2. Check if the problem occurs only when using Snippet Expander or also when using basic expansion (see From The App).
  3. Make sure that the Snippet Expander is enabled in App Settings -> Snippet Expander.
  4. Make sure that you have the necessary permissions for the Snippet Expander. See Configuration to learn how to grant permissions.
  5. Sometimes updating macOS may break permissions. In this case, you need to go to System Preferences -> Privacy & Security -> Accessibility, delete Snippety from the list, and add it again.
  6. Snippet Expander doesn't work if Snippety window is pinned, so make sure it's not visible while your are typing.
  7. Restart Snippety.
  8. Make sure that you use the correct trigger for the Snippet Expander. You can check it in App Settings -> Snippet Expander -> Triggers.
  9. Make sure that your snippet keyword does not contain a trigger. For example, if you use Snippet Expander prefix ; and you have a snippet with keyword ;email, you would need to type ;;email to expand the snippet, which is usually not what you want. Adding prefix to the keyword usually makes sense only if you want to use multiple prefixes and disable the global one.
  10. Try disabling other apps working in the background that may interfere with Snippety. Especially, apps that use global shortcuts, apps that track your keyboard, clipboard managers, etc.

The Form Does Not Pop Up​

Check if Inline Placeholders are enabled in App Settings -> Snippet Expander. If they are and your snippet contains placeholders with text input, the form won't pop up without providing values. See Inline Placeholders to learn how to use this feature.

Also, make sure that App Settings -> Snippet Expander -> Triggers -> Do not expand snippets with placeholders to fill in is NOT enabled.

Interrupted Expansion​

Keep in mind that any clicks, shortcuts, or other interactions while typing the keyword, will cancel the expansion. However, Snippety allows using the Backspace key to correct the keyword if you made a mistake.

Not Fully Deleted Keyword​

If your keyword is not fully deleted before the snippet is expanded, it may happen because the target application or the system is too slow and is unable to process many key events in a short time. In this case, you can try to increase the delay between key events in App Settings -> Snippet Expander -> Troubleshooting.

Script Placeholder​

If your snippet is unable to run a script, please make sure that you understand the limitations of the script placeholders. See Command Line Script.

If you are using Snippety Helper, make sure that it is running in the background and read Snippety Helper to learn more about it.

Cursor Position​

If you experience issues with the cursor position after expanding a snippet, please see Cursor Position to learn more about how it works and what are the limitations.

Keyboard Shortcuts​

Usually, issues with keyboard shortcuts are caused by conflicts with other apps or because of using a non-standard keyboard layout.

If you are using Dvorak, make sure that you enabled the correct mode in App Settings -> General. By default, Snippety assumes that you are using the classic Dvorak layout. If you are using Dvorak - QWERTY ⌘, you need to enable this mode in App Settings -> General.

If you are using MacBook, make sure that the issue occurs also when using the built-in keyboard.

Shared File Synchronization​

In general, this method is not recommended anymore, because it isn't able to properly handle conflicts and may cause data loss. Using this method, each client saves the whole database to a shared storage, so if two clients upload the database at the same time, one of them will overwrite the other one.

Please also note that any change in database will trigger synchronization, including using a snippet (because it updates the last used date).

On top of that, if you are using a cloud service like Dropbox, Google Drive, etc., they have their own conflict resolution mechanisms, which may cause even more problems.

Snippety offers iCloud Synchronization & Collaboration, which are much more reliable, secure, and can handle conflicts properly.

Search Performance​

  1. Try disabling fuzzy search:
    • Click on the magnifying glass icon in the search bar.
    • Uncheck Fuzzy Name Search.
  2. This issue could be also caused by performance problems with the list. See the next section.

Snippets List Performance​

  1. Try enabling raw placeholders: click on the </> icon on the Snippet Preview bar.
  2. Check if the issue is not caused by large images in snippets. Try reducing the size of the images or removing them if needed.