“Request failed with http status code 503”

Hello, On one of our test devices, we stopped receiving push notifications on our app. Upon investigation we noticed that APNs is returning a 410 status code when we try to deliver a notification to this device. In our iOS code, on every launch we call the registerForRemoteNotifications() method of UIApplication to request the device token. Upon successful registration, we receive the token in our app delegate’s application(_:didRegisterForRemoteNotificationsWithDeviceToken:) method. Each time we continue to receive the same token as before, and this token continues to receive a 410 response from APNs. How can we get more info on why this token has been marked as Inactive/Expired by APNs? Why is APNs giving us the same token on device if it has been marked as Inactive/Expired? What is the best way to start receiving push notifications on this device for our app? Is it possible to get a new token without deleting and re-installing the app?

Perhaps this could be repetitive or basic question but I have implemented following code of NEDNSProxyProvider. My basic requirement is I want to process the flow but instead of using data from datagrams I want to use data received from our custom DNS server. After tons of articles documentation Im able to write following code. But it's failing continuously in writeDataGrams with Invalid arguments data and The operation could not be completed because Flow not connected. I know somethings is wrong in processing the data but what is wrong Im not able to figure out. Also I want to know is this even possible to achieve this by using API call inside datagrams for loop and then send data to writedatagrams? After getting JSONResponse Im using third party library to convert query form JSONData binary before sending it to writeDataGrams. https://github.com/Bouke/DNS override func handleNewFlow(_ flow: NEAppProxyFlow) -> Bool { NSLog(DNSProxyProvider: handleFlow) var handled: Bool

Hi, I am running into an error on XCode 15 (iOS 17+). When I am trying to play an iframe on the app. I see this error popup. Warning: -[BETextInput attributedMarkedText] is unimplemented Failed to request allowed query parameters from WebPrivacy. How do I fix this issue? I never saw this before so I am sure it is new. The app use to run fine as well.

Hello I have WkWebview app which load webpage here is my initialization code for wkwebview override func loadView() { let webConfiguration = WKWebViewConfiguration() let preferences = WKPreferences() preferences.javaScriptEnabled = true preferences.setValue(true, forKey: DeveloperExtrasEnabled) webConfiguration.preferences = preferences browser = WKWebView(frame: .zero, configuration: webConfiguration) browser.navigationDelegate = self browser.uiDelegate = self view = browser } and here is request let url = URL(string: urlString) request = URLRequest(url: url!,cachePolicy: .reloadIgnoringLocalAndRemoteCacheData,timeoutInterval: 360) browser.navigationDelegate = self browser.uiDelegate = self browser.load(request) This works fine but when I click on subpage which load's more that 60s(which is default request timeout interval). I get this error in web-inspector Failed to load resource: The request timed out So my question is. Can I change default ti

Our iOS app talks to our own BLE accessory using CoreBluetooth. This has been working for a few months on all our devices (I have personally tested it on iPod touch 6th gen, iPad mini 2, iPhone 5s, iPhone 6s and iPhone 7). We just got our hands on an iPad mini 4 and, for some reason, have been experiencing issues:- the initial connection triggers the iOS pairing dialog- after entering the proper passkey I am able to read values from the device just fine- any subsequent attempts at reading value (CBPeripheral.readValue) just sits there and the didUpdateValue delegate method is never calledI've been trying to figure out what's happening and, I was looking at the device logs, noticed the following:Oct 23 13:18:38 iPad-mini-03 bluetoothd[77] <Notice>: Received XPC message CBMsgIdCharacteristicReadValue from session net.prolon.Focus-central-746-120 Oct 23 13:18:38 iPad-mini-03 bluetoothd[77] <Notice>: Reading value for characteristic handle 0x002d on device <private> Oct 23 13:18:38 iPad-mini-03

I'm developing an ACME server to issue identity certificates to macOS/iOS devices for MDM attestation, following RFC 8555. Per RFC, the client creates an order, performs authorization, verifies the challenge, and finalizes the order by submitting a CSR to the CA. In my setup, the CA sometimes takes longer to issue the certificate (around 50 seconds). According to RFC 8555, if certificate issuance isn’t complete after the /finalize call, the server should respond with an order object with a processing status. The client should then send a POST-as-GET request to the order resource (e.g., /order/) to check the current state. If the CA still hasn’t issued the certificate, the server should return the order object with the same processing status and include a Retry-After header, indicating when the client should retry. The client is expected to poll the order resource at this specified interval with POST-as-GET requests. However, it seems the Apple ACME client ignores the Retry-

I'm developing an ACME server to issue identity certificates to macOS/iOS devices for MDM attestation, following RFC 8555. Per RFC, the client creates an order, performs authorization, verifies the challenge, and finalizes the order by submitting a CSR to the CA. In my setup, the CA sometimes takes longer to issue the certificate (around 50 seconds). According to RFC 8555, if certificate issuance isn’t complete after the /finalize call, the server should respond with an order object with a processing status. The client should then send a POST-as-GET request to the order resource (e.g., /order/) to check the current state. If the CA still hasn’t issued the certificate, the server should return the order object with the same processing status and include a Retry-After header, indicating when the client should retry. The client is expected to poll the order resource at this specified interval with POST-as-GET requests. However, it seems the Apple ACME client ignores the Retry-