Search results for

“DTiPhoneSimulatorErrorDomain Code 2”

162,376 results found

Post

Replies

Boosts

Views

Activity

Reply to Passing closure as a 'sending' parameter risks causing data races between code in the current task and concurrent execution
I fixed the error in the actor by using this code: private var backgroundCompletionHandler: (() async -> Void)? and func getBackgroundCompletionHandler() -> ((() async -> Void)?) { return backgroundCompletionHandler } func setBackgroundCompletionHandler(_ h: (() -> Void)?){ backgroundCompletionHandler=h } func executeCompletionHandler() async{ await backgroundCompletionHandler?() } Yet my error on the app delegate at: func application( _ application: UIApplication, handleEventsForBackgroundURLSession identifier: String, completionHandler: @escaping () -> Void) { let runCompletionHandler = {@MainActor in completionHandler() } Task.init{ await GeoreferenceQueue.shared.setBackgroundCompletionHandler(runCompletionHandler) } } Converting function value of type '@MainActor @Sendable () -> Void' to '() -> Void' loses global actor 'MainActor' is still there. Now I set all functions in the actor to MainActor as well the variable storing the completion: @MainActor private var backgroundCom
Topic: Programming Languages SubTopic: Swift Tags:
3w
Reply to Secure Enclave Cryptokit
[quote='887014022, dverevkin, /thread/786223?answerId=887014022#887014022, /profile/dverevkin'] that does not appear to be the case [/quote] Agreed. Since I posted that my understanding of how this stuff works has shifted, meaning that I no longer believe that the key is tied to your App ID. When you think about this it kinda makes sense. When you store a SE-protected key in the keychain, you have the option to put it in a keychain access group that’s accessible by multiple apps. If the key bytes were tied to your App ID, those other apps wouldn’t be able to use the key. So, I repeated you tests here in my office, and I see the same results. I’m able to successfully pass an SE-protected key between two apps (running on iOS 26.4.2). Pasted in below are the code snippets I used for this. Thanks for setting things straight here! Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com For the source app: func generateAndSaveKey() throw
Topic: Privacy & Security SubTopic: General Tags:
3w
Reply to Localization doesn't work in watchOS widget configuration intent
I managed to perform multiple tests on the physical Apple Watch and I can confirm that the root cause of this problem is the app intent shared between watchOS and widget extension target. Having this file in a single target solves the issue. However, this approach can’t be used to workaround this issue because the widget configuration intent is by design supposed to be used in these two targets. Otherwise, tapping on a widget produces silent errors, which I included in the previous post. Also, sharing intents is necessary to be able to perform ClockKit complications migration and to check widgets configuration from the watchOS app. So we found the root cause, but we don’t have any suitable workaround yet. This problem is clearly watchOS bug. Additionally, I also observed that sharing the intent between iOS app and widget extension doesn’t cause this issue. So it happens only when the intent is shared between watchOS app and widget extension. Also, the problem isn’t caused by sharing the localization
3w
Need info to bypass system.preferences VPN consent prompt on MDM device for standard user
Hi, We have a macOS app that uses NETransparentProxyManager (Transparent App Proxy) with a NETunnelProviderExtension. The Network Extension is configured and deployed via an MDM configuration profile. The profile is pushed through Intune MDM as a user-enrolled device (Company Portal enrollment, not ADE/supervised). The MDM profile sets up the Transparent Proxy extension as follows (sanitized snippet): VPNType TransparentProxy TransparentProxy ProviderType app-proxy ProviderBundleIdentifier com.example.app.tunnel ProviderDesignatedRequirement identifier com.example.app.tunnel and anchor apple generic and certificate leaf[subject.OU] = TEAMID RemoteAddress 100.64.0.0 PayloadScope System What we do in code: Call NETransparentProxyManager.loadAllFromPreferences — this correctly returns the MDM-managed profile (1 profile found) We do not call saveToPreferences — the profile already exists We call NEVPNConnection.startVPNTunnel() to connect and NEVPNConnection.stopVPNTunnel() to disconnect Problem: On a
5
0
2.5k
3w
Reply to Passing closure as a 'sending' parameter risks causing data races between code in the current task and concurrent execution
[quote='887212022, fbartolom, /thread/825703?answerId=887212022#887212022, /profile/fbartolom'] Unfortunately using your code … produces … Sending 'completionHandler' risks causing data races [/quote] Hmmm, it didn’t when I tested it. Lemme try that again: Using Xcode 26.4, I created a new project from the iOS > App template template. As part of that, I selected Storyboard from the Interface popup. I changed the Swift Language Version build setting to Swift 6. I added GeoreferenceQueue.swift and copied my GeoreferenceQueue to it. I added my application(_:handleEventsForBackgroundURLSession:completionHandler:) method to the AppDelegate class. It built without error. But keep in mind that my example was meant to be an expedient option. I agree with Etresoft’s comments [1] that you should step back and consider whether you want to change your overall approach. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Well, the comments he
Topic: Programming Languages SubTopic: Swift Tags:
3w
FSKit running example project
Hello there, I am wanting to create a custom FSKit extension, and am trying to get the sample passthrough project running: https://developer.apple.com/documentation/fskit/building-a-passthrough-file-system I have just followed the basic instructions from the tutorial above, so have: Selected my team for the signing certificate (required for FSKit module). Built and run. Enabled Passthrough file system under File System Extensions. Made a test directory to mount to: mkdir ~/test But when I run the mount command, I get the following error: mount -t passthrough ~/Documents ~/test mount: Loading resource: The operation couldn’t be completed. (com.apple.extensionKit.errorDomain error 2.) mount: exec /Library/Filesystems/passthrough.fs/Contents/Resources/mount_passthrough for /Users/xxxxxxxx/test: No such file or directory mount: /Users/xxxxxxxx/test failed with 72 The contents of /Library/Filesystems/ is empty, so I don't know if allowing the extension is meant to add something to this directory or not. A
3
0
237
3w
Can't enroll; support is totally useless
https://developer.apple.com/enroll/identity/status Your enrollment could not be completed. Your enrollment in the Apple Developer Program could not be completed at this time. That's all I get. I contacted email support, they took seven days to respond with this message: Hello, Thank you for contacting Developer Support. I would first like to apologize for this delayed answer. It is certainly not the normal waiting time for an answer from Developer Support. We are currently facing a huge number of requests from our customers and your patience is well appreciated. I understand you are having issues submitting your enrollment. We can’t verify your identity with the Apple Developer app or provide further assistance with the Apple Account for Apple developer programs. You can still take advantage of great content using your Apple Account in Xcode to develop and test apps on your own device. Learn more about Xcode development. If you have additional questions related to this request, reply to this email or visit yo
2
0
115
2w
Reply to Multipeer Connectivity connection is flaky on iOS 26
What Kevin said but also… [quote='887219022, pascalgnaedinger, /thread/803339?answerId=887219022#887219022, /profile/pascalgnaedinger'] But as long as the MultipeerConnectivity framework is … not officially deprecated. [/quote] The fact that Multipeer Connectivity is not officially deprecated is an ongoing source of confusion, one that I’ve been trying to rectify for years (r. 83185901). There are two ways to resolve that confusion: Fix the various bugs affecting Multipeer Connectivity. Formally deprecate the framework. I’d bet dollars to doughnuts [1] that the ultimate resolution is gonna be that second one. So, if you’re investing time with this framework, you should carefully consider whether that’s time well spent. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Actually, doughnuts to dollars, because doughnuts have got a lot more expensive since that idiom was coined back in the 1800s (-:
3w
Sending 'geoRegion' risks causing data races
I have this simple piece of code that of course correctly ran in Swift 5: func geoRegion()-> CLRegion?{ guard let location=referenceLocation else{ return nil } return CLCircularRegion(center:location.coordinate, radius:50000, identifier:georeferencing) } func placemarksForAddress(_ address: String) async throws -> [CLPlacemark]?{ if let placemark=placemarkCache[address]{ if placemark.location!.distance(from: referenceLocation!)<100000{ return [placemark] } } do{ guard let geoRegion=self.geoRegion() else { return nil } let placemarks = try await georeferenceQueue.geocodeAddressString( address, in: geoRegion) if placemarks.count>=0{ self.placemarkCache[address]=MKPlacemark(placemark: placemarks[0]) return placemarks } } catch { let placemarks=try await self.placemarkForLocation(referenceLocation) return placemarks } return nil } That now presents error: Sending task-isolated 'geoRegion' to actor-isolated instance method 'geocodeAddressString(_:in:)' risks causing data races between actor-is
4
0
1.2k
3w
Reply to Sending 'geoRegion' risks causing data races
[quote='887247022, Etresoft, /thread/825634?answerId=887247022#887247022, /profile/Etresoft'] Most Apple APIs, with very few exceptions … should only be called on the main thread. [/quote] I don’t agree with that summary. Ignoring Swift concurrency, I generally group Apple’s Cocoa APIs into four categories: Main thread — These are limited to the main thread, with occasional exceptions. The canonical example of this is AppKit. Thread safe — These have internal locking and can be used from any thread. A good example is NSOperationQueue. Thread or queue confined — These must be used from a specific thread (or queue) that’s not necessarily the main thread (or queue). NSRunLoop is a good example of this. Serialisation required — These have no internal locking but can be used from arbitrary threads as long as you serialise that access. A good example is NSMutableDictionary. Your summary doesn’t include the last two categories, and IME that’s the biggest group of traditional Cocoa APIs. Unfortunately it’s h
Topic: Programming Languages SubTopic: Swift Tags:
3w
Reply to Best practices for bypassing critical system daemons in NETransparentProxyProvider
So there aren’t hard’n’fast rules here. I can explain some tools that you have available, but you have to make your own judgement calls as to best to use those tools in your product. The most critical item here is the sourceAppAuditToken property. This holds the bytes of an audit_token_t, and from that you can use the code signing machinery to get information about the process and its main executable. I’ve talked about this a bunch of times here on the forums. This post has a snippet you can copy, but it’s probably worth you searching for other similar threads for more advice. IMPORTANT The first part of the snippet, getting the audit token and passing it to the code signing API, is canonical. The second part, getting the bundle ID, is not. Bundle IDs aren’t secure on macOS. Once you’re in ‘code siging space’ you can use code signing requirements to check the code in question. For example, the anchor apple requirement will tell you whether the code is from
3w
Reply to Keychain Group
I suspect you’re confused by the various 10-character identifiers used by code signing. I recommend that you have a read of Code Signing Identifiers Explained, and specifically the entries on Team ID, User ID, Team Member ID, and App ID prefix. [quote='825789021, iceboy, /thread/825789, /profile/iceboy'] the retrieved Team ID is an unknown one and does not match the Team ID of my developer certificate [/quote] There are two possibilities here: Your app uses a unique App ID prefix, which by definition doesn’t match your Team ID. You’re using your Team ID as the App ID prefix, but you’re misreading the Team ID in your code signing certificate. It’s hard to tell which of this is correct without more context. What value do you get back in bundleSeedID? Does it match C____2____? If so, that’s your Team ID, which suggests you’ve hit the second case I’ve described above. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + appl
Topic: Privacy & Security SubTopic: General Tags:
3w
Reply to Cannot Install Developer Beta Update OTA or IPSW
[quote='887276022, andersonad, /thread/813869?answerId=887276022#887276022, /profile/andersonad'] No answer whatsoever. [/quote] Indeed. But that in itself is signal. If this were a common issue, it’s likely that someone else would’ve chimed in here. That fact that no one has indicates that there’s something specific to your environment that’s triggering it. In such cases there are two paths forward: A proper investigation A search for workarounds For the first, you’ve already filed bugs about this (FB21642029 and FB21017894) and that’s the correct way to request a proper investigation. For the second, I suggest you try varying your environment, one item at a time, to see if you can work out what’s triggering it. I have a standard set of things that I like try: Try again from a different network. If you’re at work, try doing it at home, or vice versa. Or in your local coffee shop. I regularly see weird problems caused by middleboxen, such as corporate firewalls. Create a new user account on your Mac.
3w
Reply to Passing closure as a 'sending' parameter risks causing data races between code in the current task and concurrent execution
I fixed the error in the actor by using this code: private var backgroundCompletionHandler: (() async -> Void)? and func getBackgroundCompletionHandler() -> ((() async -> Void)?) { return backgroundCompletionHandler } func setBackgroundCompletionHandler(_ h: (() -> Void)?){ backgroundCompletionHandler=h } func executeCompletionHandler() async{ await backgroundCompletionHandler?() } Yet my error on the app delegate at: func application( _ application: UIApplication, handleEventsForBackgroundURLSession identifier: String, completionHandler: @escaping () -> Void) { let runCompletionHandler = {@MainActor in completionHandler() } Task.init{ await GeoreferenceQueue.shared.setBackgroundCompletionHandler(runCompletionHandler) } } Converting function value of type '@MainActor @Sendable () -> Void' to '() -> Void' loses global actor 'MainActor' is still there. Now I set all functions in the actor to MainActor as well the variable storing the completion: @MainActor private var backgroundCom
Topic: Programming Languages SubTopic: Swift Tags:
Replies
Boosts
Views
Activity
3w
Reply to Secure Enclave Cryptokit
[quote='887014022, dverevkin, /thread/786223?answerId=887014022#887014022, /profile/dverevkin'] that does not appear to be the case [/quote] Agreed. Since I posted that my understanding of how this stuff works has shifted, meaning that I no longer believe that the key is tied to your App ID. When you think about this it kinda makes sense. When you store a SE-protected key in the keychain, you have the option to put it in a keychain access group that’s accessible by multiple apps. If the key bytes were tied to your App ID, those other apps wouldn’t be able to use the key. So, I repeated you tests here in my office, and I see the same results. I’m able to successfully pass an SE-protected key between two apps (running on iOS 26.4.2). Pasted in below are the code snippets I used for this. Thanks for setting things straight here! Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com For the source app: func generateAndSaveKey() throw
Topic: Privacy & Security SubTopic: General Tags:
Replies
Boosts
Views
Activity
3w
Reply to Localization doesn't work in watchOS widget configuration intent
I managed to perform multiple tests on the physical Apple Watch and I can confirm that the root cause of this problem is the app intent shared between watchOS and widget extension target. Having this file in a single target solves the issue. However, this approach can’t be used to workaround this issue because the widget configuration intent is by design supposed to be used in these two targets. Otherwise, tapping on a widget produces silent errors, which I included in the previous post. Also, sharing intents is necessary to be able to perform ClockKit complications migration and to check widgets configuration from the watchOS app. So we found the root cause, but we don’t have any suitable workaround yet. This problem is clearly watchOS bug. Additionally, I also observed that sharing the intent between iOS app and widget extension doesn’t cause this issue. So it happens only when the intent is shared between watchOS app and widget extension. Also, the problem isn’t caused by sharing the localization
Replies
Boosts
Views
Activity
3w
Reply to SF Authorization Plugin View Not Receiving Focus on macOS Tahoe 26.4.1
I’ve responded over on that other thread because there’s no point having two threads going concurrently. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Privacy & Security SubTopic: General Tags:
Replies
Boosts
Views
Activity
3w
Need info to bypass system.preferences VPN consent prompt on MDM device for standard user
Hi, We have a macOS app that uses NETransparentProxyManager (Transparent App Proxy) with a NETunnelProviderExtension. The Network Extension is configured and deployed via an MDM configuration profile. The profile is pushed through Intune MDM as a user-enrolled device (Company Portal enrollment, not ADE/supervised). The MDM profile sets up the Transparent Proxy extension as follows (sanitized snippet): VPNType TransparentProxy TransparentProxy ProviderType app-proxy ProviderBundleIdentifier com.example.app.tunnel ProviderDesignatedRequirement identifier com.example.app.tunnel and anchor apple generic and certificate leaf[subject.OU] = TEAMID RemoteAddress 100.64.0.0 PayloadScope System What we do in code: Call NETransparentProxyManager.loadAllFromPreferences — this correctly returns the MDM-managed profile (1 profile found) We do not call saveToPreferences — the profile already exists We call NEVPNConnection.startVPNTunnel() to connect and NEVPNConnection.stopVPNTunnel() to disconnect Problem: On a
Replies
5
Boosts
0
Views
2.5k
Activity
3w
Reply to Passing closure as a 'sending' parameter risks causing data races between code in the current task and concurrent execution
[quote='887212022, fbartolom, /thread/825703?answerId=887212022#887212022, /profile/fbartolom'] Unfortunately using your code … produces … Sending 'completionHandler' risks causing data races [/quote] Hmmm, it didn’t when I tested it. Lemme try that again: Using Xcode 26.4, I created a new project from the iOS > App template template. As part of that, I selected Storyboard from the Interface popup. I changed the Swift Language Version build setting to Swift 6. I added GeoreferenceQueue.swift and copied my GeoreferenceQueue to it. I added my application(_:handleEventsForBackgroundURLSession:completionHandler:) method to the AppDelegate class. It built without error. But keep in mind that my example was meant to be an expedient option. I agree with Etresoft’s comments [1] that you should step back and consider whether you want to change your overall approach. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Well, the comments he
Topic: Programming Languages SubTopic: Swift Tags:
Replies
Boosts
Views
Activity
3w
FSKit running example project
Hello there, I am wanting to create a custom FSKit extension, and am trying to get the sample passthrough project running: https://developer.apple.com/documentation/fskit/building-a-passthrough-file-system I have just followed the basic instructions from the tutorial above, so have: Selected my team for the signing certificate (required for FSKit module). Built and run. Enabled Passthrough file system under File System Extensions. Made a test directory to mount to: mkdir ~/test But when I run the mount command, I get the following error: mount -t passthrough ~/Documents ~/test mount: Loading resource: The operation couldn’t be completed. (com.apple.extensionKit.errorDomain error 2.) mount: exec /Library/Filesystems/passthrough.fs/Contents/Resources/mount_passthrough for /Users/xxxxxxxx/test: No such file or directory mount: /Users/xxxxxxxx/test failed with 72 The contents of /Library/Filesystems/ is empty, so I don't know if allowing the extension is meant to add something to this directory or not. A
Replies
3
Boosts
0
Views
237
Activity
3w
Can't enroll; support is totally useless
https://developer.apple.com/enroll/identity/status Your enrollment could not be completed. Your enrollment in the Apple Developer Program could not be completed at this time. That's all I get. I contacted email support, they took seven days to respond with this message: Hello, Thank you for contacting Developer Support. I would first like to apologize for this delayed answer. It is certainly not the normal waiting time for an answer from Developer Support. We are currently facing a huge number of requests from our customers and your patience is well appreciated. I understand you are having issues submitting your enrollment. We can’t verify your identity with the Apple Developer app or provide further assistance with the Apple Account for Apple developer programs. You can still take advantage of great content using your Apple Account in Xcode to develop and test apps on your own device. Learn more about Xcode development. If you have additional questions related to this request, reply to this email or visit yo
Replies
2
Boosts
0
Views
115
Activity
2w
Reply to Can't enroll; support is totally useless
same case for me, long time to wait but no responses by email, for 2 fa auth, this may help https://appuals.com/this-phone-number-cannot-be-used-at-this-time-try-again-later-cannot-verify-phone-number-in-apple-id/
Replies
Boosts
Views
Activity
2w
Reply to Multipeer Connectivity connection is flaky on iOS 26
What Kevin said but also… [quote='887219022, pascalgnaedinger, /thread/803339?answerId=887219022#887219022, /profile/pascalgnaedinger'] But as long as the MultipeerConnectivity framework is … not officially deprecated. [/quote] The fact that Multipeer Connectivity is not officially deprecated is an ongoing source of confusion, one that I’ve been trying to rectify for years (r. 83185901). There are two ways to resolve that confusion: Fix the various bugs affecting Multipeer Connectivity. Formally deprecate the framework. I’d bet dollars to doughnuts [1] that the ultimate resolution is gonna be that second one. So, if you’re investing time with this framework, you should carefully consider whether that’s time well spent. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Actually, doughnuts to dollars, because doughnuts have got a lot more expensive since that idiom was coined back in the 1800s (-:
Replies
Boosts
Views
Activity
3w
Sending 'geoRegion' risks causing data races
I have this simple piece of code that of course correctly ran in Swift 5: func geoRegion()-> CLRegion?{ guard let location=referenceLocation else{ return nil } return CLCircularRegion(center:location.coordinate, radius:50000, identifier:georeferencing) } func placemarksForAddress(_ address: String) async throws -> [CLPlacemark]?{ if let placemark=placemarkCache[address]{ if placemark.location!.distance(from: referenceLocation!)<100000{ return [placemark] } } do{ guard let geoRegion=self.geoRegion() else { return nil } let placemarks = try await georeferenceQueue.geocodeAddressString( address, in: geoRegion) if placemarks.count>=0{ self.placemarkCache[address]=MKPlacemark(placemark: placemarks[0]) return placemarks } } catch { let placemarks=try await self.placemarkForLocation(referenceLocation) return placemarks } return nil } That now presents error: Sending task-isolated 'geoRegion' to actor-isolated instance method 'geocodeAddressString(_:in:)' risks causing data races between actor-is
Replies
4
Boosts
0
Views
1.2k
Activity
3w
Reply to Sending 'geoRegion' risks causing data races
[quote='887247022, Etresoft, /thread/825634?answerId=887247022#887247022, /profile/Etresoft'] Most Apple APIs, with very few exceptions … should only be called on the main thread. [/quote] I don’t agree with that summary. Ignoring Swift concurrency, I generally group Apple’s Cocoa APIs into four categories: Main thread — These are limited to the main thread, with occasional exceptions. The canonical example of this is AppKit. Thread safe — These have internal locking and can be used from any thread. A good example is NSOperationQueue. Thread or queue confined — These must be used from a specific thread (or queue) that’s not necessarily the main thread (or queue). NSRunLoop is a good example of this. Serialisation required — These have no internal locking but can be used from arbitrary threads as long as you serialise that access. A good example is NSMutableDictionary. Your summary doesn’t include the last two categories, and IME that’s the biggest group of traditional Cocoa APIs. Unfortunately it’s h
Topic: Programming Languages SubTopic: Swift Tags:
Replies
Boosts
Views
Activity
3w
Reply to Best practices for bypassing critical system daemons in NETransparentProxyProvider
So there aren’t hard’n’fast rules here. I can explain some tools that you have available, but you have to make your own judgement calls as to best to use those tools in your product. The most critical item here is the sourceAppAuditToken property. This holds the bytes of an audit_token_t, and from that you can use the code signing machinery to get information about the process and its main executable. I’ve talked about this a bunch of times here on the forums. This post has a snippet you can copy, but it’s probably worth you searching for other similar threads for more advice. IMPORTANT The first part of the snippet, getting the audit token and passing it to the code signing API, is canonical. The second part, getting the bundle ID, is not. Bundle IDs aren’t secure on macOS. Once you’re in ‘code siging space’ you can use code signing requirements to check the code in question. For example, the anchor apple requirement will tell you whether the code is from
Replies
Boosts
Views
Activity
3w
Reply to Keychain Group
I suspect you’re confused by the various 10-character identifiers used by code signing. I recommend that you have a read of Code Signing Identifiers Explained, and specifically the entries on Team ID, User ID, Team Member ID, and App ID prefix. [quote='825789021, iceboy, /thread/825789, /profile/iceboy'] the retrieved Team ID is an unknown one and does not match the Team ID of my developer certificate [/quote] There are two possibilities here: Your app uses a unique App ID prefix, which by definition doesn’t match your Team ID. You’re using your Team ID as the App ID prefix, but you’re misreading the Team ID in your code signing certificate. It’s hard to tell which of this is correct without more context. What value do you get back in bundleSeedID? Does it match C____2____? If so, that’s your Team ID, which suggests you’ve hit the second case I’ve described above. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + appl
Topic: Privacy & Security SubTopic: General Tags:
Replies
Boosts
Views
Activity
3w
Reply to Cannot Install Developer Beta Update OTA or IPSW
[quote='887276022, andersonad, /thread/813869?answerId=887276022#887276022, /profile/andersonad'] No answer whatsoever. [/quote] Indeed. But that in itself is signal. If this were a common issue, it’s likely that someone else would’ve chimed in here. That fact that no one has indicates that there’s something specific to your environment that’s triggering it. In such cases there are two paths forward: A proper investigation A search for workarounds For the first, you’ve already filed bugs about this (FB21642029 and FB21017894) and that’s the correct way to request a proper investigation. For the second, I suggest you try varying your environment, one item at a time, to see if you can work out what’s triggering it. I have a standard set of things that I like try: Try again from a different network. If you’re at work, try doing it at home, or vice versa. Or in your local coffee shop. I regularly see weird problems caused by middleboxen, such as corporate firewalls. Create a new user account on your Mac.
Replies
Boosts
Views
Activity
3w