I am making a 2-player turn-based iMessage game, and I am having difficulty getting a workflow together. It seems the SImulator cannot be used because it stops the debug process when you switch user accounts, so I have attempted to connect both my iPhone and iPad to Xcode, and send iMessages to myself to emulate the back-and-forth between players. But I cannot even start a game this way because Xcode launches my Messages app into the last "real" conversation, taking me out of the conversation with myself.Surely there has to be a way to get a process working, or GamePigeon wouldn't have been able to develop so many games? Anyone who's done this kind of thing before: I'm all ears.Thanks in advance!

UserDefaults are getting erased for me on the Simulator (15.0) every time. Some users (iOS/iPad OS 15.0.2) are reporting to me that my app is erasing all their settings after re-launch. In the Simulator, I can reproduce this by quitting the app and relaunching it manually. The same procedure does not cause loss of date on my iPhone or iPad running 15.0.2, but does for a handful of my users. All of the many posts related to this issue seem to be at least 5 years old, but I am having the problem now.

I keep seeing this message in the console log as soon as my app starts, on both the device and in the Simulator: "unable to close due to unfinalized statements or unfinished backups". Having searched the internet for the message, it seems like it could be related to SQLite, which my app does in fact use. Can anyone let me know if this is of any concern, and if so, how to address it?

Hi, I left a team some time back, so I have no access to any developer privileges anymore, as intended. However, I continue to get automatic TestFlight emails about new updates the current devs are making. If I click the unsubscribe link at the bottom of the email it just generates an email with my OWN address in the TO field, which is ridiculous, as I have no access to the project. I do not even have the email of the current developer, so I don't have a practical recourse here. Please fix this Apple!