TestFlight didn't show last build - testflight

since upload last three build tester didn't get any update in testflight for testing a build i found many solution in stack overflow but none of the solution helped me out.
my appstore build:
i found solution from here ...
https://stackoverflow.com/a/60171888/5362750
Thanks all of you for support

Check in the "Activity Tab" where you can check the current activity of each build and if it was failed it would mention there , Also make sure that the appstore URL , Scheme Name were not changed during the time

Related

fastlane package questions:Couldn't find app 'com.xxx.xx' on the account of 'xxx#com.cn' on iTunes Connect

enter image description here
this is my first time to use fastlane, i want to upload ipa file to testflight, in the Fastfile, i write this:
enter image description here
but when i excuted 'fastlane beta' in command line, it appeared error "Couldn't find app 'com.xxx.RFTestDemo' on the account of 'aaa#xx.com.cn' on iTunes Connect", i don't know what's wrong, hope someone to help me, thanks very much.
EDIT 2022: This issue popped back up as I was attempting upload to Testflight
FURTHER EDIT: Fastlane 2.204.2 is the official fix - bump to that one or remove the explicit version dependency for 2.204.1 to resolve
I started seeing the same issue this week after not touching the files for quite some time (we use Deliver and Pilotfiles for upload/submissions). From Fastlanes release pages: "There is an issue with how App Store Connect API is handling /v1/apps?filter[bundleId]= where the bundle identifier is greater than 25 characters."
As an interim solution please update fastlane versions to point to 2.204.1 (had to manually specify the version in our Gemfile) this is going to be a temp fix though, so watch for upcoming releases and flip back accordingly
Reference https://github.com/fastlane/fastlane/releases
I faced this same issue when running fastlane ios beta despite having the app correctly set up on my account, and found the cause to be the app identifier in my project's fastlane configuration was mis-spelt using the wrong case (eg 'com.Pxxx' instead of 'com.pxxx').
Correcting this in the first line of ios/fastlane/Appfile fixed the issue for me.
app_identifier("com.xxx")

Upload Build Using XCode 9

As IOS release its new updates we have IOS-11 now and to support we have Xcode9.
Xcode-9 has changes its upload process of build to i-Tunes and its quite unfamiliar for us to Follow the process.
Recently i need to upload the build but the selection of certificate section is quite confusing.
I have choose my distribution certificates but i it will not allow me to proceed further
Sometimes its says : 'Profile is not manually managed.'
Sometimes its says : Profile is not Appstore certificates.
Please if anyone can guide me How to Upload build using Xcode-9
Thanks.
I think choosing Automatically manage signing, and trying to upload a build using Application Loader will solve you problem.

ITunesConnect - unable to select build

I am using Xcode 8 and I am trying to submit a newer version of my app to iTunesConnect. However I could not select any build version even though I tried to change the build number. See screenshot
I also tried waiting for a couple of hours with no impact.
Surprisingly Apple started sending out emails which tells you why your build wasn't accepted. I didn't see this email until the next day.
Dear developer,
We have discovered one or more issues with your recent delivery for . To process your delivery, the following issues must be corrected:
This app attempts to access privacy-sensitive data without a usage description. The app's Info.plist must contain an NSContactsUsageDescription key with a string value explaining to the user how the app uses this data.
Once these issues have been corrected, you can then redeliver the corrected binary.
Regards,
The App Store team
Once I fixed the issues and re-submitted the binary, I didn't see my build instantly. However after 10min or so, I get an email from Apple
iTunes Connect: Version 5.2 has completed processing.
Now when I look at iTunes .. the plus symbol next to the 'Build' section appears.
Hope this post helps others who run into the same issue.

Failed to submit app to iTunes Store

