|
|
|
|
|
|
by grantland
3955 days ago
|
|
|
It's unfortunate to hear you had a bad experience with our SDK :( We've actually fixed a few ANR deadlocks in this last release [1], as well as a few others in the releases since 1.8.0 [2]. If you can supply reproduction steps, we'd love to be able to fix this issue as I'm sure you're not the only one experiencing it. In addition, we're more than happy to accept fixes as contributions :D [1]: https://github.com/ParsePlatform/Parse-SDK-Android/releases/... [2]: https://parse.com/docs/downloads |
|
|
I think the guy on the ticket didn't really understand what I was saying. I'm happy to provide any extra info necessary (what I can remember anyway).
From looking through the code, the issue still appears to exist. [1] is called on the Main Thread. It eventually calls to a synchronized block [2]. [3] is called from a background thread and uses the same synchronised lock.
--> Main Thread + Background Thread using same lock == Trouble
One other annoying issue I reported (#937744189590638 - private) was not being able to update the GCM token. The field is readonly, even though the GCM docs explicitly state that the key changes over time. Meaning you have to delete and recreate the Installation - and what happens if you have other objects linked to that installation? Super annoying. Could be easily solved by making that field writable.
[1]: https://github.com/ParsePlatform/Parse-SDK-Android/blob/mast...
[2]: https://github.com/ParsePlatform/Parse-SDK-Android/blob/mast...
[3]: https://github.com/ParsePlatform/Parse-SDK-Android/blob/mast...