I need some help with the Team Alerts. I know how to setup the Team alerts and it works for situations like:
Build done
My Build done
Build failed
My Build failed
and so on
What I would like to cover is the following situation:
A Build failed. -> Users get a Mail that it failed.
Build gets fixed. -> Users get a Mail that the Build got fixed.
Build gets NOT fixed. -> Users do not get a Mail that is telling them, that the build is still broken.
So I would like to have Team alerts based on the Build Status and if it changes.
I don´t want a mail per good build and a mail per broken build.
I want mails for Builds that change the Build Status from Broken to Succeed and from Succeed to broken.
Is that even possible? I only see Build quality but that has nothing to do with the status.
Builds have a value called "build quality" that you can change. If you add values of "fixed" and "not fixed" you can get alerts based on this value changing.
Then all you have to do is get folks to update the value...
Related
I have published my app to testflight and it is "ready to submit" ready to submit here, however when I am trying to add it to my external testing build group it keeps showing an errorerror, so I am not really sure what is wrong with it. My previous build have no issues , but ever since I encountered this problem all my previous build got expired tooexpired. Please help
I also had this problem, and all previous commits were invalid. The latest committed version cannot be added to external testing.
I archived a new version of application on XCode and uploaded it on app store using XCode , however when I open all builds from app store connect , I am not able to find the build. Thus I am not able to choose the build on the version. to submit for review.
I'm having the same issue as well, it has been 20 hours since I upload my build when I'm writing this and it's still nowhere to be seen.
I also tried to upload a second build and it's also not showing.
So I believe it's an Apple issue and not isolated, looks like we can only wait for now.
Edit: It works now. I assume it works for everyone now.
I also had this issue this morning. I have just now uploaded a new build of my app and the new build now appears, the missing one still doesn't appear. You will need to change the version number and re-archive your app, as otherwise it will be rejected as a redundant upload.
Update after 10 minutes the new build also disappears. Awesome..
After archieved file uploaded successfully it will go into processing stage. Where they are checking the internal settings using the automated tools.
Things will be checked like if any permission issues coming etc.
Lets say of example if you are using camera into your application but you have not given permission into.plist file than it will get failed into processing & removed build from the App Store.
Also if you have set up the permission properly but not given instructions that how & why this gets used than also build will get failed into processing stage. So there can be various reasons.
Ofcourse they will send you an email to your Admin email Id about the build failed while processing with the reason so by that you can resolve the issue.
Hope this will helps to everyone.
I know its duplicate question, I want to update my app and after getting upload successful through the Xcode I can't see the new version...
I want to know how long it usually takes until ill see that? and if after I got upload successful could be another problem why its not upload? if yes what are the problems might be?
I updated the version and the build number, so its not the issue
thank you for the help
So I will post an answer since a comment is to short to answer this.
So the step for the release are:
Upload a build from Xcode
Wait for the build to be processed (this can take some time)
You will be notified by itunesconnect when the processing is done
In this stage the processing can already detect some issues with your app, like missing assets or something like that
You can check the status of your build in the activity tab
You won't get any "App Store status" until you actually release it. Now after the processing is done, you can select the build from the "My App -> App Name" in the "Build" section, there is a "+" that, in my opinion is placed very bad.
My connection was dropped while I am uploading the archive to the apps store.. and it showed Uploaded successfully with big green tick..
And also it goes to the app store and wait forever in the processing state. So I just uploaded it with the new build number and it's processed within less than 10 minutes.
but troubles are not over :(
then I couldn't select my latest build for test it still showed that stuck one..
What can I do for this ?
====================================================================
This has happened to me a few times already i.e. when a binary doesn't finish processing due to connection drop or other issues (on apple side).
Just upload a new build and use that build for release or test flight. Don't worry about the build that never finishes. Just ignore it and move on.
If you are still seeing build 2 as the latest under testfligth section, then logout, clear your browser cache, log back in and see. Clearly your build 3 is the latest one. itunesconnect is super flaky.
Use apple support as a last resort. They will take days to solve something as simple as this.
In my experience when the build stays greyed out and (processing) for longer than a few minutes it will stay forever like that. Best to just re-upload and wait for the new build to process. It does take a bit of time to show up for testing though.
These are the steps which I did to got build to the testflight internal testers
to show Export Compliance add below line
to info.plist
<key>ITSAppUsesNonExemptEncryption</key><false/>
change version no to different one (not the build no)
create archive and upload it without upload bitcode enable tick
This has been happening for multiple build recently for my account. I upload the build to TestFlight. It gives me a success message. However, it creates 2 entries for the same build even though I upload the build just once as seen in the screenshot below. One of the entries remains in Processing state forever. The other entry completes Processing and becomes Active.
After the entry is Active, if I go to the TestFlight option to select it for testing, it shows it grayed out and doesn't allow me to test this.
The only way I can fix this is to generate another build with a new build version string and upload it to TestFlight and hope that it doesn't get stuck the same way.
Anyone else facing this issue and any advise on how to fix this?
Thanks.