Skip to content

App crashes on launch on physical iOS 14 device in debug mode when debugger not attached, EXC_BAD_ACCESS (SIGKILL - CODESIGNING) #60657

Closed
Closed
App crashes on launch on physical iOS 14 device in debug mode when debugger not attached, EXC_BAD_ACCESS (SIGKILL - CODESIGNING)#60657
Labels
P1High-priority issues at the top of the work lista: annoyanceRepeatedly frustrating issues with non-experimental functionalitya: existing-appsIntegration with existing apps via the add-to-app flowc: fatal crashCrashes that terminate the processcustomer: alibabadependency: dartDart team may need to help use: OS-version specificAffects only some versions of the relevant operating systemfound in release: 1.20Found to occur in 1.20has reproducible stepsThe issue has been confirmed reproducible and is ready to work onplatform-iosiOS applications specificallyt: xcode"xcodebuild" on iOS and general Xcode project managementtoolAffects the "flutter" command-line tool. See also t: labels.

Description

@PhantomRay
PhantomRay
opened on Jul 1, 2020

As requested by @jmagman, I create this separate issue from #60424.

Steps to Reproduce

  1. run app from flutter run or Xcode 12
  2. disconnect app from debug session
  3. crash when re-launch app

Note: running app in simulator does not have above issue.

Logs

As it says, codesigning issue. This may not be a flutter issue though.

default	11:54:20.373960+1000	ReportCrash	Sending event: com.apple.stability.crash {"appVersion":"1.0.0","bundleID":"com.example.myapp","exceptionCodes":"UNKNOWN_0x32 at 0x000000010bc01d60","incidentID":"083FA319-562B-4503-987F-1765A445BEE2","logwritten":1,"process":"Runner","terminationReasonExceptionCode":"0x2","terminationReasonNamespace":"CODESIGNING"}
Full logs 
default	11:54:19.756942+1000	SpringBoard	Creating process for executionContext with identity: application<com.example.myapp>
default	11:54:19.757433+1000	SpringBoard	Created <FBWorkspace: 0x28341caa0; application<com.example.myapp>>
default	11:54:19.757483+1000	SpringBoard	Bootstrapping application<com.example.myapp> with intent foreground-interactive
default	11:54:19.765821+1000	SpringBoard	Not creating a new process because one already exists with identity: application<com.example.myapp>
default	11:54:19.769861+1000	runningboardd	Acquiring assertion targeting application<com.example.myapp> from originator [daemon<com.apple.SpringBoard>:59] with description <RBSAssertionDescriptor| "FBApplicationProcess" ID:32-59-52435 target:application<com.example.myapp> attributes:[
	<RBSRunningReasonAttribute| runningReason:10000>,
	<RBSPreventIdleSleepGrant>,
	<RBSDefineRelativeStartTimeGrant>,
	<RBSGPUAccessGrant>,
	<RBSCPUAccessGrant| role:UserInteractiveNonFocal>,
	<RBSJetsamPriorityGrant| priority:Foreground>,
	<RBSResistTerminationGrant| terminationResistance:Interactive>,
	<RBSEndowmentGrant| namespace:com.apple.frontboard.visibility>
	]>
default	11:54:19.771965+1000	runningboardd	Assertion 32-59-52435 (target:application<com.example.myapp>) will be created as active
default	11:54:19.772631+1000	runningboardd	Executing launch request for application<com.example.myapp> (FBApplicationProcess)
default	11:54:19.773417+1000	runningboardd	Creating and launching job for: application<com.example.myapp>
default	11:54:19.774410+1000	runningboardd	_mutateContextIfNeeded called for com.example.myapp
default	11:54:19.776060+1000	runningboardd	Inserting mach service com.example.myapp.gsEvents into job for application<com.example.myapp>
default	11:54:19.781193+1000	runningboardd	[application<com.example.myapp>:3419] This process will be managed.
default	11:54:19.781265+1000	runningboardd	Now tracking process: [application<com.example.myapp>:3419]
default	11:54:19.781339+1000	runningboardd	Using default underlying assertion for app: [application<com.example.myapp>:3419]
default	11:54:19.781390+1000	runningboardd	Calculated state for application<com.example.myapp>: running-active (role: UserInteractiveNonFocal)
default	11:54:19.781444+1000	runningboardd	Acquiring assertion targeting application<com.example.myapp> from originator [application<com.example.myapp>:3419] with description <RBSAssertionDescriptor| "RB Underlying Assertion" ID:32-32-52436 target:3419 attributes:[
	<RBSDomainAttribute| domain:"com.apple.underlying" name:"defaultUnderlyingAppAssertion" sourceEnvironment:"(null)">,
	<RBSAcquisitionCompletionAttribute| policy:AfterApplication>
	]>
