Is it possible to use the Matter.xcframework without using the MatterSupport extension for onboarding a device to our ecosystem?

Is it possible to use the Matter.xcframework without the MatterSupport extension for onboarding a Matter device to our own ecosystem(own OTBR and matter controller) for an official App Store release?

Currently, we can achieve this in developer mode by adding the Bluetooth Central Matter Client Developer mode profile (as outlined here https://github.com/project-chip/connectedhomeip/blob/master/docs/guides/darwin.md). For an official release, what entitlements or capabilities do we need to request approval from Apple to replace the Bluetooth Central Matter Client Developer mode profile?

Thank you for your assistance.

Answered by DTS Engineer in 858883022

Is it possible to use the Matter.xcframework without the MatterSupport extension for onboarding a Matter device to our own ecosystem(own OTBR and matter controller) for an official App Store release?

Why do you want to do this? Why is using the MatterSupport framework an issue? The point of matter is facilitate sharing accessories across ecosystems, which is exactly why the MatterSupport ecosystem exists.

__
Kevin Elliott
DTS Engineer, CoreOS/Hardware

I am in a case described by @MarcoKhoo. I would appreciate an answer as to whether we can use Matter.xcframework directly in our production application. What entitlements do we need (if any)?

Thank you for your assistance.

Hello there,

Have you found a solution?

There is no way to use Matter.framework alone 😞

https://developer.apple.com/forums/thread/795746

Is it possible to use the Matter.xcframework without the MatterSupport extension for onboarding a Matter device to our own ecosystem(own OTBR and matter controller) for an official App Store release?

Why do you want to do this? Why is using the MatterSupport framework an issue? The point of matter is facilitate sharing accessories across ecosystems, which is exactly why the MatterSupport ecosystem exists.

__
Kevin Elliott
DTS Engineer, CoreOS/Hardware

The reason is that we have been receiving repeated complaints from end users regarding failures when commissioning Matter devices using iOS. Interestingly, Android devices that use the Matter SDK directly do not exhibit these issues under the same conditions. During our testing, we have observed several recurring problems across iOS versions 18 through 26.2. Below are the most common issues: (Especially for Matter over Thread device)

Commissioning Flow Stops Before Second Fabric Creation

The first fabric is created successfully, as confirmed by the end device logs and receipt of the “Open Commissioning Window” command from the first fabric. However, the process halts before creating the second fabric. This appears to be outside our control, as these steps occur within the MatterSupport Extension.

Performance Degradation After Multiple Commissioning Attempts

When commissioning is tested repeatedly using the same Apple account (e.g., over 200 times), the process stalls at the beginning for an extended period (>1 minute). During this time, iOS BLE does not attempt to connect to the end device. Removing the Matter accessory in iOS settings sometimes helps, but not consistently. Recovery often requires waiting several days or weeks.

Please let me know if others in the Matter ecosystem are experiencing similar issues. We would greatly appreciate any efforts to address these problems within the MatterSupport Extension.

Is it possible to use the Matter.xcframework without using the MatterSupport extension for onboarding a device to our ecosystem?
 
 
Q