WobblePic v1.5.2 is a housekeeping release, and the housekeeping turned out to matter more than it sounds. The app had been storing its settings, logs and caches inside its own installation folder — the one place on both platforms it should never write to. On macOS that quietly invalidated Apple’s signature; on Windows it quietly threw your settings away.
Both are fixed, and two smaller things came along with them.
Settings and caches no longer live inside the installed app
macOS: the signature lasted exactly one launch
Since v1.4.6 the macOS build has been code-signed with an Apple Developer ID and notarized, so it opens with an ordinary double-click. That is still true of the download — but not of the copy on your disk after you had run it once.
WobblePic was writing its settings, logs, ad cache and a 158 MB CoreML compile cache inside its own signed .app bundle. A signed bundle is sealed: change anything in it and the seal breaks. Logs are written on every launch, so the very first run was enough. Running codesign --verify on an installed v1.5.1 reports “a sealed resource is missing or invalid”.
Nothing visibly broke, which is why it went unnoticed for so long — macOS stops re-checking a bundle once the quarantine flag is cleared. But it meant the notarization we set up in v1.4.6 stopped meaning anything immediately after the first launch, and any future check would have failed.
Installing v1.5.2 replaces the bundle and the signature holds.
Windows: settings were being discarded without a word
If you installed WobblePic for all users — the default landing in Program Files — the app had no permission to write there. Two things followed:
- Your settings were dropped. Sliders, recording format and last folder went nowhere. The save failed silently, so there was no error to notice.
- Startup was slower than it needed to be. The optimised AI model could not be cached, so it was rebuilt from scratch on every single launch, adding seconds each time.
Where things live now
| Platform | Location |
|---|---|
| macOS | ~/Library/Application Support/WobblePic |
| Windows | %APPDATA%\WobblePic |
Settings, logs, caches and the compiled model all live there now. Your existing settings are carried over automatically the first time you run v1.5.2 — nothing to move by hand. The macOS location is where your Ad-Free License key has always been kept, so half of this separation was already in place.
If you have ever gone looking for log files to attach to a bug report, that is where they are now: logs inside the folder above.
Folders show the names your file manager uses
The file browser listed Pictures and Documents while the rest of your system showed the localised names. On a Korean system that is 사진 and 문서 in Windows Explorer — but 그림 and 문서 in Finder. The two platforms do not even agree with each other, which is the reason not to hardcode a table: the tree now asks the operating system for the display name, so it matches whatever your own file manager calls the folder.
Renaming still edits the folder’s real name on disk, not the display name — the two are deliberately kept apart.
WobblePic reopens the folder you were last in
Every launch used to drop you in your Pictures folder, wherever you had been working the day before. It now returns to the folder you had open when you last closed the app.
Opening an image directly — from Explorer, Finder, or drag and drop — still takes you to that image instead.
Also fixed
- Settings are saved again on a fresh install. Window position survived, but the sliders, recording format and last folder were being dropped with no error shown.
- Faster startup on Windows all-user installs, now that the optimised model has somewhere it can be cached.
Download
WobblePic v1.5.2 is free for Windows and macOS.
- Windows 10/11 —
WobblePic_Setup_1.5.2.exe - macOS (Apple Silicon) —
WobblePic-1.5.2-arm64.dmg - macOS (Intel) —
WobblePic-1.5.2-x64.dmg
Grab it from the Download page. If you are on macOS, this is the version worth updating to: it is the one that keeps its signature.