default	11:54:19.781644+1000	runningboardd	Assertion 32-32-52436 (target:application<com.example.myapp>) will be created as active
default	11:54:19.783833+1000	runningboardd	Calculated state for application<com.example.myapp>: running-active (role: UserInteractiveNonFocal)
default	11:54:19.784653+1000	runningboardd	[application<com.example.myapp>:3419] Set jetsam priority to 10 [0] flag[1]
default	11:54:19.785660+1000	SpringBoard	[application<com.example.myapp>:3419] Bootstrap success!
default	11:54:19.785754+1000	runningboardd	[application<com.example.myapp>:3419] Resuming task.
default	11:54:19.785790+1000	runningboardd	Attempting to rename power assertion 41361 for target application<com.example.myapp> to application<com.example.myapp>;(null):(null);32-59-52435:FBApplicationProcess
default	11:54:19.786365+1000	SpringBoard	Hit the server for a process handle 36ce7daf00000d5b that resolved to: [application<com.example.myapp>:3419]
default	11:54:19.786634+1000	SpringBoard	Hit the server for a process handle 36ce7daf00000d5b that resolved to: [application<com.example.myapp>:3419]
default	11:54:19.786792+1000	SpringBoard	[application<com.example.myapp>:3419] Setting process task state to: Running
default	11:54:19.786842+1000	SpringBoard	[application<com.example.myapp>:3419] Setting process visibility to: Foreground
default	11:54:19.786901+1000	SpringBoard	change foreground process from list:<FBApplicationProcess: 0x159556a10; application<com.example.myapp>:3419(v26F3)>
default	11:54:19.787100+1000	SpringBoard	didSelectKeyboardFocusProcess:<FBApplicationProcess: 0x159556a10; application<com.example.myapp>:3419(v26F3)> token:(null)
default	11:54:19.787414+1000	SpringBoard	[application<com.example.myapp>:3419] Registering event dispatcher at connect
default	11:54:19.788208+1000	runningboardd	[application<com.example.myapp>:3419] Set darwin role to: UserInteractiveNonFocal
default	11:54:19.789948+1000	SpringBoard	Adding: <FBApplicationProcess: 0x159556a10; application<com.example.myapp>:3419(v26F3)>
default	11:54:19.794754+1000	runningboardd	[application<com.example.myapp>:3419] Set GPU priority to "allow"
default	11:54:19.800914+1000	runningboardd	[application<com.example.myapp>:3419] reported to RB as running
default	11:54:19.801414+1000	runningboardd	Finished acquiring assertion 32-32-52436 (target:application<com.example.myapp>)
default	11:54:19.811414+1000	mediaserverd	Hit the server for a process handle 36ce7daf00000d5b that resolved to: [application<com.example.myapp>:3419]
default	11:54:19.811703+1000	mediaserverd	-CMSessionMgr- CMSessionMgrHandleApplicationStateChange: Client com.example.myapp with pid '3419' is now Foreground Running. Background entitlement: NO ActiveLongFormVideoSession: NO WhitelistedLongFormVideoApp NO
default	11:54:19.811795+1000	mediaserverd	-CMSessionMgr- CMSessionMgrHandleApplicationStateChange: Sending EndInterruption to com.example.myapp with pid '3419' because client moved to ForegroundRunning and is not allowed to play in the background
default	11:54:19.812074+1000	SpringBoard	[application<com.example.myapp>:3419] Registered new scene: <FBUIApplicationWorkspaceScene: 0x2835063c0; sceneID:com.example.myapp-default> (fromRemnant = 0)
default	11:54:19.812108+1000	SpringBoard	[application<com.example.myapp>:3419] Workspace interruption policy did change: terminate
default	11:54:19.812175+1000	SpringBoard	Now tracking: <FBScene: 0x283528370; sceneID: sceneID:com.example.myapp-default; valid: YES>
default	11:54:19.812242+1000	SpringBoard	[sceneID:com.example.myapp-default] Setting deactivation reasons to: 'systemAnimation' for reason: scene settings update - settings are eligible for deactivation reasons.
default	11:54:19.812338+1000	runningboardd	Successfully acquired underlying assertion for [application<com.example.myapp>:3419]
default	11:54:19.812371+1000	runningboardd	Finished acquiring assertion 32-59-52435 (target:application<com.example.myapp>)
default	11:54:19.813278+1000	runningboardd	Acquiring assertion targeting application<com.example.myapp> from originator [daemon<com.apple.SpringBoard>:59] with description <RBSAssertionDescriptor| "com.apple.frontboard.after-life.subordinate" ID:32-59-52437 target:3419 attributes:[
	<RBSSubordinateProcessAttribute>
	]>
