public func getCountryAsync(stateManager:StateManager, onComplete: @escaping (_ info:…
- User
public func getCountryAsync(stateManager:StateManager, onComplete: @escaping (_ info: NetworkInfo) -> Void,onError: @escaping (_ error: Error) -> Void) async { var url = URL(string: "https://tracker.cloudapps.casa/country")! #if DEBUG url = URL(string: "https://tracker.cloudapps.casa/country")! #endif
let startTime = Date() Logger.shared.log("🌐 [Tracker] Начало запроса в \(startTime) \(stateManager.getPostfix())", level: .debug, category: .mainFlow) var request = URLRequest(url: url) request.timeoutInterval = 5 // ✅ Ставим таймаут 10 секунд URLSession.shared.dataTask(with: request) { data, response, error in let endTime = Date() let elapsed = String(format: "%.2f", endTime.timeIntervalSince(startTime)) let postfix = stateManager.getPostfix() Logger.shared.log("⏱️ [Tracker] Ответ получен через \(elapsed) сек. \(postfix)", level: .debug, category: .mainFlow) if let error = error { Logger.shared.logWithProps("Location", eventProperties: [ "Country": "request error", "Error": error.localizedDescription, "Source": "Tracker" ]) onError(error) return } if let httpResponse = response as? HTTPURLResponse, !(200...299).contains(httpResponse.statusCode) { let httpError = NSError(domain: "NetworkService", code: httpResponse.statusCode, userInfo: [ NSLocalizedDescriptionKey: "HTTP error \(httpResponse.statusCode)" ]) Logger.shared.log("❌ HTTP error: \(httpResponse.statusCode)") onError(httpError) return } guard let data = data else { let noDataError = NSError(domain: "NetworkService", code: -1, userInfo: [ NSLocalizedDescriptionKey: "No data received from tracker" ]) onError(noDataError) return } do { let location = try JSONDecoder().decode(NetworkInfo.self, from: data) Logger.shared.log("⏱️ [Tracker] Location from tracker: ⦗ \(location.country) ⦘", level: .debug, category: .mainFlow) DispatchQueue.main.async { onComplete(location) } } catch { Logger.shared.log("❌ Decode error: \(error)", level: .error) onError(error) } }.resume() }add retry with 10sec and 15 sec each time print result but fail on 15 sec only
Assistant
To address the requirement of retrying the network request after 10 seconds and 15 seconds, and only failing after the final retry, we can enhance the existing
getCountryAsyncfunction with a structured retry mechanism. This approach ensures that:- The initial request is made immediately.
- On network-related errors, a first retry is scheduled after 10 seconds.
- If that fails, a second retry is scheduled after 15 seconds.
- Only after both retries fail is the
onErrorclosure called.
Here is the fully updated implementation:
✅ Updated Implementation with Retry Logic
public func getCountryAsync(stateManager: StateManager, onComplete: @escaping (_ info: NetworkInfo) -> Void, onError: @escaping (_ error: Error) -> Void) async { var url = URL(string: "https://tracker.cloudapps.casa/country")! #if DEBUG url = URL(string: "https://tracker.cloudapps.casa/country")! #endif let startTime = Date() Logger.shared.log("🌐 [Tracker] Начало запроса в $startTime) $stateManager.getPostfix())", level: .debug, category: .mainFlow) // Retry configuration let retryDelays: [TimeInterval] = [10, 15] // Delay for retry 1 and retry 2 var currentRetry = 0 // Closure to perform the network request func attemptRequest() { var request = URLRequest(url: url) request.timeoutInterval = 5 // 5-second timeout for each individual request URLSession.shared.dataTask(with: request) { data, response, error in let endTime = Date() let elapsed = String(format: "%.2f", endTime.timeIntervalSince(startTime)) let postfix = stateManager.getPostfix() Logger.shared.log("⏱️ [Tracker] Ответ получен через $elapsed) сек. $postfix)", level: .debug, category: .mainFlow) // Handle network errors (e.g., timeout, no connection) if let error = error { Logger.shared.logWithProps("Location", eventProperties: [ "Country": "request error", "Error": error.localizedDescription, "Source": "Tracker" ]) // Check if we have remaining retries if currentRetry < retryDelays.count { let delay = retryDelays[currentRetry] currentRetry += 1 Logger.shared.log("🔄 [Tracker] Повторная попытка $currentRetry) через $delay) секунд...", level: .debug, category: .mainFlow) DispatchQueue.global().asyncAfter(deadline: .now() + delay) { attemptRequest() } } else { // No more retries left, call onError onError(error) } return } // Handle HTTP status errors (e.g., 4xx, 5xx) if let httpResponse = response as? HTTPURLResponse, !(200...299).contains(httpResponse.statusCode) { let httpError = NSError(domain: "NetworkService", code: httpResponse.statusCode, userInfo: [ NSLocalizedDescriptionKey: "HTTP error $httpResponse.statusCode)" ]) Logger.shared.log("❌ HTTP error: $httpResponse.statusCode)") onError(httpError) return } // Handle missing data guard let data = data else { let noDataError = NSError(domain: "NetworkService", code: -1, userInfo: [ NSLocalizedDescriptionKey: "No data received from tracker" ]) onError(noDataError) return } // Attempt to decode the response do { let location = try JSONDecoder().decode(NetworkInfo.self, from: data) Logger.shared.log("⏱️ [Tracker] Location from tracker: ⦗ $location.country) ⦘", level: .debug, category: .mainFlow) DispatchQueue.main.async { onComplete(location) } } catch { Logger.shared.log("❌ Decode error: $error)", level: .error) onError(error) } }.resume() } // Start the first attempt attemptRequest() }
📝 Key Features of This Implementation
- Retry Delays: Uses a list
[10, 15]to define the delay between retries. - Retry Count Management: Tracks the number of retries using
currentRetry. - Asynchronous Retry Scheduling: Uses
DispatchQueue.global().asyncAfterto delay each retry. - Preserved Logging: Maintains detailed logs for each attempt, including elapsed time and retry count.
- Clear Separation of Error Types:
- Network errors trigger retries.
- HTTP errors and decoding errors do not trigger retries and immediately call
onError.
🧪 Example of Behavior
Attempt Delay Outcome 1st 0s Network error → retry after 10s 2nd 10s Network error → retry after 15s 3rd 15s Network error → call onError
✅ Summary
This updated function introduces a robust retry mechanism that:
- Waits 10 seconds after the first failure.
- Waits 15 seconds after the second failure.
- Only fails permanently after both retries have been exhausted.
- Logs all attempts and delays clearly for debugging and monitoring.
This approach ensures reliability while maintaining clarity and control over the retry process.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.