[ad_1]
This drawback is just like this query: iPhone app crashing in TestFlight, working nice in simulator and iPhone Units
The path is lifeless on that one, and I nonetheless have the issue.
I’ve an app that on beginning, runs this:
override func viewDidLoad() {
tremendous.viewDidLoad()
print("right here we go")
CoreDataManager.shared.initialize()
NotificationCenter.default.addObserver(self, selector: #selector(updateAfterData(notification:)),
identify: oNames.identify(.callHomeCompleted), object: nil)
Event.appBuild = UIApplication.construct
Event.appRelease = UIApplication.launch
print(" (Event.appRelease) (Event.appBuild)")
_ = Event.callHome()
// return
createUI()
let notificationCenter = NotificationCenter.default
notificationCenter.addObserver(self, selector: #selector(appMovedToFront), identify: UIApplication.willEnterForegroundNotification, object: nil)
//return
initializeUI()
}
With no adjustments to this code, this has been working completely nice for months, together with on production-released app. The routines known as are all an identical to what was there earlier than, when it was operating nice.
Out of the blue, nevertheless, and whereas working completely nice on the Simulator and on a linked matching iPhone, on TestFlight, it began crashing on startup. Checks of the server log that it connects to confirmed it by no means makes that request. including the “right here we go” remark didn’t present up both within the app logs (on Heroku). A take a look at the place the CoreDataManager initialization was run after which the app returned labored nice. The display screen was clean, as a result of the UI is constructed by createUI(). Nevertheless it appears clear that there’s nothing within the pre-viewDidLoad course of that’s inflicting an issue.
All that modified was I added a button, that opens a segue to a different VC that additionally checks nice. When that button is just not added (the VC was already in place), the issue persists. However once more, all that works nice on Simulator and an precise iPhone.
Infuriatingly, a brand new model despatched to AppStoreConnect was declined as a result of I hit the each day add restrict, so I am ready a day. In fact, the one cause I hit the restrict was the countless troubleshooting explicit to this drawback….
In any case, the issue is a normal one, and I’ve skilled it as soon as earlier than on this mission. TestFlight model crashes, however nothing else does. No crash report in TestFlight. Minor, non-sigificant code chasing, like including returns at completely different phases and all the pieces runs okay…. then take away all of the return on the final take a look at, and all of it works nice…
Somebody should have had this drawback and know a repair…
[ad_2]