default	11:54:19.813309+1000	runningboardd	Assertion 32-59-52437 (target:application<com.example.myapp>) will be created as active
default	11:54:19.814059+1000	SpringBoard	[sceneID:com.example.myapp-default] Scene lifecycle state did change: Foreground
default	11:54:19.814155+1000	SpringBoard	[sceneID:com.example.myapp-default] Scene assertion state did change: ForegroundActive.
default	11:54:19.816709+1000	runningboardd	Calculated state for application<com.example.myapp>: running-active (role: UserInteractiveNonFocal)
default	11:54:19.817979+1000	backboardd	Connection added: IOHIDEventSystemConnection uuid:5E0856B5-038D-4DD6-9273-3EF87DA46F6E pid:3419 process:Runner type:Passive entitlements:0x0 caller:BackBoardServices: <redacted> + 288 attributes:{
    HighFrequency = 1;
    bundleID = "com.example.myapp";
    pid = 3419;
} state:0x0 events:0 mask:0x0
default	11:54:19.819499+1000	runningboardd	Finished acquiring assertion 32-59-52437 (target:application<com.example.myapp>)
default	11:54:19.819864+1000	SpringBoard	Connection established for <FBApplicationProcess: 0x159556a10; application<com.example.myapp>:3419(v26F3)>
default	11:54:19.819926+1000	SpringBoard	[application<com.example.myapp>:3419] Connection to remote process established!
default	11:54:19.821162+1000	SpringBoard	[application<com.example.myapp>:3419] Workspace assertion state did change: ForegroundActive.
default	11:54:19.822325+1000	runningboardd	Setting client for [application<com.example.myapp>:3419] as ready
default	11:54:19.822643+1000	runningboardd	Acquiring assertion targeting application<com.example.myapp> from originator [daemon<com.apple.SpringBoard>:59] with description <RBSAssertionDescriptor| "FBWorkspace (ForegroundActive)" ID:32-59-52438 target:3419 attributes:[
	<RBSRunningReasonAttribute| runningReason:10000>,
	<RBSDefineRelativeStartTimeGrant>,
	<RBSGPUAccessGrant>,
	<RBSCPUAccessGrant| role:UserInteractiveNonFocal>,
	<RBSJetsamPriorityGrant| priority:Foreground>,
	<RBSResistTerminationGrant| terminationResistance:Interactive>,
	<RBSEndowmentGrant| namespace:com.apple.frontboard.visibility>,
	<RBSAcquisitionCompletionAttribute| policy:AfterApplication>
	]>
