Geek asks and answers

Testflight closes at startup

I am trying to install an ad-hoc application through testflight, so I create ad-hoc software from the apple portal, I create .ipa and then send it to testflight.

The problem is that I can install the application from testflight (I get no errors), but when it starts the application, it closes without any warnings or messages.

After some testing, I connected the device to xcode, and then clicked the “Configure for development” button (or something like this, I don’t remember correctly, because I can’t see this option again). After that, the application did not close at startup, and it works well.

The problem is that I cannot distribute the application through testflight if I need to enable development using xcode for any device!

Why do I have this behavior? Am I doing something wrong?

thank

+5
source share
2 answers

If you can install the application from TestFlight without errors, your device was correctly listed in the provisioning profile. Your problem is something else.

Try looking at the device crash logs to see what went wrong. you can extract and symbolize them in Xcode.

Correction answer to MusiGenesis: . Of course, for special assemblies, of course, it is not normal to work with push notifications! You just need to properly configure the system and use it.

Common sources of errors when your ad assemblies do not receive push notifications:

  • push . , .
  • APNS. , .
  • ( dev) ( ) APNS. , push- . , adhoc , . , , , .

3 backend , push. , App Store. , API dev.mybackend.com, staging.mybackend.com production.mybackend.com, , .

Xcode . , , , .. ..

+1

2012 , . , . OCMock, 3.0, . , . , OCMock 3.0 . , .

http://ocmock.org/ocmock3/

+1

More articles:


All Articles