I'm using the code for my Core ML model that's automatically generated by XCode. The files say not to modify them at the top, and the files themselves seem to be stored outside of my project, so I'm not sure if any modifications would even persist. So, the MLMultiArray member variables are declared the way they're declared. As for ARC, I've never used it before and I wasn't sure it would give me the behavior I wanted. (How would it know when to free the output of the prediction?)

Thank you for your reply. It sent me in the right direction. I was able to figure out that my output object was actually being retained as intended, but its constituent data (two MLMultiArray member variables) were being freed. I didn't realize that's how things worked. I've been able to solve the problem by calling retain on the MLMultiArrays. Thanks again. You're also right that I was using the term "leak" the wrong way. I'm working on a command line program and it doesn't have an event loop. So NSObjects don't get freed unless I do something to manually free them. I didn't really understand that last night but I've been learning.

Done. Feedback FB7843105.

Thanks guys--using a pool of player nodes is a great idea.

I'm in exactly the same situation as you. I've been using playerID for authentication for years.By deprecating playerID, Apple is basically deleting all my users' accounts and data. Because what's the difference between losing your account and data, and not being able to log in to access it?This will be a data loss "bug" on a spectacular scale.I have started storing teamPlayerID/playerID pairs on my server but am already running into problems. At least one player on my server has a teamPlayerID of "Unavailable Player Identification" but a valid playerID. I have no idea what to do about this.So you are not alone here. Any news from Apple?