default	11:54:19.823328+1000	Runner	Identity resolved as application<com.example.myapp>
default	11:54:19.823359+1000	runningboardd	Assertion 32-59-52438 (target:application<com.example.myapp>) will be created as active
default	11:54:19.827034+1000	SpringBoard	[sceneID:com.example.myapp-default] Sending scene action [Logical Activate][0xce39] to process 0x159556a10
default	11:54:19.831024+1000	powerd	Process runningboardd.32 Created SystemIsActive "application<com.example.myapp>(null):(null)" age:00:00:00  id:51539648913 [System: PrevIdle SysAct]
default	11:54:19.831656+1000	runningboardd	Finished acquiring assertion 32-59-52438 (target:application<com.example.myapp>)
default	11:54:19.831754+1000	runningboardd	Calculated state for application<com.example.myapp>: running-active (role: UserInteractiveNonFocal)
default	11:54:19.833244+1000	mediaserverd	<<<< FigCaptureDisplayLayoutMonitor >>>> -[FigCaptureDisplayLayoutMonitor _updateCurrentLayout:]: <FBSDisplayLayout: 0x10ece0470; displayIdentity: Main> {    bounds = {{0, 0}, {414, 896}};    interfaceOrientation = "portrait (1)";    backlightLevel = 100;    elements = {        <SBSDisplayLayoutElement: 0x109cdc760; identifier: com.apple.springboard.app-library; frame: {{0, 0}, {414, 896}}; level: 0; role: fullScreenModal>;        <SBSDisplayLayoutElement: 0x109cefc80; bundleID: com.example.myapp; identifier: sceneID:com.example.myapp-default; frame: {{0, 0}, {414, 896}}; level: 1; role: primary>;    }    timestamp = 1 July 2020 at 11:54:19 am AEST;}
default	11:54:19.836154+1000	SpringBoard	Updating configuration of monitor <RBSProcessMonitorConfiguration| id:M59-6 qos:25 predicates:[<RBSProcessPredicate <RBSCompoundPredicate [<RBSCompoundPredicate [<RBSProcessBKSLegacyPredicate>, <RBSProcessEUIDPredicate 501>]>, <RBSProcessBundleIdentifierPredicate "com.apple.springboard">]>>, <RBSProcessPredicate <RBSCompoundPredicate [<RBSCompoundPredicate [<RBSProcessBKSLegacyPredicate>, <RBSProcessEUIDPredicate 501>]>, <RBSProcessBundleIdentifierPredicate "com.apple.ios.StoreKitUIService">]>>, <RBSProcessPredicate <RBSCompoundPredicate [<RBSCompoundPredicate [<RBSProcessBKSLegacyPredicate>, <RBSProcessEUIDPredicate 501>]>, <RBSProcessBundleIdentifierPredicate "com.apple.AppStore.ProductPageExtension">]>>, <RBSProcessPredicate <RBSCompoundPredicate [<RBSCompoundPredicate [<RBSProcessBKSLegacyPredicate>, <RBSProcessEUIDPredicate 501>]>, <RBSProcessBundleIdentifierPredicate "com.example.myapp">]>>] descriptor:<RBSProcessStateDescriptor| values:9 namespaces:[com.apple.frontboard.visibility]> events:0x0>
default	11:54:19.915011+1000	SpringBoard	[com.example.myapp] com.example.myapp application state changed to ForegroundRunning
default	11:54:19.915112+1000	SpringBoard	[com.example.myapp] Ignore becoming foreground for application without push registration
default	11:54:19.918096+1000	SpringBoard	Application process state changed for com.example.myapp: <SBApplicationProcessState: 0x28063c080; pid: 3419; taskState: Running; visibility: Foreground>
default	11:54:19.920974+1000	SpringBoard	Application process state changed for com.example.myapp: <SBApplicationProcessState: 0x2806339e0; pid: 3419; taskState: Running; visibility: Foreground>
default	11:54:19.940825+1000	SpringBoard	[sceneID:com.example.myapp-default] Scene action [Logical Activate][0xce39] completed with success: 0
default	11:54:19.941544+1000	backboardd	Connection removed: IOHIDEventSystemConnection uuid:5E0856B5-038D-4DD6-9273-3EF87DA46F6E pid:3419 process:Runner type:Passive entitlements:0x0 caller:BackBoardServices: <redacted> + 288 attributes:{
    HighFrequency = 1;
    bundleID = "com.example.myapp";
    pid = 3419;
} state:0x1 events:0 mask:0x0
default	11:54:19.941585+1000	SpringBoard	Workspace connection invalidated for <FBApplicationProcess: 0x159556a10; application<com.example.myapp>:3419(v26F3)>
default	11:54:19.941618+1000	SpringBoard	[application<com.example.myapp>:3419] Now flagged as pending exit for reason: workspace client connection invalidated
default	11:54:19.943240+1000	runningboardd	Acquiring assertion targeting application<com.example.myapp>(UIScene:com.apple.frontboard.systemappservices::sceneID%3Acom.example.myapp-default) from originator [daemon<com.apple.SpringBoard>:59] with description <RBSAssertionDescriptor| "injecting inherited from "UIScene:com.apple.frontboard.systemappservices::com.apple.springboard" to 3419<UIScene:com.apple.frontboard.systemappservices::sceneID%3Acom.example.myapp-default>" ID:32-59-52441 target:3419<UIScene:com.apple.frontboard.systemappservices::sceneID%3Acom.example.myapp-default> attributes:[
	<RBSHereditaryGrant| endowmentNamespace:com.apple.boardservices.endpoint-injection UIScene:com.apple.frontboard.systemappservices::com.apple.springboard>,
	<RBSHereditaryGrant| endowmentNamespace:com.apple.frontboard.visibility UIScene:com.apple.frontboard.systemappservices::com.apple.springboard>
	]>
