macOS apps built with Objo can share an executable UUID and lose local network access

macOS desktop apps built or published by Objo Studio can share the same main executable UUID even when they have different names and bundle identifiers. macOS Local Network privacy can then confuse one app with another: a Finder-launched app may fail to connect to a LAN server with “No route to host” and may not appear in System Settings → Privacy & Security → Local Network. Each distinct generated app should have its own main executable UUID so macOS can track its permissions independently.