Post

Replies

Boosts

Views

Activity

Reply to A timestamp was expected but was not found
I don’t think this is an apple issue that you are encountering. We have had no issues from any of our networks or build machines since the original issue was resolved over a year ago. As Quinn mentioned, this appears to be a networking issue on your own network. I would suggest reaching out to your IT and security teams and see what changes they made on July 18th to determine if there may be new firewall rules that they recently put into place that are preventing access to the time stamp service. I know that many organizations will try to “lock down” their networks - particularly those networks that have access to source code - and this can cause problems with the time stamping and notarization services. In fact, just a few months ago, my own organization did a firewall rule review, updated some rules, and broke our access for timestamping and notarization. we had to re-request our firewall exemptions to our internal security team to allow the signing and notarization to work again. But the most important thing is, this is doesn’t look like an apple issue, and there is nothing that can be done from apples side to resolve it. I would suggest working with your company help desk, IT, and/or security teams to resolve this issue. The document at https://support.apple.com/en-us/HT210060 is likely a good place to start for what endpoints need to be available from your network (there may be additional endpoints - for example, I don’t see timestamp.apple.com on that list - we just ensure that we can access everything on 17.0.0.0/8 and have had no problems). If, after working and ruling out your own organizations networking issues, there continues to be a problem, I suggest you open a developer support incident with apple - this thread is for a completely separate issue from over a year ago that has been resolved - and there are MANY people on this thread who do not need to be getting notifications of your corporate firewall issues.
Topic: Code Signing SubTopic: General Tags:
Jul ’22
Reply to MDM payload for preventing signal delivery
It isn't needed - we are just seeing on some customer machines that signals are not being delivered to our application (we send SIGUSR* signals to communicate between some troubleshooting scripts we have and our application). In some cases, those signals are not getting delivered to our application, and we were wondering if it might be related to something that they are doing with their MDM configuration.
Topic: App & System Services SubTopic: Core OS Tags:
Jan ’22
Reply to A timestamp was expected but was not found
I don’t think this is an apple issue that you are encountering. We have had no issues from any of our networks or build machines since the original issue was resolved over a year ago. As Quinn mentioned, this appears to be a networking issue on your own network. I would suggest reaching out to your IT and security teams and see what changes they made on July 18th to determine if there may be new firewall rules that they recently put into place that are preventing access to the time stamp service. I know that many organizations will try to “lock down” their networks - particularly those networks that have access to source code - and this can cause problems with the time stamping and notarization services. In fact, just a few months ago, my own organization did a firewall rule review, updated some rules, and broke our access for timestamping and notarization. we had to re-request our firewall exemptions to our internal security team to allow the signing and notarization to work again. But the most important thing is, this is doesn’t look like an apple issue, and there is nothing that can be done from apples side to resolve it. I would suggest working with your company help desk, IT, and/or security teams to resolve this issue. The document at https://support.apple.com/en-us/HT210060 is likely a good place to start for what endpoints need to be available from your network (there may be additional endpoints - for example, I don’t see timestamp.apple.com on that list - we just ensure that we can access everything on 17.0.0.0/8 and have had no problems). If, after working and ruling out your own organizations networking issues, there continues to be a problem, I suggest you open a developer support incident with apple - this thread is for a completely separate issue from over a year ago that has been resolved - and there are MANY people on this thread who do not need to be getting notifications of your corporate firewall issues.
Topic: Code Signing SubTopic: General Tags:
Replies
Boosts
Views
Activity
Jul ’22
Reply to MDM payload for preventing signal delivery
It isn't needed - we are just seeing on some customer machines that signals are not being delivered to our application (we send SIGUSR* signals to communicate between some troubleshooting scripts we have and our application). In some cases, those signals are not getting delivered to our application, and we were wondering if it might be related to something that they are doing with their MDM configuration.
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Jan ’22