As a Team Foundation Server administrator I'm not able to turn off the Build Failed notifications. Is there a possibility to do that. The Build Notification is sent to the whole team.
I've tried to turn of this message in my own personal Notification Settings. Also in the Team nofication settings and in the notification settings of the Default Collection (that's where my project belongs).
The Build Failed Notification is greyed out for me. The only ability I have is to Turn Off the notification which I did. Unfortunately the Build Failed message will be sent when a build fails.
Can anyone assist me to turn off the build failed notification to the whole team?
You could directly turn off the team notifications in Project Settings--Notifications--Project team
The sample screenshot from Azure DevOps/TFS server 2019 for your reference：
For collection level Notifications, you could choose to disable the subscription.
Note: This will effect any project in the collection.
Finally, I found the reason which was responsible for sending the build failed mails. It was a subscribtion of which I thought is was disabled. Sorry for this question....
Related
I'm using react-native-push-notification.
I'm trying to test push notifications, if I build app and upload it to testflight it shows remote notifications just fine, but when I do it with xcode build on a real device it doesn't react at all (I'm getting onRegister call and notification token though). This problem is only on IOS, android getting notifications in production and development. Can't google anything related so probably I'm missing something.
P.S. I'm using backend to send notifications through firebase
you have to go in capaibility in xcode and active PushNotification first
for more info see this
hope you have followed all the steps to get the APNS certificate and attached that to your xcode, before the build, if not please do so.
Also, in addition you need to have .pem file to add to your Firebase to make your ios app enable to send and receive push.
Over the past two years, we've had around 3-400 beta testers. After Apples update to TestFlight the summer of 2017, we've had problems with nearly all our TestFlight-uploads. Sometimes our beta testers receive email/notification about "a new build is ready to test" 90 days too late, at the exact time the build expires, and sometimes they don't receive notification at all. Just a handful of times it works as expected, that they get notified when we the build is available to test.
Is there a secret trick to managing TestFlight?
I upload the build, click "provide export compliance"-thing, add my internal and external group, and click "Start testing". The build automatically gets available for internal testing, and is sent to beta-review for Apple for external testing. They approve it within 24h, and the build is available in the TestFlight-app for all our beta-testers. But none of them got a notification saying there's a new build..
Followup: How can we fix this now? Do we have to upload a completely new build, or can I remove the "external testers"-group from the build and re-add them again. Will they receive a "new build available"-notifications?
Will they also receive "Build is no longer available for testing" at the moment I remove the external group from the currently active new build? Meh..
Ok. It baffles me how extremely bad Apples dev-websites and services are.
So, in my newly uploaded build, there are two "groups". One called "iTunes Connect Users", which are the internal users who are invited to the developer team. They got an email and a notification immediately when I clicked "Start Testing", because a review is not needed for internal testing.
The other group is called "External testers". The build is available for them, but they didn't get notified when the build was approved by Apple.
I was considering removing the "External testers"-group from the build, hoping for a notification when re-adding the group. But, I also thought the group might first receive "This build is no longer available for testing" or something if I removed the group from the build.
I figured I wanted to test this first, to see if testers receive a notification when I remove their group from a build, so I created a new group (called "ExternalTest"), added one single (new)test-member, and added this new group to the same active build, so that there are three groups under that build.
At the very moment I clicked "add group to build", all of our test-devices here, and apparently every single beta-tester, received a push notification from TestFlight, saying that the new build is available to test. Now, our "installed"-number is skyrocketing, as people are updating.
What the hell, Apple?
I agree with you, #Nitish, TestFlight sucks badly.
Having the exact same problem - a build was approved for external testing by Apple yesterday, but no one received a notification. I created a new group now, added my private email to it, and then added the group to the build. Swoosh! All out test devices received the push notification about the new build. Thumb down emote from me, Apple.
I myself have encountered the same problem. My client who is added as a Beta Tester receives a notification when a build is uploaded. (Never reached a state where he would need a notification where build has expired after 90 days). However, his further client is also added as a Beta tester. But doesn't receive notifications.
This is where I would like to say keenly, TestFlight sucks badly. I would suggest, the best way to track this is to check the status of Build installed or not. Usually Apple reviews the Beta build within 24 hours. At that time, make sure to check the above mentioned status. Re-invite the tester if it still doesn't work.
That's the lame way to get along this, unfortunately.
Otherwise, I would suggest going for other libraries such as Hockey or Diawi.
This is the best I can offer :)
I had a go round with the TestFlight crew a while ago about how bad their interface was. I wanted them to have a simple list that you filled out and a Save button so that you didn't have to do it all at once. Then there should be another button, Send To Testers, that you touched when done. Simple, no? Nah, they rejected my suggestion. I pointed out that when you submit an app to iTunes that's exactly how you do it. Nope, we're doing it this stupid way.
The best I can figure out is that you should walk down the left hand list in the TestFlight section one at a time starting with Builds/iOS . When you reach the bottom and fill out App Information/Test Information hitting Save sends out the invitation. Maybe...
We passed from TFS 2015 to TFS 2017.2 last week. Apparently, we don't have the Release option when setting notifications. Do you know why is that? Or how can we enable the Release notifications?
Current Notifications Screenshot
Release notifications are only available with TFS 2018 later and VSTS. It's not able to use it in TFS2017. You could refer below blog:
We are now announcing the feature as generally available on all accounts and be the only available release notification settings
experience. The same experience is also available with TFS 2018.
Managing Release Notifications
As a workaround, you could use some 3rd-party E-mail extensions to notify peoples in the Release definition such as Send Email.
You could also set up your own E-mail extension, just follow this blog as a tutorial: Sending Email Notification from VSTS/TFS Build
I'm trying to upload an app with Application Loader but I get following error :
Apple's web service operation was not successful Unable to
authenticate the package: 54005906.itmsp An unknown error occurred.
(2010)
What is the problem? I really can't find any info.
Its was problem with Apples process. Worked the day after!
I would check following
1. Profile, username, password, certificate 2. Clean Build and Try again.
I kept getting it for several days until I changed Deployment Target from 3.1.3 to 4.3.
I just selected Standard Architectures in both Project and Target, and it worked for me.
I had the same error but fixed it by changing Build Active Architecture Only from
Release YES
to
Release NO.
When submitting a question like this you need to include all the error messages
If you choose to post only the error messages that you think are relevant, you are probably going to choose the wrong messages. If you know how to indentify the extraneous info, you probably don't need to post a question to StackOverflow at all. ;-)
When submitting a question like this there are a few things to note:
• If you submit enough failures in some given time frame, Apple will stop allowing you to connect/submit for some other time frame!
- This is a situation that seems to correct itself overnight in most cases. You can use a different authorized account to get around this. (Create a new one if you gotta.)
• The first 2 items are red herrings
Apple's web service operation was not successful
In spite of how it sounds, this doesn't mean it couldn't connect. This simply means that the ultimate goal was not successful.
As a metaphor: if (ApplicationLoader.DeliverYourApp(SelectedFile)){log("Delivery Successful");} else {msg("Apple's web service operation was not successful");}
Unable to authenticate the package: 81680085.itmsp
Before Apple accepts your package on their server, they want it to pass a few "field sobriety" checks.
From their perspective, it's like "cloud computing". They are saving server resources by doing analysis in the cloud. And the cloud is the workstations of all their developer.apple.com members.
• The "Background Activity" panel (revealed by clicking "Activity...") is very useful to watch.
Seeing "Could not start delivery: all transports failed diagnostics" makes you think there is some form of connection or login error (especially when combined with the top 2 errors. If you open the Background Activity panel early on and watch the entire process, you see that the message that is RED in the screenshot above actually goes through these states:
Upload package to the iTunes Store
Authenticating with the iTunes Store
Verifying assets with the iTunes Store
Could not start delivery: all transports failed diagnostics
Finally, the error in my screenshot actually means...
The IPA file I was given fixes the bug that prevented my previous upload from succeeding, however, the developer forgot to increment the build number and Apple re-rejects it out of principle. This could be avoided if they would implement a build script that does something alone the lines of git log --oneline | wc -l. This is pretty much exactly the way I do it in my projects.
I have so far done the following:
- Generated certificate and private key as .pem, also cat'd them together. Successfully connected to gateway.sandbox.push.apple.com.
- Using the provisional profile with push notifications is enabled for development, I have a basic app that successfully prompted "Do you want to allow push notifications", so this is working correctly
- Obtained the device token
- I have tried pulling a few pre-made files for SSLing into sandbox from the internet just to see if I can get them running before I start development.
The files are the php file posted here: http://www.raywenderlich.com/3443/apple-push-notification-services-tutorial-part-12. I actually got a "Message successfully sent"
The python file posted here: Apple PNS (push notification services) sample code; I had to edit the Python 3 command "fromhash" line to str(float.fromhash(...))
I also tried using the PyAPNs API: https://github.com/simonwhitaker/PyAPNs. I still have use_sandbox set to true.
Obviously I changed the device tokens and public keys/certificates to my own. Sadly I have not received any pushed notifications yet, and I'm not receiving any concrete errors to tell me why. If anyone can shed some light, that would be amazing.
From my comment in radesix's answer, and apologies that I can provide no more detail as it's been a year since I've touched iOS development.
The problem was my provisional profile had the "aps-environment" key set to developer, but for some reason xcode defaulted to "debug". Changing this in the editor solved my problem.
Use a service like urban airship (urbanairship.com) and you'll have this up and running in minutes. Less for you to maintain in the long run also.