SUP error while registering: Failure in setConfigProperty

[_IvanFemia_]

Hi all,

do you have any clue on this error "SUPConnectionPropertyException: fail to set application connection properties, -2146435069,RuntimeException: Failure in setConfigProperty"?

We got this error while a custom app (MBO based) is trying to register to SUP (2.1.2 or 2.1.3) either on IOS simulators or phisical devices. (it seems not related to iOS and iPhone version).

On simulator we solved removing the /Library/Application Support/iPhone Simulator/ files and reset it to "factory settings", but we cannot proceed with a factory reset on phisical devices.

What is the error referring to?

Have you any suggestion how to solve on phisical devices?

Thanks and Regards,

Ivan

[D_Olderdissen · Accepted solution]

It will be important to understand what SDK version you are using. There is a major change in the mobile SDK from 2.1.2 to 2.1.3 on iOS as MBS got "deprechiated" and since 2.1.3 you are working with the unified sync protocol.

That means the registration process (all the stuff you do in the early startup phases of your app) is completely different in 2.1.3 when compared to 2.1.2.

Questions:

• The way I read your post, the client connection does not even reach the SUP server?
• Did you try to completely uninstall the app on the iOS? Removed the registrations for this device/app in SCC?
• Depending on the SDK version you are using, did you revisit the communication initiation phase in one of the tutorials? Did you pick the right tutorial? (Would be hard if you are on SDK 2.1.2 and by accident read into the 2.1.2 tut)

[_IvanFemia_ · Accepted solution]

Hi Dirk,

we got this error either on 2.1.2 or 2.1.3.

Btw currently we moved on SUP 2.1.3 and we adjusted the application using RBS sync and we also modified the connection and registration code.

The application works fine on some devices and simulators but in others we got this error. With simulators as I said we solved with a complete "factory reset", but we don't want to reset/wipe real devices.

Questions:
The way I read your post, the client connection does not even reach the SUP server?
Correct
Did you try to completely uninstall the app on the iOS? Removed the registrations for this device/app in SCC?
Yes, we did it both several time without any success.
Depending on the SDK version you are using, did you revisit the communication initiation phase in one of the tutorials? Did you pick the right tutorial? (Would be hard if you are on SDK 2.1.2 and by accident read into the 2.1.2 tut)
Yes, the initialization works fine and it follows demo apps. As I said the application works fine in most of the devices, but we have this issue on some of them.

Thanks again,

Ivan

[D_Olderdissen · Accepted solution]

How do you register the devices? Manually? Auto-Registration?

Did you check the logs if the device really NEVER connects to SUP?

What values are you setting in the connection properties? Where do they come from? Any localized characters? Anything that is different from the not to the working devices in that respect?

[_IvanFemia_ · Accepted solution]

How do you register the devices? Manually? Auto-Registration?

How do you register the devices? Manually? Auto-Registration?

We are using auto-registration procedure.

Did you check the logs if the device really NEVER connects to SUP?

it reaches the SUP server, but once it is trying to register/connect we got this error.

What values are you setting in the connection properties? Where do they come from? Any localized characters? 

SUPConnectionProperties* props = app.connectionProperties;

[props setServerName:@"relay_server_url"];

[props setPortNumber:80];

[props setUrlSuffix:@"/cli/iarelayserver"];

[props setFarmId:@"MBS_farm_id"];

SUPConnectionProfile *sp = [**********DB getSynchronizationProfile];

[sp setServerName:@"relay_server_url"];

[sp setNetworkProtocol:@"http"];

[sp setPortNumber:80];

[sp setNetworkStreamParams:[NSString stringWithFormat:@"trusted_certificates=;compression=none;url_suffix=/cli/iarelayserver/%@",@"RBS_farm_id"]];

[sp setUser:@"user_name"];   //Login User name

[sp setPassword:@"user_pass"]; //Login password

Dirk Olderdissen wrote:
Anything that is different from the not to the working devices in that respect?

We suspect that not working devices were using old SUP 2.1.2 application that used MBS only connection and once they removed 2.1.2 to switch on 2.1.3 version got this error.

Could it possible that SUP libraries store some settings on the device?

Thanks

Ivan

[_IvanFemia_ · Accepted solution]

Finally solved.

On exception I execute this code

[MessagingClientLib resetMessagingState];