ios - Iphone application works fine on simulator but crashes on actual devise -


my application works on simulator , doesn't show warning or error in console when test application on actual device crashes when start application. have local notification service enabled. storing large image file server local database when first view loads. tried launch application without storing images also,still not working.

following crash report getting. let me know if knows it. in advance.

incident identifier: b92ec717-8391-4f9a-8c34-3cf9aa2e697c  crashreporter key:   e06a9cfad6f483253b1278ac34a2f38ab1b5cd18  hardware model:      iphone7,2  process:             timestamp [268]  path:                /private/var/mobile/containers/bundle/application/e87aee22-e2d8-407f-bda4-ea626d287c98/timestamp.app/timestamp  identifier:          sg.timestamp  version:             1 (1.0)  code type:           arm-64 (native)  parent process:      launchd [1]  date/time:           2015-10-02 10:44:13.13 +0530 launch time:         2015-10-02 10:44:13.13 +0530 os version:          ios 9.0.2 (13a452) report version:      105  exception type:  exc_crash (sigabrt) exception codes: 0x0000000000000000, 0x0000000000000000 exception note:  exc_corpse_notify triggered thread:  0  filtered syslog: none found  last exception backtrace:  0   corefoundation                  0x185544f5c 0x185420000 + 1199964  1   libobjc.a.dylib                 0x19a13bf80 0x19a134000 + 32640  2   corefoundation                  0x185544ea4 0x185420000 + 1199780  3   foundation                      0x1863b6a0c 0x186390000 + 158220  4   timestamp                       0x100049890 -[appdelegate copyandpaste] (appdelegate.m:104)  5   timestamp                       0x100048f2c -[appdelegate application:didfinishlaunchingwithoptions:] (appdelegate.m:21)  6   uikit                           0x18ab0f184 0x18aa88000 + 553348  7   uikit                           0x18ad37e60 0x18aa88000 + 2817632  8   uikit                           0x18ad3c1a4 0x18aa88000 + 2834852  9   uikit                           0x18ad392e4 0x18aa88000 + 2822884  10  frontboardservices              0x18f28b7ec 0x18f264000 + 161772  11  frontboardservices              0x18f28bb6c 0x18f264000 + 162668  12  corefoundation                  0x1854fc5a4 0x185420000 + 902564  13  corefoundation                  0x1854fc038 0x185420000 + 901176  14  corefoundation                  0x1854f9d38 0x185420000 + 892216  15  corefoundation                  0x185428dc0 0x185420000 + 36288  16  uikit                           0x18ab080ac 0x18aa88000 + 524460  17  uikit                           0x18ab02f44 0x18aa88000 + 503620  18  timestamp                       0x100050220 main (main.m:14)  19  libdyld.dylib                   0x19a9668b8 0x19a964000 + 10424  thread 0 name:  dispatch queue: com.apple.main-thread thread 0 crashed:  0   libsystem_kernel.dylib          0x000000019aa831e0 0x19aa68000 + 111072  1   libsystem_pthread.dylib         0x000000019ab4cf0c 0x19ab48000 + 20236  2   libsystem_c.dylib               0x000000019a9f6b78 0x19a994000 + 404344  3   libc++abi.dylib                 0x00000001997b93f4 0x1997b8000 + 5108  4   libc++abi.dylib                 0x00000001997d5e98 0x1997b8000 + 122520  5   libobjc.a.dylib                 0x000000019a13c248 0x19a134000 + 33352  6   libc++abi.dylib                 0x00000001997d2f44 0x1997b8000 + 110404  7   libc++abi.dylib                 0x00000001997d2b10 0x1997b8000 + 109328  8   libobjc.a.dylib                 0x000000019a13c120 0x19a134000 + 33056  9   corefoundation                  0x0000000185428e68 0x185420000 + 36456  10  uikit                           0x000000018ab080ac 0x18aa88000 + 524460  11  uikit                           0x000000018ab02f44 0x18aa88000 + 503620  12  timestamp                       0x0000000100050220 main (main.m:14)  13  libdyld.dylib                   0x000000019a9668b8 0x19a964000 + 10424  thread 1 name:  dispatch queue: com.apple.libdispatch-manager  thread 1:  0   libsystem_kernel.dylib          0x000000019aa8459c 0x19aa68000 + 116124  1   libdispatch.dylib               0x000000019a948a04 0x19a934000 + 84484  2   libdispatch.dylib               0x000000019a93793c 0x19a934000 + 14652   thread 2 name:  dispatch queue: axbinarymonitorqueue  thread 2:  0   libsystem_kernel.dylib          0x000000019aa68c6c 0x19aa68000 + 3180  1   libsystem_platform.dylib        0x000000019ab4297c 0x19ab40000 + 10620  2   libdispatch.dylib               0x000000019a940614 0x19a934000 + 50708  3   accessibilityutilities          0x000000018bfe6648 0x18bfc0000 + 157256  4   libdispatch.dylib               0x000000019a9357b0 0x19a934000 + 6064  5   libdispatch.dylib               0x000000019a935770 0x19a934000 + 6000  6   libdispatch.dylib               0x000000019a94175c 0x19a934000 + 55132  7   libdispatch.dylib               0x000000019a939274 0x19a934000 + 21108  8   libdispatch.dylib               0x000000019a935770 0x19a934000 + 6000  9   libdispatch.dylib               0x000000019a943bb0 0x19a934000 + 64432  10  libdispatch.dylib               0x000000019a94334c 0x19a934000 + 62284  11  libsystem_pthread.dylib         0x000000019ab49478 0x19ab48000 + 5240  12  libsystem_pthread.dylib         0x000000019ab49028 0x19ab48000 + 4136  thread 3:  0   libsystem_kernel.dylib          0x000000019aa83c0c 0x19aa68000 + 113676  1   libsystem_pthread.dylib         0x000000019ab49538 0x19ab48000 + 5432  2   libsystem_pthread.dylib         0x000000019ab49028 0x19ab48000 + 4136  thread 4:  0   libsystem_kernel.dylib          0x000000019aa83c0c 0x19aa68000 + 113676  1   libsystem_pthread.dylib         0x000000019ab49538 0x19ab48000 + 5432  2   libsystem_pthread.dylib         0x000000019ab49028 0x19ab48000 + 4136  thread 5:  0   libsystem_kernel.dylib          0x000000019aa83c0c 0x19aa68000 + 113676  1   libsystem_pthread.dylib         0x000000019ab49538 0x19ab48000 + 5432  2   libsystem_pthread.dylib         0x000000019ab49028 0x19ab48000 + 4136  thread 6:  0   libsystem_kernel.dylib          0x000000019aa83c0c 0x19aa68000 + 113676  1   libsystem_pthread.dylib         0x000000019ab49538 0x19ab48000 + 5432  2   libsystem_pthread.dylib         0x000000019ab49028 0x19ab48000 + 4136  thread 0 crashed arm thread state (64-bit):     x0: 0x0000000000000000   x1: 0x0000000000000000   x2: 0x0000000000000000   x3: 0x0000000147666967     x4: 0x00000001997d6e02   x5: 0x000000016fdd3530   x6: 0x000000000000006e   x7: 0x0000000000000f80     x8: 0x0000000008000000   x9: 0x0000000004000000  x10: 0x0000000000000002  x11: 0x0000000000000010    x12: 0x0000000000000000  x13: 0x0000000000000002  x14: 0x0000000000000000  x15: 0x0000030000000300    x16: 0x0000000000000148  x17: 0x0000000000000000  x18: 0x0000000000000000  x19: 0x0000000000000006    x20: 0x00000001a13ee000  x21: 0x000000016fdd3530  x22: 0x0000000147619a60  x23: 0x00000001a13f9b68    x24: 0x0000000000000001  x25: 0xcf00ec12820beef7  x26: 0x0000000147608640  x27: 0x0000000000000000    x28: 0x0000000000000001  fp: 0x000000016fdd3490   lr: 0x000000019ab4cf0c     sp: 0x000000016fdd3470   pc: 0x000000019aa831e0 cpsr: 0x00000000  binary images ->  there lot of data think might not of use.   -(void)copyandpaste   {      nsarray *arrpath=nssearchpathfordirectoriesindomains(nsdocumentdirectory, nsuserdomainmask, yes);      nsstring *str=[arrpath objectatindex:0];      self.strdbpath=[str stringbyappendingpathcomponent:@"time.db"];      nslog(@"%@",self.strdbpath);      if(![[nsfilemanager defaultmanager]fileexistsatpath:self.strdbpath]) {         nsstring *localdb=[[nsstring alloc]initwithstring:[[nsbundle mainbundle]pathforresource:@"time" oftype:@"db"]];          [[nsfilemanager defaultmanager]copyitematpath:localdb topath:self.strdbpath error:nil];     } }