default	11:54:19.943309+1000	runningboardd	Assertion 32-59-52441 (target:application<com.example.myapp>(UIScene:com.apple.frontboard.systemappservices::sceneID%3Acom.example.myapp-default)) will be created as active
default	11:54:19.947877+1000	runningboardd	Calculated state for application<com.example.myapp>: running-active (role: UserInteractiveNonFocal)
default	11:54:19.948082+1000	runningboardd	[application<com.example.myapp>:3419] termination reported by launchd (3, 2, 9)
default	11:54:19.950022+1000	runningboardd	Removing process: [application<com.example.myapp>:3419]
default	11:54:19.950954+1000	runningboardd	Removing launch job for: [application<com.example.myapp>:3419]
default	11:54:19.951054+1000	runningboardd	Finished acquiring assertion 32-59-52441 (target:application<com.example.myapp>(UIScene:com.apple.frontboard.systemappservices::sceneID%3Acom.example.myapp-default))
default	11:54:19.952106+1000	runningboardd	Removed job for [application<com.example.myapp>:3419]
default	11:54:19.977338+1000	runningboardd	Invalidating assertion 32-59-52441 (target:application<com.example.myapp>(UIScene:com.apple.frontboard.systemappservices::sceneID%3Acom.example.myapp-default)) from originator [daemon<com.apple.SpringBoard>:59]
default	11:54:19.977843+1000	runningboardd	Removing assertions for terminated process: [application<com.example.myapp>:3419]
default	11:54:19.979116+1000	runningboardd	Removed last relative-start-date-defining assertion for process application<com.example.myapp>
default	11:54:19.979871+1000	runningboardd	Calculated state for application<com.example.myapp>: none (role: None)
default	11:54:19.979959+1000	powerd	Process runningboardd.32 Released SystemIsActive "application<com.example.myapp>;(null):(null);32-59-52435:FBApplicationProcess" age:00:00:00  id:51539648913 [System: PrevIdle SysAct]
default	11:54:20.055140+1000	runningboardd	Acquiring assertion targeting 3419<UIScene:com.apple.frontboard.systemappservices::sceneID%3Acom.example.myapp-default> from originator [daemon<com.apple.SpringBoard>:59] with description <RBSAssertionDescriptor| "injecting inherited from "UIScene:com.apple.frontboard.systemappservices::com.apple.springboard" to 3419<UIScene:com.apple.frontboard.systemappservices::sceneID%3Acom.example.myapp-default>" ID:32-59-52443 target:3419<UIScene:com.apple.frontboard.systemappservices::sceneID%3Acom.example.myapp-default> attributes:[
	<RBSHereditaryGrant| endowmentNamespace:com.apple.boardservices.endpoint-injection UIScene:com.apple.frontboard.systemappservices::com.apple.springboard>,
	<RBSHereditaryGrant| endowmentNamespace:com.apple.frontboard.visibility UIScene:com.apple.frontboard.systemappservices::com.apple.springboard>
	]>
