Hi! Community!
Have you expirienced this and how did you solve this?
After duplicating projects on WeWeb and Xano, there are complications arising when reconfiguring the authentication plugin and the main Xano plugin for the duplicated Xano instance. Specifically, there’s an overlap in API groups, resulting in operational challenges. If authentication settings remain unchanged and only the main plugin is configured, authentication proceeds to the original Xano instance from which the duplication was made. While this setup functions with most requests to the duplicates, it leads to significant time investment in reconfiguring requests across various components and workflows.
The issue arises due to the inherent conflict in API groups following the duplication process. When attempting to reconfigure the authentication plugin and the primary Xano plugin for the duplicated Xano instance, conflicts emerge within the API group structure. If adjustments are made solely to the main plugin while leaving the authentication settings unaltered, authentication routes traffic to the original Xano instance rather than the intended duplicate. Consequently, while basic functionality remains intact for most requests directed at the duplicates, significant manual intervention is required to realign requests across disparate components and workflows.
