Yes, however gears have separate limits, so even if it compiles, it doesn't mean runtime is fine. Just to be sure it's really rockpool-specific(maybe for the certain platform) problem.

Speaking about the platform. Can you estimate from the top of your head protocol-level changes btw pebbled(2.x) and rockworkd(3.x) implementation? I'm just thinking whether ios/android could be falling back to older proto when speaking to aplite for certain transfer types. Which may lead to nacks for pure 3.x comm.