In the default implementation, this function checks the settings bundle to see if
it contains a nonempty value. Since you know you are providing one, you can make
hasCredentials always return YES, or you can call
getDefaultConnectionActivationCode and test that the returned
value is nonempty. Be sure you call
getDefaultConnectionActivationCode only if you override its
implementation so that it does not call getConfigProperty.Your
implementation would look like this:
Note: Providing default connection settings only populates the initial values each
time the application starts. The user can still change the values in the Settings
screen, but those changes are disregarded when the application starts. This
approach still does not prevent a server change from overwriting the properties on
the client, but those changes will get reverted once the application restarts.