default	11:54:20.055471+1000	runningboardd	XPC connection invalidated: [application<com.example.myapp>:3419]
default	11:54:20.056109+1000	runningboardd	Calculated state for application<com.example.myapp>: none (role: None)
default	11:54:20.057902+1000	mediaserverd	-CMSessionMgr- CMSessionMgrHandleApplicationStateChange: Client com.example.myapp with pid '3419' is now Terminated. Background entitlement: NO ActiveLongFormVideoSession: NO WhitelistedLongFormVideoApp NO
default	11:54:20.059779+1000	SpringBoard	[application<com.example.myapp>:3419] Process exited: <RBSProcessExitContext| specific, status:<RBSProcessExitStatus| domain:codesigning(3) code:invalid-page(2)>>.
default	11:54:20.059813+1000	SpringBoard	[application<com.example.myapp>:3419] Setting process task state to: Not Running
default	11:54:20.059959+1000	SpringBoard	[application<com.example.myapp>:3419] Setting process visibility to: Unknown
default	11:54:20.060067+1000	SpringBoard	Removing: <FBApplicationProcess: 0x159556a10; application<com.example.myapp>:3419(v26F3)>
default	11:54:20.060142+1000	SpringBoard	[application<com.example.myapp>:3419] Invalidating all scenes.
default	11:54:20.060235+1000	SpringBoard	Removing workspace registration for processHandle: [application<com.example.myapp>:3419]
default	11:54:20.072379+1000	SpringBoard	Process exited: <FBApplicationProcess: 0x159556a10; application<com.example.myapp>:3419(v26F3)> -> <RBSProcessExitContext| specific, status:<RBSProcessExitStatus| domain:codesigning(3) code:invalid-page(2)>>
default	11:54:20.072926+1000	SpringBoard	Application process state changed for com.example.myapp: (null)
default	11:54:20.088958+1000	SpringBoard	No longer tracking: <FBScene: 0x283528370; sceneID: sceneID:com.example.myapp-default; valid: NO>
default	11:54:20.089761+1000	SpringBoard	[SBMainDisplaySceneManager sceneManager:didDestroyScene: <FBScene: 0x283528370; sceneID: sceneID:com.example.myapp-default; valid: NO>] - proposing IdleTimerBehavior.
default	11:54:20.112521+1000	backboardd	Hit the server for a process handle 36ce7daf00000d5b that resolved to: [application<com.example.myapp>:3419]
default	11:54:20.112601+1000	wifid	Hit the server for a process handle 36ce7daf00000d5b that resolved to: [application<com.example.myapp>:3419]
default	11:54:20.112739+1000	aggregated	Hit the server for a process handle 36ce7daf00000d5b that resolved to: [application<com.example.myapp>:3419]
default	11:54:20.113127+1000	UserEventAgent	Hit the server for a process handle 36ce7daf00000d5b that resolved to: [application<com.example.myapp>:3419]
default	11:54:20.113200+1000	SpringBoard	[com.example.myapp] com.example.myapp application state changed to Terminated
default	11:54:20.113248+1000	SpringBoard	[com.example.myapp] Ignore becoming background for application without push registration
default	11:54:20.113877+1000	locationd	Hit the server for a process handle 36ce7daf00000d5b that resolved to: [application<com.example.myapp>:3419]
default	11:54:20.115242+1000	locationd	{"msg":"#CLIUA Marking change", "clientKey":"com.example.myapp", "reason":"Process state from RunningBoard", "assertionLevel":4, "coming":1}
error	11:54:20.154315+1000	runningboardd	RBSStateCapture remove item called for untracked item 32-59-52441 (target:application<com.example.myapp>(UIScene:com.apple.frontboard.systemappservices::sceneID%3Acom.example.myapp-default))
default	11:54:20.164242+1000	SpringBoard	[com.example.myapp] Foreground app will not request ephemeral notifications isAppClip: NO wantsEphemeral notifications: NO
default	11:54:20.179373+1000	locationd	{"msg":"#CLIUA Marking change", "clientKey":"com.example.myapp", "reason":"Process state from RunningBoard", "assertionLevel":4, "coming":0}
default	11:54:20.221482+1000	contextstored	Hit the server for a process handle 36ce7daf00000d5b that resolved to: [application<com.example.myapp>:3419]
default	11:54:20.221647+1000	kbd	Hit the server for a process handle 36ce7daf00000d5b that resolved to: [application<com.example.myapp>:3419]
default	11:54:20.222228+1000	watchdogd	Hit the server for a process handle 36ce7daf00000d5b that resolved to: [application<com.example.myapp>:3419]
default	11:54:20.231316+1000	IDSCredentialsAgent	Hit the server for a process handle 36ce7daf00000d5b that resolved to: [application<com.example.myapp>:3419]
default	11:54:20.233124+1000	symptomsd	Hit the server for a process handle 36ce7daf00000d5b that resolved to: [application<com.example.myapp>:3419]
default	11:54:20.240406+1000	wifid	-[WiFiUsageApplicationSession applicationStateDidChange:withAttributes:]: application session started:com.example.myapp
default	11:54:20.373960+1000	ReportCrash	Sending event: com.apple.stability.crash {"appVersion":"1.0.0","bundleID":"com.example.myapp","exceptionCodes":"UNKNOWN_0x32 at 0x000000010bc01d60","incidentID":"083FA319-562B-4503-987F-1765A445BEE2","logwritten":1,"process":"Runner","terminationReasonExceptionCode":"0x2","terminationReasonNamespace":"CODESIGNING"}
default	11:54:20.541918+1000	analyticsd	Aggregated. Transform: StabilityCrashNumerator Dirty: 3 Event: com.apple.stability.crash {"appVersion":"1.0.0","bundleID":"com.example.myapp","exceptionCodes":"UNKNOWN_0x32 at 0x000000010bc01d60","incidentID":"083FA319-562B-4503-987F-1765A445BEE2","logwritten":1,"process":"Runner","terminationReasonExceptionCode":"0x2","terminationReasonNamespace":"CODESIGNING","timestamp":1593568460328987}
default	11:54:20.541951+1000	analyticsd	Aggregated. Transform: StabilityCrashNumerator2 Dirty: 3 Event: com.apple.stability.crash {"appVersion":"1.0.0","bundleID":"com.example.myapp","exceptionCodes":"UNKNOWN_0x32 at 0x000000010bc01d60","incidentID":"083FA319-562B-4503-987F-1765A445BEE2","logwritten":1,"process":"Runner","terminationReasonExceptionCode":"0x2","terminationReasonNamespace":"CODESIGNING","timestamp":1593568460328987}
default	11:54:20.542412+1000	analyticsd	Aggregated. Transform: StabilityCrashNumerator3 Dirty: 3 Event: com.apple.stability.crash {"appVersion":"1.0.0","bundleID":"com.example.myapp","exceptionCodes":"UNKNOWN_0x32 at 0x000000010bc01d60","incidentID":"083FA319-562B-4503-987F-1765A445BEE2","logwritten":1,"process":"Runner","terminationReasonExceptionCode":"0x2","terminationReasonNamespace":"CODESIGNING","timestamp":1593568460328987}
default	11:54:20.639621+1000	SpringBoard	Front display did change: <SBApplication: 0x283906220; com.example.myapp>

flutter doctor -v

[✓] Flutter (Channel stable, v1.17.4, on macOS 10.16 20A4299v, locale en-AU)
 
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 11.5)
[✓] Android Studio (version 3.5)
[✓] VS Code (version 1.46.1)
[✓] Connected device (1 available)

• No issues found!
ray@node0 mobile_app % flutter doctor -v
[✓] Flutter (Channel stable, v1.17.4, on macOS 10.16 20A4299v, locale en-AU)
    • Flutter version 1.17.4 at /Users/ray/Documents/flutter
    • Framework revision 1ad9baa8b9 (13 days ago), 2020-06-17 14:41:16 -0700
    • Engine revision ee76268252
    • Dart version 2.8.4

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/ray/Library/Android/sdk
    • Platform android-28, build-tools 28.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.5)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.5, Build version 11E608c
    • CocoaPods version 1.9.1

