Skip to content

Conversation

@rihadavid
Copy link
Contributor

The currentInstallation object was never cached between app launches, because the exclamation mark was missing. When you look at the similar code in ParseUser, the exclamation mark is there, confirming this is a typo.

The currentInstallation object was never cached between app launches, because the exclamation mark was missing. When you look at the similar code in ParseUser, the exclamation mark is there, confirming this is a typo.
@TobiasPott
Copy link
Member

@rihadavid Hi there, I've recently looked into this issue and want to check if it's still an open issue with the current state of the repository.
If you are still using parse and occasionally the latest version of this repository, it would be of great help if you could check your issue with the current state of repository.

I've looked at it very briefly and noticed that I get conversion exceptions from ParseObject to ParseInstallation and cannot even call ParseInstallation.CurrentInstallation from a simple console application.
To avoid this exception I needed to add ParseObject.RegisterSubclass<ParseInstallation>(); to the ParseClient.Initialize(Configuration) method as I could not find it anywhere else in the code.

I'll try to reproduce your CurrentInstallation issue afterwards to keep this issue active and hopefully resolve it in the near future.

Kind Regards
Tobias

@TobiasPott
Copy link
Member

This issue does no longer occur on the latest state of the master branch (merge of #329).
If an issue related to this or any other part of the SDK reappears, please create a new issue to discuss possible solutions or create a pull request to provide a fix.

@TobiasPott TobiasPott closed this Jun 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants