Hi John,
Are you also running JRebel 6.1.2 I believe this was fixed in one of our recent releases. Could you try updating to 6.2.1 and let me know if you still run into this issue?
Hi John,
Are you also running JRebel 6.1.2 I believe this was fixed in one of our recent releases. Could you try updating to 6.2.1 and let me know if you still run into this issue?