As of April 12th, you must go to Progress SupportLink to create new support cases or to access existing cases. Please, bookmark the SupportLink URL and use the new portal to contact the support team.
I encountered the same problem. Using [KCSUser activeUser] solved it.
On the other hand, this means [KCSUser hasSavedCredentials] leads to errors after deleting and reinstalling the app.
Arun Venkatesan
I use the following logic to check whether a user is logged in already or not:
if ([KCSUser hasSavedCredentials] == NO) {
// show login screen
} else {
// proceed into the app
}
While the user is logged in, if I delete the app and reinstall the app, the hasSavedCredentials method returns a YES, so the logic proceeds to let the user into the app, but all the server calls fail with a 'No Authorization Found' error:
The documentation says the credentials are saved in the Keychain and persist even after an app install and that we can use the hasSavedCredentials to check if the user is available and the user will be loaded on the first call to Kinvey (http://devcenter.kinvey.com/ios/guides/users#login).
Please let me know if there is anything else we need to do to get this functionality to work the way it did.