The issue
After the Kamma screen replacement app is deployed or updated in Reapit, some users may not see the new version immediately. The Reapit desktop application caches the screen replacement and does not always pick up changes within an active session.
How to resolve it
Close and reopen Reapit completely. This clears the cache and forces Reapit to load the latest version of the Kamma screen replacement.
Note that simply navigating away and back within the same Reapit session is not sufficient — a full close and reopen is required.
When this applies
This is most likely to occur:
Immediately after a new version of the Kamma screen replacement is released.