Bummer. Haven’t reproduced yet. Wondering if this is related to bundler version. Let’s also note the bundler version if y’all run into it.
This feels similar to what was happening in:
In any case, think might add a deploy check to fail hard also before it gets to lambda. Im assuming it’s getting to lambda before the error surfaces. Issue is it’s going to be hard to add this sanity check unless can reproduce it. Please report bundler version when y’all get a chance. Thanks!