I managed to “work around” the issue but you DO NOT want to do this in production (my island was submitted as public but unlisted so I was not worried about players loosing data, you have been warned)
I fixed the ambiguous identiefier issue, in fact I totally removed the offending file from the project and was still getting the same error (even pointing to the non-exisitent file). I reverted my Active Release to V1 -
After forcing it to use the V1 release (potentially loosing data) I was able to take the same private release (that had just failed earlier) and now it passed.
This make me think this issue might be part of a bigger problem as this happened after I followed the instructions here to “fix” an inability to publish via Scene Graph - [MAJOR] Asset Reflection - General / Issues and Bug Reporting - Epic Developer Community Forums
After that “fix” I was able to push and publish V2, however all future updates to it had this Ambiguous identifier bug, even if I removed the file the Nomad service wasn’t refreshing. Only reverting to a previous published code then allowed me to push a fixed private code. It’s like the one in between became broken.
Now this should NOT be closed as it’s a HUGE issue that on a live game (as this one will be within days) players could loose save data and that’s really not an option on most maps.
Either way, hopefully this provides more info for epic to track down. I’m happy to provide anything to assist.