May 27 2026 APP 2.0.0-beta45 has been released !
Fully Multi-Threaded LNC, many improvements for the registration engine, platform upgrade, and further tuning of internal memory consumption and memory release back to OS.
Apr 14 2026: Google Pay, Apple Pay & WeChat Pay added as payment options
Update on the 2.0.0 release & the full manual
We are getting close to the 2.0.0 stable release and the full manual. The manual will soon become available on the website and also in PDF format. Both versions will be identical and once released, will start to follow the APP release cycle and thus will stay up-to-date to the latest APP version.
Once 2.0.0 is released, the price for APP will increase. Owner's license holders will not need to pay an upgrade fee to use 2.0.0, neither do Renter's license holders.
Hi Mabula.
I encountered this bug in APP beta 45 running on macOS 26.5:
when setting "image viewer in separate window" in the config the application freezes with a beach ball. Force closing it and relaunching causes it to freeze immediately at launch so it becomes unusable.
This happened with beta 45. I tried to launch beta 38 (with the config set) but wouldn't launch either (expected as they share the same key).
After some spelunking I found that APP saves its config in `~/Library/Preferences/com.apple.java.util.prefs.plist`
I reset the key detach.imageviewer.mode to false manually and I'm able to restart the application.
The separate frames list works without issues.
Saved the hang report (attached).
From what I can tell the AppKit main thread is pinned 100% inside an infinite accessibility-tree recursion:
NSAccessibilityChildren → NSAccessibilityUnignoredChildren → NSAccessibilityChildren → …, bottoming out in
NSAccessibilityUnignoredChildrenForOnlyChild.
seems that the detached-viewer window builds an accessibility hierarchy with a cycle.
This, in my instance, causes the utility alt-tab to freeze the app as it inspects its accessibility chain.
Given that the frames list works fine maybe there's something that can be done in APP to prevent this?
