Question Re: Error occurred while communicating with the server in Technology Q&A

Error occurred while communicating with the server

former_member38225 — Thu, 29 Aug 2019 21:46:16 GMT

Wondering if there is something I might be doing wrong, I am constantly getting errors trying to use the the assistant, most are the same server errors message. And trying again over and over again does nothing. It's hard to develop and test with all these issues. The assistant just does not seem to be reliable for us, is there just something I am doing wrong.

It also happens on my colleagues computer but at a different step. with the invalid metadata message first but then if you try again it just gives you the same old server error. In the meantime I just bypass the assistant.

Thanks in advance for any insight.

Re: Error occurred while communicating with the server

grabz — Mon, 02 Sep 2019 07:01:18 GMT

If you're using the SCP trial account then it might be connected to some temporary maintenance job running on your server. Time resolves it.

Re: Error occurred while communicating with the server

former_member38225 — Tue, 03 Sep 2019 13:57:36 GMT

Thanks Akos, no this is on our global account. I see there is SP04 patch level for the IOS SDK is out today, I will download and try that next but I think the only answer is to bypass the assistant at this point.

Re: Error occurred while communicating with the server

grabz — Tue, 03 Sep 2019 14:37:08 GMT

The Assistant is a reliable software. In case the upgrade doesn't help I think you should try out these troubleshooting best practices to see what is going on:

Based on your error message the problem can be related with the configuration of your application in SCPms (Connectivity feature).

Collecting the Assistant logs

Start the “Console” application
Reproduce the issue in Assistant
Open the preferences in Assistant, select the General tab.
Copy the filter string (subsystem: com.sap.SAPCPSDKforiOSAssistant)
Switch to the Console application, paste the filter string into the search field (top right corner)
Now, you can see the Assistant’s logs. (If you need some help with analysis them, then copy them here.)

Enable Network Trace in SCPms:

Analytics
Network Traces
Choose your app's Registration ID under Recording
Set the Logging Limit to One hour
Start Recording
Reproduce the issue of the Assistant
Go back to SCPms and Download the Network Trace as a .har file (you can check it in Notepad)

Check the SCPms Logs:

Settings
Log Settings
Set the Log components to Debug: Connectivity, Proxy, Foundation
Reproduce the issue of the Assistant
Go back to SCPms and Analytics
Logs
Technical Logs

If you need some help with these then you can create a ticket on MOB-SDK-IOS-AST

Re: Error occurred while communicating with the server

former_member38225 — Tue, 03 Sep 2019 15:21:30 GMT

Thanks Akos,

OK updated to PL05, still doesn't work. Note the sample app template always works this is just an issue with the new app template. Appreciate your help here.

Ok something real quick to make sure I am working on the latest version.

In preferences there is no general tab, there is only one screen, correct?

Re: Error occurred while communicating with the server

former_member38225 — Tue, 03 Sep 2019 15:29:00 GMT

Akos, Ill take a look in Mobile services to see if i can find the OAuthSettings it is looking for but whats frustrating is that it works sometimes and other times it does not even when all settings are the same.

The error messages I see are here

- Required properties missing from OAuthSettings. OAuthSettings: nil (File: NeoApplication.swift, Function: cpmsApplicationSecurityAuthenticationType, Line: 136)

- SAPURLSessionTask's finishBehaviour: initial (File: SAPURLSessionDelegateDispatcher.swift, Function: urlSession(_:task:didCompleteWithError:), Line: 228)

- updateApplication(_:) failed - Error Log: DataServiceError: Error 500 (Internal Server Error)

<error xmlns="http://docs.oasis-open.org/odata/ns/metadata"><code>500</code><message>Could not create Mapping between application and connection, see log for details</message></error> (File: NeoAdministrationService.swift, Function: updateApplication(_:), Line: 401)

Thanks for any insight