Register Client ID

[JeffreyThompson2]

After upgrading to Developer Edition 1.16, I am getting a warning that the Client ID is missing in one of my projects every time I open it.

I have entered the App ID from my Experience Builder Credentials.  I have also tried the App Secret. Neither has stopped the warning from appearing.

Entering something in this box creates a new entry into the connections array in the server/public/apps/1/resources/config/config.json. This array was ten identical records long before I deleted it and tried again. Copying the project also did not clear the issue.

Using the refresh button on the Builder page crashes Experience Builder. I can refresh on the Preview page and all the other functions appear to be normal whether I enter a value into this box or hit cancel.

This project has been through hundreds of revisions at this point. It is highly complex with many utilities and custom widgets. It started on 1.11, then 1.12, then 1.14 and now is on 1.16. While on 1.12, it was forcefully migrated between Portals by editing the JSON. Another much simpler project created in 1.14, upgraded without throwing this error message. 

I am on Enterprise 10.9.1 with SSO Authentication.

Is there way to get the Client ID to properly register? Can this error be ignored?

[Wei_Ying]

@JeffreyThompson2 this project should have some resources (data) from another portal other then the connected portal right? Does this issue happen before upgrading to 1.16?

[JeffreyThompson2]

This warning did not appear before 1.16.

All of the resources at load should be from the connected Enterprise Portal. There are some references in the code base to the test Enterprise Portal that it was migrated off of at 1.12. They are not functional in the project. It is also possible for the end user to load some resources from the Online Portal at runtime.

[TimWestern]

I have seen this in either 1.14 or 1.15. (Memory is fuzzy if I have testing in 1.15 yet)

I seem to recall this dialog appearing (and that the issue described) being caused  by how a layer or tool was published.  Something about a reference that is published by client, then brought into a map/feature service, and a reference again, then included and published through another server URL, might mean there references to references that are somewhere else.    I seem to recall I had to republish and not use 'reference' data but rather copy it, got rid of that.  (I don't recall if it was 2 reference hops or 3 I think it was the original was a reference, and so what I was doing would have been the second reference, which would have created a weird client server referring to us who were building a feature's hosting, then back to theirs kind of thing)

I'm not sure if its the same thing you are experiencing @JeffreyThompson2 but something you can look at on the layers of your map/feature service layer.  For me it was only one layer or tool wrongly setup that caused it, but took me days to find out that it was the one it was.

[JeffreyThompson2]

I have now deployed this project to a server and it appears to be functional even with this issue unresolved.