Skip to Content
0

SAP Cloud Platform SDK for iOS Assistant hangs

Apr 03, 2017 at 02:53 PM

176

avatar image

Anyone seeing this as well, my Assistant hangs when creating the Xcode project, more specifically when trying to generate the proxy classes.

It worked once on the first project and subsequently it hangs. Both on new projects and when trying to re-generate the proxy classes for the one project that worked initially. This happens regardless of the backend service I'm trying to reach.

This is what I'm seeing in the console log over and over again:

SAP Cloud Platform SDK for iOS Assistant: getting current attributes...
SAP Cloud Platform SDK for iOS Assistant: filling 16 attributes for type 2147483648
SAP Cloud Platform SDK for iOS Assistant: looking at 16 attributes
SAP Cloud Platform SDK for iOS Assistant: finished: 1a00c9960ffb6a36276a8943551296dfb9a5f40960d6e202f32964e747270a19

Any idea why and what to do?

iOS
10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Robin van het Hof
Apr 03, 2017 at 04:43 PM
1

Hi Daniel,

Which version of the SDK are you using? The one for Xcode 8.2 or 8.3?

Are you using a custom OData service? Have you tried with the Sample OData service as well?

Show 8 Share
10 |10000 characters needed characters left characters exceeded

I use the one for 8.3 and have only tried with custom OData services. Will check with the sample service now...

0

OK. Using the sample works - any chance to see any errors since the console log seems fine, just cycling thru the same messages over and over again.

0

Hmmm, difficult to tell, was hoping the Console logs would reveal a bit more... At least we now pinpointed the issue to the OData service.

Not sure if this would show anything different, but you could try and use the command line tool and generate the proxy classes from there? Go to <SDK_LOCATION>/Tools/ProxyGenerator and run :

./sapcpsdk-proxygenerator -m <PATH_TO_METADATA.XML> -p ./sapcpsdk-resources -d <DESTINATION_FOLDER> -v
1

Strange, once I used the commandline once, the assistant started working again. Not sure if it had anything to do with it though - tried various OData services and they all work fine now.

1

Hi Daniel,

Could you please send us the relevant Assistant logs? (The logs you are seeing are coming from the Keychain, and not relevant here.)

Please use the following filter in Console: "process:assistant message:message"

Then please export it using the Share option and send them to us.

Thanks and Best regards,

David

1

We are having the same issue. Have you found a solution yet?

Kind regards,

Marlies

0

Hi Marlies,

Could you please send us the same logs, what I requested from Daniel?

Thanks,

David

0

Hi David,

I already issued an incident report on this, hopefully there will be a solution soon.

Best regards,

Marlies

0