ios - testflight application closes on start -
i'm trying install ad-hoc application through testflight, create ad-hoc provisioning apple portal, build .ipa , submit testflight.
the problem can install application testflight (i don't receive errors), when starts application close without alert or messages.
after test, i've attached device xcode , clicked on 'configure development' (or this, don't remember correctly because can't see again option). after that, application didn't close on startup , works well.
the problem can't distribute application via testflight if have enable development xcode device!
why have behaviour? i'm doing wrong?
thank you
if install application testflight without errors device correctly listed in provisioning profile. problem else.
try looking @ crash logs device see went wrong. can extract them , symbolicate them in xcode.
a correction musigenesis answer: not normal ad-hoc builds not work push notifications! have set , use system correctly.
common sources of errors when ad-hoc builds not receiving push notifications:
- you did not generate new provisioning profile after enabling push app. causes received push token nil.
- you using development certificates connect apns servers. ad hoc builds considered distribution builds, must use production keys.
- you sending mix of development tokens (from dev builds) , production tokens (from ad hoc builds) apns service. causes whole batch of push notifications silently discarded server. keep development, adhoc , production token databases totally separate avoid this. there no way identify tokens poisoning batch, have clear them out , make sure right type of token inserted.
i keep 3 backend instances running app needs register push. 1 development builds, 1 ad-hoc builds , 1 app store builds. example keep separate api endpoints online @ dev.mybackend.com, staging.mybackend.com , production.mybackend.com backed different database instances isolate them.
in xcode project have separate build configurations these types of builds , swap correct backend in using preprocessor macros. separate build configurations handy if want make sure dev builds not reporting wrong analytics production account, correct provisioning profiles automatically used etc. etc.
Comments
Post a Comment