User Profile

So when the first beta arrived, I wanted to check out the new features, same as everyone. I installed on my device and everything seemed fine. Then beta 2 arrived, and I installed the OTA profile and tried to get beta 2, but It never showed up. It was pretty new so I thought I'd have to wait. As my main work does not develop for beta iOS, I forgot about it until the latest beta, and the phone still couldn't find any OTAs available. I then went to restore the phone to beta 5 instead. To restore I had to turn off Find My iPhone, but that also wouldn't connect to the server, so I put my phone into DFU mode and restored from that, hoping beta 5 would fix the connection issues, but it didn't, and I couldn't activate my phone even then. I'm in the process of restoring back to iOS 12.4, hoping a normal release can fix this, and then back to beta 5. I searched the forums and haven't seen anything in iOS 13 beta but I have found similar posts for iOS 11, 10, and 9. I didn't see any answers or success stories though. Is my phone now useless?Edit:Downgraded to iOS 12, but It cannot log into my iTunes account. I enter my Apple Id email and a spinner appears and loads forever. Guess I've learned never to install beta software.

So I'm running into a really odd visual glitch where my cells contentView doesn't change after performing the action of a swipe for `editActionsForRowAt`. It does work the first time, and every other time after though. I believe this issue is caused by NSFetchedResultsController, but also specific to my single app. I can replicate this issue in 3 different table controllers, with custom cells and a plain UITableViewCell only setting the textLabel property. I've tried disabling as much code as possible but can still reproduce. I converted one of the views to not use NSFetchedResultsController and to just perform it's own fetches but it didn't reproduce even with custom cells on there. I created a new project and implemented NSFetchedResultsController and wasn't able to reproduce. I'm not sure how else to fix at this point. Here's a link to a tweet with picture of the visual bug. https://twitter.com/maxhasadhd/status/1153112418316431365