New builds get uploaded to fabric. I have one-two groups with multiple users in fabric attached to the project. They are not receiving notifications on their test devices with every builds but sporadically. They can download the builds manually through the app, but the emails are not consistent with releases in beta. What does that depend on?
Related
I'm not getting any crash report data on the application dashboard for an app that I had previously setup and configured on a different organization account. I'm able to upload and distribute builds but the crash report data goes to the previous account's dashboard. I thought deleting the app from the previous account dashboard would fix the issue but after deleting the app I'm not getting crash report data in either account now. I don't want to loose the uploaded builds or release history otherwise I would have tried deleting the app from both places and trying to configure it again from the account where I want to distribute builds and receive crash data.
Thanks for reaching out. It sounds like the old organizations API keys are still cached in your app. Please clean your app and check the info.plist and run script build phase (or if Android, AndroidManifest and/or fabric.properties file)
When I send multiple notifications to Apple or Android devices through MFP, Apple devices will display all notifications in the notifications center on the other hand Android will only display one last notification. We are using Unicast Notification to send messages to user devices using this REST API.
Initially my issue got fixed when I implemented solution given in this thread.
But after upgrading to MFP 7.1.0.00.20151227-1725 I started facing the issue again.
It it a known limitation that the attribute gets removed from the file upon re-build, since a re-build re-generates the file...
You need to add it back after a re-build. It is scheduled to be enhanced in the future so this won't be needed.
For now you can use for example an Ant task to replace the wlclient.properties file post-build with a version that contains again the attribute.
We have about 100 testers in our iTunes Connect in total, without about 20-30 of them on each of our apps. When we push a new build (sometimes just with bug-fixes for specific people), we'd like to be able to give access to all our testers, but either send no emails at all, or just emails to the specific people that are affected by that update.
Case in point, unfortunately one of our old keys expired yesterday, and someone was trying to get the app today. So we sorted our key issue, up the version, re-sign the ipa and re-upload to iTunes Connect. We don't want to prevent access to any of our previous testers, and we don't want to email all our users, because it's not a new build, just a re-signed old build.
Currently, and extremely frustratingly, we can't see any way to currently do that, despite that being exactly how it worked when TestFlight was TestFlight.
iTunes Connect - Prerelease - Beta testing with Internal testers says 31 days left, what does this mean?
Will the app uninstall itself after 30 days? Will it become inactive or unusable? What happens?
From some months' experience, I find that my original answer(guess) is not right. If an application has expired on iTunes Connect Beta Testing. It will very soon(in one or two days after the expiration) stop working from the device that has it installed.
Original answer:
Short answer: when the testing period end, testers will no longer be able to accept invites and install builds. Testers that already have builds installed will not be affected.
In this document,
https://developer.apple.com/library/ios/documentation/LanguagesUtilities/Conceptual/iTunesConnect_Guide/Chapters/BetaTestingTheApp.html#//apple_ref/doc/uid/TP40011225-CH35-SW2
Apple says:
“After the 30 day testing period has ended, the build status changes to Expired"
"To continue testing after the 30-day period expires, upload another build. Internal testers will automatically receive an update notification when the new build is available. To distribute the new build to external testers, you must submit it to Beta App Review. Once it is approved, you can send the external testers an update email by clicking Send Invites from the External Testers column on Builds, as shown above."
Apple doesn't describe clearly the behaviors on the tester side when a build expired.
But when I try to turn off the "TestFlight Beta Testing" on an app,
the prompt says:
"Are you sure you want to stop testing?
Testers will no longer be able to accept invites and install builds. Testers that already have builds installed will not be affected."
So I guess the behaviors on the tester side when a build expired are going to be the same
as that when the testing is shut down by turning off the "TestFlight Beta Testing" option.
In my experience with Internal testing, after 30 days, the build changes to Expired, and will no longer launch on devices where it has already been installed. Trying to launch the app will show the splash screen, and then it immediately quits and you're back on the home screen.
I've also found that uploading a new build does NOT automatically send out the update to existing internal testers. Although iTunes Connect will say the build is available, you have to manually toggle TestFlight testing off and then on again to get it to recognize the new build and send out the update emails to existing internal testers.
I've been building and deploying apps for several months now and am aware that provisioning can get a bit sticky at times. But my current situation is particularly unusual.
I can attach my development device and build and run the app on it through Xcode. If I archive it for Ad-Hoc Distribution as an ipa file, I can also successfully load it onto a distribution device via iTunes. However, running it on the device causes an immediate crash: it opens then promptly closes.
There are no permissions errors during the iTunes load, and this issue presents so far on 3 distribution devices, including the same device that it successfully runs when sent via Xcode.
For the life of me I cannot figure out what is going on; in the past, if there was a misplaced profile or a device not added to the profile, you'd get a simple permissions error during the iTunes sync. I've never seen it successfully transfer to a device with no errors, but then crash. I'd love some suggestions as I've been working with this for 2 hours trying to track it all down.
All devices are in the provisioning profile and I reloaded the profiles in XCode to make sure they were current. I also reloaded the ad-hoc profile in iTunes to make it was current.
I've had a similar experience with expired provisioning profiles: dev build of an app opens then immediately closes when run on a device. Double check that all profiles installed on the devices are current.