testflight

Swift keychain and provisioning profiles

只愿长相守 提交于 2019-11-30 01:02:16
We've created an app in swift that uses keychain. The app works fine when run on a device or in the simulator but can't access the keychain when provisioned via Testflight unless provisioned to a new device that's never had the app previously installed via Xcode 6.1. Following is an excerpt of the keychain code: import UIKit import Security let serviceIdentifier = "com.ourdomain" let kSecClassValue = kSecClass as NSString let kSecAttrAccountValue = kSecAttrAccount as NSString let kSecValueDataValue = kSecValueData as NSString let kSecClassGenericPasswordValue = kSecClassGenericPassword as

Testflight Profile Installation Failed, the SCEP server return an invalid response

℡╲_俬逩灬. 提交于 2019-11-29 23:11:50
One of my user is having trouble installing the TestFlight App (not Apple's TestFlight). He encountered the error: "Profile Installation Failed, the SCEP server return an invalid response." Error http://i60.tinypic.com/mky6j5.jpg I advise him to follow the steps listed here: http://help.testflightapp.com/customer/portal/articles/402816-registration-issues He told me that he has no profile installed in his profiles and after following the steps, he still encounter the same error. I at a lost as to what to do now and any advise will be appreciated. I finally got my testers to get past this SCEP

Xcode: Should I Strip Debug Symbols During Copy?

╄→尐↘猪︶ㄣ 提交于 2019-11-29 22:59:18
The TestFlight SDK recommends setting Strip Debug Symbols During Copy to YES in Xcode Build Settings to enable the best crash reporting possible. I noticed that it's set to YES by default. Should I change it to YES ? Why or why not? I work at TestFlight. Short answer is: set it to YES . Long answer: @Kerni is correct. Before we started symbolicating server side, we needed that data to symbolicate on device. So if you upload your dSYM to TestFlight, you can strip them. If you don't want to upload your dSYM for some reason, you can leave them in and TestFlight can symbolicate on device.

Missing Compliance in Status when i add built for internal testing in Test Flight.How to solve?

浪子不回头ぞ 提交于 2019-11-29 18:35:19
When I added my latest build for internal testing with TestFlight , I saw that it had a "Missing Compliance" status. Is this a major problem? Why does this appear? How can I resolve this issue? mokagio Unless your app is using some special encryption you can simply add Boolean a key to your Info.plist with name ITSAppUsesNonExemptEncryption and value NO . If your app is using custom encryption then you will need to provide extra legal documents and go through a review of your encryption before being able to select builds. If you continue with selecting that version for testing, it will ask for

Testflight SDK and iOS Simulator - how to use?

二次信任 提交于 2019-11-29 14:53:51
I'm a bit puzzled how I'm supposed to use Testflight's SDK jn combination with the iOS Simulator. Let's say I'm starting to integrate Testflight into my project and want to test it on the Simulator. Obviously I will not get any remote logs or checkpoint information because my project hasn't been uploaded (although I'm using the correct team token). But if I upload the project first, it says that it isn't using Testflight SDK - which is of course correct, so I won't get anything either. So I'm facing a chicken-egg problem here or do I misunderstand something? Is Testflight working at all with

Will TestFlight prerelease beta app version update existing App Store version, or install another instance of the app on tester's device?

二次信任 提交于 2019-11-29 14:14:35
问题 We are going to submit a prerelease version of an app to external users, but I wonder: what will their experience be? The user had a production App Store version of the app on the device, and now installs a new beta via TestFlight. Will this be in-place update, with the data preserved, or a completely new install with data wiped, or will TestFlight's version be installed next to production - so that the user has the app twice? Testing is over, and the production-ready version is submitted to

Apple Testfiight App Submission Can't Click Next

落爺英雄遲暮 提交于 2019-11-29 11:11:01
I submitted my TestFlight build, and not I'm trying to select it for external testing. I've done this with the prior beta version, and with several other apps. The problem is I can't click the Next button. All the fields are clearly populated. Also of note, when this happened yesterday there were Support and Marketing fields. Today (for English) they are not there. Anyone else ever experience this? Hello my dear friend there, I am also having your issue this morning. After several trials and errors, I found that turn out the next button greyed out just because we have to fill all description

Installed App from Testflight crashes due to alleged UISearchDisplayController

我与影子孤独终老i 提交于 2019-11-29 10:44:33
问题 I implemented the Dark Mode with the current beta version of XCode in a relatively old app. I uploaded these to the testflight for my testers. However, this crashes for anyone who has the public beta of iOS 13 immediately. I've integrated Crashlytics into the app, and the cause of these crashes is as follows. UISearchDisplayController is no longer supported when using this version of iOS. Please migrate your application to UISearchController. All UISearchDisplayController have already been

Testflight: Cannot upload build, cannot download SDK

醉酒当歌 提交于 2019-11-29 10:38:54
问题 I'm having difficulties with TestFlight today. I've tried to upload ipa for the new app but getting this error: Sorry, we are no longer accepting any new builds that use the TestFlight SDK. Please remove the SDK and re-upload. Learn More. Learn more just point to generic Help portal, not helpful. Thought the problem is with actual SDK (it's not latest version) but when I went to Dashboard/SDK, there is another error waiting for me: Sorry, the TestFlight SDK is no longer available for download

Testflight testers getting “unable to download app could not be installed at this time”

家住魔仙堡 提交于 2019-11-29 05:54:37
问题 I distributed version 1.0, build 1, of my app via TestFlight, and everything worked perfectly. Yesterday I archived and sent out build 2, and now upon tapping the update button, every user seems to be getting an error: Unable to Download App [App name] could not be installed at this time I haven't heard from any users who didn't have build 1 installed already, but looking at iTunes Connect, no user has build 2 installed. 回答1: I've got this error many times, but I saw a really strange pattern