I have two applications (MinimServer and MinimWatch) that run on macOS. Both use the local network.
On Sequoia, starting MinimWatch for the very first time after installing Sequoia shows a prompt for permission to access the local network. If the user agrees, an enabled entry for MinimWatch appears in the Privacy & Security > Local Network section as expected.
If MinimServer is then started for the very first time, there is no prompt and the existing Local Network entry for MinimWatch now controls local network access for both MinimWatch and MinimServer.
If ths above order is reversed (start MinimServer first after installing Sequoia and then start MinimWatch), Local Network shows a single entry for MinimServer which controls network access for both MinimServer and MinimWatch.
It appears there is a false positive match when the second application is started. Sequoia finds the Local Network entry for the first application and incorrectly idenfies this as matching the second application.
Both applications are written in Java and have a similar internal structure. The app packages contain some identical files but the following files are different:
The bundle executable in the MacOS folder
Other executables in the MacOS folder launched by the bundle executable
The Info.plist keys CFBundleName, CFBundleIdentifier, CFBundleExecutable, CFBundleIconFile and JVMMainJarName
What might be the similarity between these app packages that is causing Sequoia to incorrectly identify one of these applications as being the other application?