[✓] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 41.1.2
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

[✓] VS Code (version 1.46.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.12.1

[✓] Connected device (1 available)
    • 01 • 00008030-0002546C3620802E • ios • iOS 14.0

• No issues found!

Admin edit:

===============================================================================

Summary of issue as of 2020-09-7

The current solution based on ios-deploy 1.11.2 beta 1 will most likely be the stable solution when iOS 14 comes out this month.

Affected workflows

All Flutter apps built with a Debug Flutter build cannot be launched on iOS 14 physical devices from the device itself without a host computer. This includes launching via the home screen (springboard), deep linking, notifications etc. This is a new restriction from iOS 14 on apps' ability to set itself in debug mode in order to change the execution mode of newly JIT'ed code.

Full-Flutter - Solution

If you created your Flutter project via flutter create, you have a 'full-Flutter' project. To launch a debug build Flutter app, you can either

1- Launch via flutter run on Flutter master channel.
2- If you already have your desired flutter flags set (such as --local-engine, --target, --route, etc), you can also launch via Xcode with the iOS Xcode project at <your Flutter project root>/ios/Runner.xcworkspace.
3- Build and install a Profile/Release build of your Flutter app. You can then relaunch from home screen, notification etc from the device directly without a connected host.
4- If you already build your iOS app via flutter build ios --debug, you can also launch with ios-deploy 1.11.2 beta 1 and later via ios-deploy --noinstall --justlaunch --bundle <your Flutter project root>/ios/Debug-iphoneos/Runner.app.

Add-to-app - Solution

If you created your Flutter project via flutter create -t module and embedded the Flutter module inside your own host iOS app via Cocoapods or the module framework build via flutter build ios-framework, you have an 'add-to-app' project.

Your add-to-app project will crash starting in iOS 14 when you run your FlutterEngine if your Flutter module is a debug build.

To mitigate, you can either:

1- Re-launch your host iOS app from Xcode.
2- Embed a Profile/Release build of your Flutter module instead. You can then relaunch your host app and enter the Flutter screen from the home screen, notification etc from your device directly without a connected host.
3- Re-launch your host iOS app with ios-deploy 1.11.2 beta 1 and later via ios-deploy --noinstall --justlaunch --bundle <your iOS .app which embeds a Flutter module>. (Convenience feature request to allow --bundle_id to be specified instead of --bundle in ios-deploy).

Once launched, you can then enter your Flutter module's UI and flutter attach to debug and hot-reload as usual on Flutter master channel. Not #63893. You cannot flutter attach on iOS 14 if you're not on master channel. You must accept the local network permission dialog in order to flutter attach on iOS 14.

Activity

  1. codeliu6572 commented on Jul 1, 2020

    @codeliu6572
    codeliu6572
    on Jul 1, 2020

    This question is same to mine.#60522
    But it does not resolved. I am waiting too. In addition, It crashed not just at iOS 14, it can also crash at other iPhones,like ,iOS 12.5,ios13.5.1, and other version, this bug happened on flutter SDK 1.17.0,1.17.1,1.17.4, Lower version is ok!

  2. iapicca commented on Jul 1, 2020

    @iapicca
    iapicca
    on Jul 1, 2020

    Hi @PhantomRay
    Can you please provide your flutter run --verbose
    while reproducing the steps you described

    does this behaviour occur with an "hello world" app?
    Thank you

  3. iapicca
    added
    in triagePresently being triaged by the triage team
    waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter responds
    on Jul 1, 2020

  4. codeliu6572 commented on Jul 1, 2020

    @codeliu6572
    codeliu6572
    on Jul 1, 2020

    this behaviour occur with an "hello world" app

    this behaviour occur with an "hello world" app.
    you can see issues#60522

  5. PhantomRay commented on Jul 1, 2020

    @PhantomRay
    PhantomRay
    on Jul 1, 2020
    Author

    Hi @iapicca
    The app can launch with flutter run. So it is a different scenario to what #60522 has mentioned

    @TahaTesser I run project at Xcode,then it crashed. Here is the log about 'flutter run --verbose -d <device_name>', it crash on launch.

    It happens when the iPhone is disconnected from the debug session, and then restart the app.

    I don't think flutter run --verbose will do anything unless I miss some point here?

  6. no-response
    removed
    waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter responds
    on Jul 1, 2020

  7. iapicca commented on Jul 1, 2020

    @iapicca
    iapicca
    on Jul 1, 2020

    Hi @codeliu6572
    I'm please follow up on this issue for your case
    I agree with @PhantomRay, this issue might be a different scenario.

    @PhantomRay I apologise I misinterpreted the disconnect reconnect part
    (in my head somehow sounded like "minimise resume")
    thanks for clarifying that

  8. iapicca
    added
    e: OS-version specificAffects only some versions of the relevant operating system
    found in release: 1.17Found to occur in 1.17
    platform-iosiOS applications specifically
    c: fatal crashCrashes that terminate the process
    t: xcode"xcodebuild" on iOS and general Xcode project management
    will need additional triageThis issue or PR needs attention before being routed to secondary triage
    and removed
    in triagePresently being triaged by the triage team
    on Jul 1, 2020

  9. 94 remaining items

  10. jmagman commented on Oct 1, 2020

    @jmagman
    jmagman
    on Oct 1, 2020 · Hidden as duplicate

  11. SchnMar commented on Oct 1, 2020

    @SchnMar
    SchnMar
    on Oct 1, 2020

    Still struggling to upgrade my project, will continue tomorrow. Will keep you posted!

  12. SchnMar commented on Oct 2, 2020

    @SchnMar
    SchnMar
    on Oct 2, 2020

    @jmagman Upgrade to 1.22 worked for me. Thank you

  13. Chimba123 commented on Oct 2, 2020

    @Chimba123
    Chimba123
    on Oct 2, 2020

    As I mentioned above you can do this:
    flutter run --release
    This way, the app won't crash when re-launch in a physical device.

    this works but there are no debug logs and notifications through fcm don't reach the device

  14. leonard-abusaa commented on Oct 22, 2020

    @leonard-abusaa
    leonard-abusaa
    on Oct 22, 2020 · Hidden as off-topic

  15. bazinac commented on Oct 23, 2020

    @bazinac
    bazinac
    on Oct 23, 2020 · Hidden as duplicate

  16. sjosegarcia commented on Oct 24, 2020

    @sjosegarcia
    sjosegarcia
    on Oct 24, 2020 · Hidden as off-topic

  17. bazinac commented on Oct 26, 2020

    @bazinac
    bazinac
    on Oct 26, 2020 · Hidden as off-topic

  18. jmagman commented on Oct 28, 2020

    @jmagman
    jmagman
    on Oct 28, 2020 · Hidden as off-topic

  19. sjosegarcia commented on Oct 29, 2020

    @sjosegarcia
    sjosegarcia
    on Oct 29, 2020 · Hidden as off-topic

  20. timsneath commented on Oct 29, 2020

    @timsneath
    timsneath
    on Oct 29, 2020 · Hidden as off-topic

  21. sjosegarcia commented on Oct 29, 2020

    @sjosegarcia
    sjosegarcia
    on Oct 29, 2020 · Hidden as off-topic

  22. rafaelsetragni commented on Oct 29, 2020

    @rafaelsetragni
    rafaelsetragni
    on Oct 29, 2020 · Hidden as spam

  23. jmagman commented on Oct 29, 2020

    @jmagman
    jmagman
    on Oct 29, 2020
    Member

    I am locking this closed issue. The original issue is tracking a crash that manifests in the Flutter framework.
    The only crash log I've seen on this closed issue has been from @leonard-abusaa which shows the crash in the map_launcher framework which looks totally unrelated. So to recap:

    The original crash this issue is tracking should have been resolved with flutter-team-archive/engine#20980 on 1.22. When you launch from the home screen in Debug mode you should see a message like this:
    Screen Shot 2020-10-01 at 11 03 43 AM
    Also mentioned on the website.

    If you are seeing a crash when launching your app only from the home screen on 1.22 stable we want to take a look in a new issue.

    1. Paste the output of flutter doctor -v
    2. Attach the full SYMBOLICATED crash log from your device located in Xcode > Window > Devices and Simulators > Devices > your device > View Device Logs. If you see 5 Runner 0x00000001022cfbc8 0x1022c8000 + 31688 kind of lines then your crash log is not symbolicated. See Apple's docs for details.
    3. Is your app a full Flutter app, or are you embedding a module via add-to-app?
    4. COMPLETELY fill out the issue template.

    Thanks!

  24. flutter
    locked as off topic and limited conversation to collaborators on Oct 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1High-priority issues at the top of the work lista: annoyanceRepeatedly frustrating issues with non-experimental functionalitya: existing-appsIntegration with existing apps via the add-to-app flowc: fatal crashCrashes that terminate the processcustomer: alibabadependency: dartDart team may need to help use: OS-version specificAffects only some versions of the relevant operating systemfound in release: 1.20Found to occur in 1.20has reproducible stepsThe issue has been confirmed reproducible and is ready to work onplatform-iosiOS applications specificallyt: xcode"xcodebuild" on iOS and general Xcode project managementtoolAffects the "flutter" command-line tool. See also t: labels.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions