Symptom
When there is no network connection and a user tries to unregister the application by invoking the Application instances
unregisterApplication method
@try {
[app unregisterApplication:30];
}
@catch (SUPApplicationTimeoutException * pe) {
NSLog(@"%@: %@", [pe name],[pe message]);
}
no exception is thrown with the above code and at the same time the following code:
SUPApplicationDefaultCallback perfoms method- (void)onRegistrationStatusChanged:(SUPRegistrationStatusType)
registrationStatus:(int32_t)errorCode :(NSString*)errorMessage;
throws errorCode = 14811.
After the above code is executed the registrationStatus api in the SUPApplication class has value 205 (SUPRegistrationStatus_UNREGISTERED) and if a second call to unregister is attempted then the api unregisterApplication() api does nothing.
Later, when the client has a valid connection to SUP and the user attempts to register the application with new user credentials
@try {
// Register the application with the server.
[app registerApplication:30];
}
@catch (NSException *e) {
NSLog(@"%@: %@", [e name],[e reason]);
}
an exception is throw in
"SUPApplicationRuntimeException: error @ registerApplication
14853 Device already register wih username, security config and application id that doesn't match current values."
The SUPApplicationDefaultCallback perfoms method:
(void)onRegistrationStatusChanged:(SUPRegistrationStatusType)
registrationStatus:(int32_t)errorCode :(NSString*)errorMessage;
with errorCode = 14853
We need to kill the connection on the server manually. Then manually unregister the user within SCC.
Read more...
Environment
- SUP 2.0.x through 2.3.x
- SUP 2.0.x through 2.3.x SDK
- Winows 2008.
- Windows Mobile.
- IOS 6.5.
- Android.
Product
Keywords
SUP Server , KBA , MOB-SUP , Sybase Unwired Platform , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.