From 033c7c27adb7dd14aad59901d72de2a8d9f3a7f2 Mon Sep 17 00:00:00 2001
From: h2zero <ryan@nable-embedded.io>
Date: Sun, 13 Apr 2025 16:06:34 -0600
Subject: [PATCH] Fix extended server example - data too long error

---
 examples/Bluetooth_5/NimBLE_extended_server/main/main.cpp | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/examples/Bluetooth_5/NimBLE_extended_server/main/main.cpp b/examples/Bluetooth_5/NimBLE_extended_server/main/main.cpp
index 13428ec..607cd02 100644
--- a/examples/Bluetooth_5/NimBLE_extended_server/main/main.cpp
+++ b/examples/Bluetooth_5/NimBLE_extended_server/main/main.cpp
@@ -65,8 +65,7 @@ class AdvertisingCallbacks : public NimBLEExtAdvertisingCallbacks {
     }
 } advertisingCallbacks;
 
-extern "C"
-void app_main(void) {
+extern "C" void app_main(void) {
     /** Initialize NimBLE and set the device name */
     NimBLEDevice::init("Extended advertiser");
 
@@ -105,7 +104,6 @@ void app_main(void) {
                                       "This example message is 226 bytes long "
                                       "and is using CODED_PHY for long range."));
 
-    extAdv.setCompleteServices16({NimBLEUUID(SERVICE_UUID)});
     extAdv.setName("Extended advertiser");
 
     /** When extended advertising is enabled `NimBLEDevice::getAdvertising` returns a pointer to `NimBLEExtAdvertising */