you're trying store large image file server during application launch. based on code, you're trying synchronously on main thread. if block main thread significant amount of time, user interface becomes unacceptably unresponsive. in order keep user interface responsive, ios includes watchdog mechanism. if application fails respond user interface events (launch, suspend, resume, terminate) in time, watchdog kill application. resolve issue i'd call copyandpaste asynchronously:

dispatch_async(dispatch_get_global_queue( dispatch_queue_priority_default, 0), ^(void){         copyandpaste();     });

Comments

Post a Comment

Popular posts from this blog

resizing Telegram inline keyboard -

telegram's inline keyboard great feature lots of different use cases. inline buttons added list of items this: inline_keyboard = [[inlinekeyboardbutton(text="button", callback_data="button"), inlinekeyboardbutton(text="reset",callback_data="reset")]] inline_keyboard_markup = inlinekeyboardmarkup(inline_keyboard) update.message.reply_text("hi", reply_markup=inline_keyboard_markup) the above code adds 2 buttons each half width of chat screen. i know the normal keyboard button there resize_keyboard parameter somehow can used. my question is there way resize inline buttons ? example make full width or quarter width. unfortunately, can't now. :( you can suggest @botsupport , might add feature next version.
Read more

command line - How can a Python program background itself? -

consider following python command-line program. doesn't work because incomplete, think illustrates problem: #!/usr/bin/python3 import multiprocessing pool = multiprocessing.pool() task in expensive_iterator_with_user_interaction(): pool.call_async(expensive_computation, (task,)) pool.close() print("dear user, may press ctrl-z , bg script.") pool.join() thus, problem scripts needs user input while it's launching expensive parallel processes. there moment when user interaction not needed anymore. then, ask user background process shell actions. however, can achieved program itself? (side note: core of problem entanglement of user input firing “expensive computations”. therefore, cannot separate both in 2 scripts, , letting 1 spawning other daemon.) the command screen may you. use screen -l create new session , run application. after inputting data, can press " ctrl-a " , press " d " on keyboard detach session. now...
Read more

php - "cURL error 28: Resolving timed out" on Wordpress on Azure App Service on Linux -

Image
my wordpress installation on azure app service on linux using custom docker container has slow response times. pages take around 20-40 seconds load. i have troubleshooting plugin installed indicates problem "curl error 28: resolving timed out after n milliseconds" when making requests following urls https://api.wordpress.org/core/version-check/1.7/ http://api.wordpress.org/core/version-check/1.7/ https://api.wordpress.org/plugins/update-check/1.1/ http://api.wordpress.org/plugins/update-check/1.1/ https://api.wordpress.org/themes/update-check/1.1/ http://api.wordpress.org/themes/update-check/1.1/ curl works fine on scm-site command line. example works ok. curl -x post http://api.wordpress.org/core/version-check/1.7/ edit if ssh container , run php code, works fine. <?php $url = 'http://api.wordpress.org/core/version-check/1.7/'; $fields = array( 'version' => urlencode('4.8.1'), 'php' => urlencode(...
Read more