SODataOfflineStore does not refresh

[Former Member]

Hi , as instructed I moved the question to the discussion section. I hope you can still help me out on this.

I have an iOS app with offline store up and running, however I have noticed that when I perform a refresh my data is not being updated even with a refresh success.

We have an offline store that pulls the initial data, within the data there is a property that contains the server timestamp. At the server end every time we access this property it will return the server's current timestamp.

However when I perform a refresh on the offline store I was expecting this timestamp property to be updated, but it hasn't. The only time when it gives me a new timestamp is if I delete the offline store and open it again.

1. Do you know why this maybe happening?

2. Is there anyway to see what has been brought down in a refresh?

Tested this with a rest client, I am able to receive the new data every time I make a request.

[kenichi_unnai]

Okie, with the scenario described there is no reason that the timestamp data would not be refreshed as expected.

Maybe you can share the server log after bumping the Offline and Proxy component log levels to DEBUG?

[Former Member]

Hi Kenichi,

Thank you for getting back to me.

I noticed that when I terminate the app the session cookies are removed from the iOS shared cookie storage. When this happens my refresh fails due to invalid authentication.

I can't figure out a way to renew a session. I receive a session token and everything works fine when I first onboard onto SMP. When the app terminates these cookies are removed (not by me), at this point I am unable to connect properly due to invalid authentication.

Do you know how I can get a new session?

I can only find register/onboard in the SDK and there doesn't seem to be a "login" functionality post initial on boarding.

[kenichi_unnai]

Is it a native iOS app, not the kapsel one?

If it is the case, perhaps you can check if you are correctly configuring a HttpConversationManager with authentication providers and passing them to the conversationManager store option.