MTU request Error 133 with Extended Advertising

[brett_anderson]

So, this could just be an odd coincidence, but I'm stuck.

I had a project working using standard advertising. You connect, pair, and then the client (nRF Connect on Android) could request a new MTU (200 or above in this case). Worked fine.

I changed the advertising to be extended. That seems to work just fine, I see it in nRFConnect and can connect and pair. But if I issue a request MTU, it just spins for a bit and then I get Error 133 on the app. I have logging on the GATTS event, and I see the MTU change happen in the RTT viewer.

Ideas?

I am continuing to advertise after connection, but if there is a connection then the advertisement is non-connectable. I'm using some manufacturer data so I want that to still go out if someone is connected. Again, this all worked just fine. The only switch was to extended, and that somehow broke responding to the MTU request?

SDK 17.1, nRF52833. SD340 v7.0.1

[brett_anderson]

Bah!!!

Chalk this one up to stupid coincidence. The size of my encoded advdata array was not updated correctly with the change to extended. This was being overrun, and somehow breaking the MTU response. So, once I fix the overrun, everything works correctly.