ios - Container App Crashing: More Information Needed from Crashlytics -
the development team work has produced container app serves client's mobile site. can see container app crashing on ios 10 don't have information cause of problem. stack trace doesn't point other possible issue webkit , js core:
crashed: com.apple.main-thread 0 webkit 0x19673fddc api::object::ref() + 2 1 webkit 0x1968bb35c webkit::webpageproxy::didstartprovisionalloadforframe(unsigned long long, unsigned long long, wtf::string const&, wtf::string const&, webkit::userdata const&) + 192 2 webkit 0x1968d621c void ipc::handlemessage<messages::webpageproxy::didstartprovisionalloadforframe, webkit::webpageproxy, void (webkit::webpageproxy::*)(unsigned long long, unsigned long long, wtf::string const&, wtf::string const&, webkit::userdata const&)>(ipc::messagedecoder&, webkit::webpageproxy*, void (webkit::webpageproxy::*)(unsigned long long, unsigned long long, wtf::string const&, wtf::string const&, webkit::userdata const&)) + 100 3 webkit 0x1967941d0 ipc::messagereceivermap::dispatchmessage(ipc::connection&, ipc::messagedecoder&) + 120 4 webkit 0x196917614 webkit::webprocessproxy::didreceivemessage(ipc::connection&, ipc::messagedecoder&) + 32 5 webkit 0x19675d3e8 ipc::connection::dispatchmessage(std::__1::unique_ptr<ipc::messagedecoder, std::__1::default_delete<ipc::messagedecoder> >) + 160 6 webkit 0x19675fa00 ipc::connection::dispatchonemessage() + 204 7 javascriptcore 0x191b4c834 wtf::runloop::performwork() + 172 8 javascriptcore 0x191b4ca60 wtf::runloop::performwork(void*) + 36 9 corefoundation 0x18d332b5c __cfrunloop_is_calling_out_to_a_source0_perform_function__ + 24 10 corefoundation 0x18d3324a4 __cfrunloopdosources0 + 524 11 corefoundation 0x18d3300a4 __cfrunlooprun + 804 12 corefoundation 0x18d25e2b8 cfrunlooprunspecific + 444 13 graphicsservices 0x18ed12198 gseventrunmodal + 180 14 uikit 0x1932a57fc -[uiapplication _run] + 684 15 uikit 0x1932a0534 uiapplicationmain + 208 16 betfred 0x10005c250 main (main.m:16) 17 libdispatch.dylib 0x18c2415b8 (missing) nobody internal has been able app crash reliably (including test team using around clock) , far know, there no issues mobile site.
i've been asked issue @ bit of loss can't diagnose , fix if can't consistently break.
is there way more information crashlytics cause of crash?
mike fabric here , crashes can tough track down. you'd need release new version of app, there 3 different ways additional information.
1) add custom keys, example track pages being loaded or endpoints being hit, can provide additional context:
- (void)setobjectvalue:(id)value forkey:(nsstring *)key; // calls -description on value, perfect nsstrings! - (void)setintvalue:(int)value forkey:(nsstring *)key; - (void)setboolvalue:(bool)value forkey:(nsstring *)key; - (void)setfloatvalue:(float)value forkey:(nsstring *)key; 2) add custom logs form of breadcrumbs make easier reproduce steps user doing in lead-up crash:
cls_log(@"user clicked on menu %@", attributesdict); 3) add user identifiers:
[crashlyticskit setuseridentifier:@"123456789"]; [crashlyticskit setuseremail:@"person@domain.com"]; [crashlyticskit setusername:@"awesome appuser"]; when else fails, reaching out user additional information can track down.
Comments
Post a Comment