# App Store manifest size / driver-combination limit for large Zigbee apps

**URL:** <https://community.homey.app/t/app-store-manifest-size-driver-combination-limit-for-large-zigbee-apps/161681>\
**Category:** Developers\
**Created:** [November 2, 2026, 4:34pm UTC](https://community.homey.app/t/app-store-manifest-size-driver-combination-limit-for-large-zigbee-apps/161681 "2026-11-02T16:34:52Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![dlnraja](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dlnraja/32/129224_2.png) [@dlnraja](https://community.homey.app/u/dlnraja)\
**Post date:** [November 2, 2026, 4:34pm UTC](https://community.homey.app/t/app-store-manifest-size-driver-combination-limit-for-large-zigbee-apps/161681/1 "2026-11-02T16:34:52Z")

</div>

Hi everyone,

I maintain the community app Universal Tuya Zigbee (`com.dlnraja.tuya.zigbee`). Recent builds are rejected or fail at upload, apparently because of the manifest size or the number of zigbee `manufacturerName` × `productId` combinations per driver. Athom support redirected me to the developer portal, which is only open to verified developers, so I’m asking here:

1. Is there a documented App Store limit, either on the manifest size in bytes or on the number of `manufacturerName` × `productId` combinations, per driver or per app?
2. Can this limit be raised for a large community app?
3. If not, what approach do you recommend? I’m considering splitting large drivers into continuation drivers that share the same code, while already-paired devices stay on their current driver.

Any experience from other large-app developers is welcome. Thanks!  
Dylan

---

<div class="post-metadata">

**Author:** ![Doekse](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/doekse/32/109415_2.png) [@Doekse](https://community.homey.app/u/Doekse)\
**Post date:** [November 2, 2026, 5:49pm UTC](https://community.homey.app/t/app-store-manifest-size-driver-combination-limit-for-large-zigbee-apps/161681/2 "2026-11-02T17:49:17Z")

</div>

I would highly recommend asking your AI to follow some best practices and consolidate stuff. I’m seeing no less than 3 Door/Window sensor drivers for example 😉

---

<div class="post-metadata">

**Author:** ![dlnraja](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dlnraja/32/129224_2.png) [@dlnraja](https://community.homey.app/u/dlnraja)\
**Post date:** [November 2, 2026, 7:03pm UTC](https://community.homey.app/t/app-store-manifest-size-driver-combination-limit-for-large-zigbee-apps/161681/3 "2026-11-02T19:03:10Z")

</div>

Thanks Doekse, fair point. Several of those drivers exist because already-paired devices must keep their driver when I split or move fingerprints, but I’m now auditing them to merge true duplicates (door/window first) and shrink the manifest. Could you still share the exact manifest/combination limit so I can target it?

---

<div class="post-metadata">

**Author:** ![dlnraja](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dlnraja/32/129224_2.png) [@dlnraja](https://community.homey.app/u/dlnraja)\
**Post date:** [November 2, 2026, 7:14pm UTC](https://community.homey.app/t/app-store-manifest-size-driver-combination-limit-for-large-zigbee-apps/161681/4 "2026-11-02T19:14:15Z")

</div>

Good point, but part of that is intentional: some drivers hit the per-driver fingerprint limit, so I split them into continuation drivers (same code, capabilities and flows, chained root → \_2 → \_3) instead of dropping devices. Paired devices also can’t be migrated between drivers, so old ids must stay. That said, the audit did find true duplicates (two door/window drivers with no real fingerprints), which I’m deprecating now, plus a CI gate against new duplicates. Knowing the exact manifest/combination limit would let me size the chain correctly.