I am having some problems when trying to submit my iPhone app to store using Xcode 5 that my app is always failed validation with below errors:
Apple's web service operation was not successful
Unable to authenticate the package: [My app id, ex: 123456789].itmsp
ERROR ITEMS-9000: "The bundle [Bundle ID, ex: com.myapp.mobile] at bundle path 'Payload/[My App Name].app' is not signed using an Apple submission certificate." at SoftwareAssets/SoftwareAsset (MZItmspSoftwareAssetPackage)
I am quite sure about settings (bundle id, certificate, profile, entitlement) because this is not first time I submit app to store, jut don't know why these issues come up, I have tried to search and found some related article but they don't help.
I have this issue for 1 week.
I just selected Standard Architectures in both Project and Target, and it worked for me.
I had the exact the same error, after hours of trying, adjusting all the parameters like the bundle ID or display name, etc. None of them worked.
Finally I got it work. Here is what I did.
I started all over by deleting all the records in keychain, certificates and provision profiles. And just added one certificate and profile for app distribution. There was only one record to make no confusion. And then boom, it uploaded successfully.
I guess my mistake was to submit multiple times of certificates or provision profiles earlier (although I deleted multiple entries but I did see something strange) because I thought the creation process was stuck so I refreshed the browser. Being patient in each steps will eventually saves more time! :) Good luck!
I got the same error today with xCode 7. I resubmitted with no changes and it went through. Probably Apple bug. I am letting you know that sometimes it is not an issue with our project/target settings.
As far as I can tell, this specific error is intermittent and not caused by anything in the app package. I think many of the answers here are people that saw this error, changed something, and saw the error go away, and assumed that their change made it go away.
I would suggest, if you get this error, just try again (worked for me). If it fails in this exact way a second time, and you have some theory about what will fix it, do that and try again. If that works, undo your fix and see if the failure comes back. In this way you will have proven that there was an identified root cause and a fix.
I don't know the cause, but I had the same exact issue crop up this week and just got things to work. I had checked the build, distribution certificate, provisioning profile. I went through all of the troubleshooting steps in Technical Note TN2250 -- no luck! However, I just got it to upload successfully. I happened to have an old Mac Mini that had Application Loader 2.5.1 on it. I created a zip file from the .app within the Payload folder of the .ipa, put this on a USB drive, and watched as it finally uploaded after trying about 50 times with both Xcode organizer and Application Loader v2.9.
Other people have reccomended reverting to a previous Application Loader version. Perhaps the web service endpoint uses a different (and properly working) certificate validation method for older AL versions.
I too have had the same problem and after many hours I managed to solve.
I finally fixed the problem. You needed to download the "Apple Root Certificate Authority" (http://www.apple.com/certificateauthority/) and put it in your login keychain & system, I also put your iPhone disitrbution certified in your system and set all keychian trust values ​​for all certificates to "system default". Finally went through!
For me the problem was in selecting the wrong iOS distribution code signing identity, where I was using a different team as the provisioning profile.
Probably make sure your Code Signing Identity is set to automatic, which will probably fix this issue.
In XCode 6.3, You have connect actual device and selected in the XCode.
I didn't see this listed on here, but I received this issue and realized that I already had a build for this specific Version # waiting for review on iTunes Connect. I rejected the build in ITC and then tried uploading the build again and it uploaded correctly after that. Just in case this could possibly help anyone else out there with this issue!

My monotouch application refuses to compile for distribution with Array index is out of range

I am unable to compile my app in Monotouch when I select the full enterprise distribution profile I have setup. All the other profiles work ok.
To be specific: when I hit the build button I get
Detecting signing identity...
0 errors 0 warnings, just Build failed. Array index out of range
I am guessing this is a provisioning issue and I have failed to do something important.
There are pointers on the web to adhoc ditribution builds but no real documentation on full enterprise distribution.
I have the following:
Monotouch : Enterprise edition
Apple : Enterprise membership, have installed the corp certificate & dev user certificate and downloaded the provisioning certificates for dev, adhoc & enterprise and finally created the App ID.
I have spent 2 days scouring the web for similar problems but have found nothing really close. At one point I scrubbed all my profiles with Apple Dev site and re imported them and this resolved some other issues I was having.
Having the full enterprise rights/certificate means I do not need UDIDs, I just have to sign my life away to prevent illegal ditribution. The only thing other than just plain missing something on the provisioning front is that the UDID's are held in an array in the certificates and as I have none specified for this build it errors out. (But it shouldn't surely!)
If I use the adhoc distribution which as UDID's specified in it I can load it on my machine.
Any pointers would be greatly received
I had a similar situation.
"mtouch failed to build". No other messages.
Had to go through tech support and eventually found it was a compiler bug and they sent me a patch for my particular case. I assume it will come out in the next release.
However, I did learn two things along the way that may help you.
a) in my case the problem went away if I changed the "Linker Behavior" setting for the project. Project-> [project] Options -> Build -> iPhone Build -> Linker Behavior
Try all available options. See if makes a difference.
b) On the same iPhone Build options page you can enter "-v -v -v" to the "extra arguments setting. Now check the build output after compiling. There may be additional details.
Finally, I pulled my hair out for a few days with an error similar to yours. In the end it was a compiler bug. Novell was quite quick to identify and fix the bug. Maybe just log it with them and see what happens.
Good luck
I had this problem when switching between my "test" and "release" builds, which had different app identifiers -- I'd switched to the "release" provisioning profile, but I forgot to fix the app display name and app identifier under Build / iPhone Application. Doubt the display name makes a difference but the app identifier certainly does.

Resources