Custom Snap Pack versioning is broken?


I can confirm that I’m seeing some errant behavior along the lines of what you’re describing, where the older version of the code appears to be executed instead of the newer code. I’ll create a defect ticket in our ticket system with a workable example.

For now, it sounds like you can work around this by keeping the version number at 1, correct?


@ptaylor I suppose, though it is certainly not desirable… Thanks for your help!

Ok. Agreed: not desirable. Thanks for your patience. This is a tricky one to even understand the problem. I’m still trying to get a clearer picture of it through my own testing.