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:
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?
Can this limit be raised for a large community app?
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
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
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?
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.
