Closed dipendrapulse closed 5 years ago
If you want send something after application goes to background you can use background Task https://developer.apple.com/documentation/uikit/core_app/managing_your_app_s_life_cycle/preparing_your_app_to_run_in_the_background/extending_your_app_s_background_execution_time
Dear @dipendrapulse
Could you confirm that the solution from our developer is suitable for you?
The status of the ticket changed to "Closed", the solution has been provided. If this issue is still actual for you - please reopen the ticket.
New Issue Checklist
Environment details
Did this work before? No
Expected behavior It should allow user to send message
Actual behavior I get error to response failed 1002
Logs
Please use the following template for logs:
To enable full logs use the following code:
Title for logs
```logos // Your logs here 2018-09-14 18:06:51.961317+0530 Leafpon[16752:128500] [MC] Reading from private effective user settings. 2018-09-14 18:06:51.997846+0530 Leafpon[16752:128500] [Crashlytics] Version 3.10.1 (129) 2018-09-14 18:06:52.126114+0530 Leafpon[16752:128500] Init - QMAuthService service... 2018-09-14 18:06:52.126899+0530 Leafpon[16752:128500] Init - QMChatService service... 2018-09-14 18:06:52.127378+0530 Leafpon[16752:128500] Init - QMDeferredQueueManager service... 2018-09-14 18:06:52.149787+0530 Leafpon[16752:128500] Init - QMUsersService service... 2018-09-14 18:06:52.153257+0530 Leafpon[16752:128576] [QBCore]: Request[1]: POST URL:https://api.quickblox.com/login.json headers: { "Accept-Language" = "en;q=1"; "Content-Type" = "application/x-www-form-urlencoded"; "QB-OS" = "iOS 11.4"; "QB-SDK" = "iOS 2.16"; "QB-Token" = e1530e5ec2f4ec8a675224a4c5ec97bc120109ea; "QuickBlox-REST-API-Version" = "0.1.1"; "User-Agent" = "Leafpon/1.0 (iPhone; iOS 11.4; Scale/2.00)"; } parameters: { email = "dipendra.dubey@******"; password = ********; } 2018-09-14 18:06:52.299939+0530 Leafpon[16752:128500] Could not successfully update network info during initialization. 2018-09-14 18:06:52.703025+0530 Leafpon[16752:128576] TIC Read Status [3:0x0]: 1:57 2018-09-14 18:06:52.703207+0530 Leafpon[16752:128576] TIC Read Status [3:0x0]: 1:57 2018-09-14 18:06:52.703752+0530 Leafpon[16752:128576] TIC Read Status [3:0x0]: 1:57 2018-09-14 18:06:52.704010+0530 Leafpon[16752:128576] TIC Read Status [3:0x0]: 1:57 2018-09-14 18:06:53.947927+0530 Leafpon[16752:128576] [QBCore]: Response[1]: headers: { "Access-Control-Allow-Origin" = "*"; "Cache-Control" = "no-cache"; Connection = "keep-alive"; "Content-Length" = 375; "Content-Type" = "application/json; charset=utf-8"; Date = "Fri, 14 Sep 2018 12:36:53 GMT"; Duration = "1.794239"; "QB-Token-ExpirationDate" = "2018-09-14 14:36:34 +0000"; "QuickBlox-REST-API-Version" = "0.1.1"; Server = "nginx/1.8.1"; "Set-Cookie" = "_mkra_ctxt=b2d803caedb431393c766612b798fcfa--202; path=/; max-age=5; HttpOnly; secure"; Status = "202 Accepted"; "Strict-Transport-Security" = "max-age=31536000"; "X-Content-Type-Options" = nosniff; "X-Frame-Options" = SAMEORIGIN; "X-Request-Id" = "4035aee5-d8ab-4481-bd33-3cf6c1f2718b"; "X-Runtime" = "0.020334"; "X-XSS-Protection" = "1; mode=block"; } object: { user = { "blob_id" = 9115202; "created_at" = "2018-07-13T13:51:55Z"; "custom_data" = "Steps to reproduce the behavior
Any others comments I have added below methods too
(void)applicationDidEnterBackground:(UIApplication *)application { // Use this method to release shared resources, save user data, invalidate timers, and store enough application state information to restore your application to its current state in case it is terminated later. // If your application supports background execution, this method is called instead of applicationWillTerminate: when the user quits.
// Logout from chat [ServicesManager.instance.chatService disconnectWithCompletionBlock:nil]; }
(void)applicationWillEnterForeground:(UIApplication *)application { // Called as part of the transition from the background to the active state; here you can undo many of the changes made on entering the background.
// Login to QuickBlox Chat // [ServicesManager.instance.chatService connectWithCompletionBlock:nil];
}