iOS 13 TestFlight not reporting crash, only feedback.json
This happens when the watchdog kills the application due to some reason. we can check the logs in the Analytic & Improvement section
This happens when the watchdog kills the application due to some reason. we can check the logs in the Analytic & Improvement section
TestFlight users don’t require a sandbox account, but they will test against an automatically created sandbox account. Sandbox Accounts The moment a tester opens your application, a sandbox account is created for them. This means it’s no longer necessary to create test accounts in iTunes Connect. Testing In-App Purchases was never easier. Source Note that … Read more
There is a maximum number of 10 devices that can be registered to each user. To remove a device from your user account: 1. Launch TestFlight on one of the devices you are signed in. 2. Tap on the “Apple ID” button at the bottom. 3. On the next screen click on the “Edit” button … Read more
I finally got my testers to get past this SCEP error. Hopefully this works for you too. Workaround: Open the iOS Settings app, select Safari then tap on “Clear History and Website Data” Open the Safari app and go to testflightapp.com Log into your TestFlight account On the “Connect this device by installing profile” screen, … Read more
Got an answer from Apple Developer Technical Support which says it is a bug on Apple’s side. this is the suggested workaround below which did not work for me: To diagnose this issue, you should export the IPA you are sending to the App Store from Xcode. Since IPAs are zip files, you can decompress … Read more
Put this in AppDelegate.cs: [DllImport (“libc”)] private static extern int sigaction (Signal sig, IntPtr act, IntPtr oact); enum Signal { SIGBUS = 10, SIGSEGV = 11 } static void EnableCrashReporting () { IntPtr sigbus = Marshal.AllocHGlobal (512); IntPtr sigsegv = Marshal.AllocHGlobal (512); // Store Mono SIGSEGV and SIGBUS handlers sigaction (Signal.SIGBUS, IntPtr.Zero, sigbus); sigaction (Signal.SIGSEGV, … Read more
No need to rebuild the .ipa Upload the .ipa Send invitations to testers Add their devices to provisioning profile Download the approved profile Go to TestFlight builds >> Permissions >> Upload profile … Click Send Email/Update You’re done – the new user get’s the link to download the app. Hope that helps.
after you add the user for testing. the user should get an email. open that email by your iOS device, then click “Start testing” it will bring you to testFlight to download the app directly. If you open that email via computer, and then click “Start testing” it will show you another page which have … Read more
clear your cache and cookies in Safari, make sure your device is in provisioning profile and provisioning profile is installed on the device. If everything mentioned above didn’t help, try to create a new build with higher build number and try to distribute your app again
I had this as well. I removed the users from the test group (I did not delete them from TestFlight) and then re-added them. That gave me the “resend invite” option, which I used. The testers received the new invite, and were able to install the build.